From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com>
Cc: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in do_mkdirat
Date: Sun, 11 Dec 2022 02:52:57 +0000 [thread overview]
Message-ID: <Y5VGCefLZmrOyd0Z@ZenIV> (raw)
In-Reply-To: <00000000000025ff8d05ef842be6@google.com>
On Sat, Dec 10, 2022 at 06:30:22PM -0800, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> WARNING in done_path_create
How many times does it need to be repeated that ANY BUG REPORTS INVOLVING NTFS3 IN
REPRODUCER NEED TO BE CCED TO MAINTAINERS OF NTFS3?
I'm done with any syzbot output. From now on it's getting triaged
straight to /dev/null here.
*plonk*
next prev parent reply other threads:[~2022-12-11 2:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221211002908.2210-1-hdanton@sina.com>
2022-12-11 2:30 ` [syzbot] WARNING in do_mkdirat syzbot
2022-12-11 2:52 ` Al Viro [this message]
[not found] ` <20221211075612.2486-1-hdanton@sina.com>
2022-12-11 8:39 ` Al Viro
[not found] ` <20221211102208.2600-1-hdanton@sina.com>
2022-12-11 15:46 ` Matthew Wilcox
2022-12-11 20:54 ` Al Viro
[not found] ` <20221212032911.2965-1-hdanton@sina.com>
2022-12-12 18:58 ` Theodore Ts'o
2022-12-12 19:29 ` Marco Elver
2022-12-13 1:44 ` Al Viro
2022-12-16 15:48 ` Aleksandr Nogikh
2022-12-29 21:17 ` Eric Biggers
2022-12-31 16:57 ` Theodore Ts'o
2022-12-31 17:03 ` Randy Dunlap
2023-01-03 13:36 ` Aleksandr Nogikh
[not found] ` <20221213014716.3347-1-hdanton@sina.com>
2022-12-13 3:36 ` Al Viro
[not found] ` <20221213041225.3461-1-hdanton@sina.com>
2022-12-13 11:05 ` Alexander Potapenko
[not found] <20221215235133.1097-1-hdanton@sina.com>
2022-12-16 7:53 ` syzbot
[not found] <20221210011440.2050-1-hdanton@sina.com>
2022-12-10 7:24 ` syzbot
2022-12-03 14:52 syzbot
2022-12-09 19:50 ` syzbot
2022-12-09 19:57 ` Matthew Wilcox
2022-12-10 18:06 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y5VGCefLZmrOyd0Z@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox