From: Matthew Wilcox <willy@infradead.org>
To: syzbot <syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com>
Cc: dvyukov@google.com, elver@google.com, hdanton@sina.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] WARNING in do_mkdirat
Date: Fri, 9 Dec 2022 19:57:03 +0000 [thread overview]
Message-ID: <Y5OTDzE6grKZWrH6@casper.infradead.org> (raw)
In-Reply-To: <000000000000f865be05ef6a77fa@google.com>
On Fri, Dec 09, 2022 at 11:50:41AM -0800, syzbot wrote:
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145fde33880000
I see that ntfs3 is involved. It's probably the known issue where ntfs3
corrupts the lockdep database.
next prev parent reply other threads:[~2022-12-09 19:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 14:52 [syzbot] WARNING in do_mkdirat syzbot
2022-12-04 1:04 ` Hillf Danton
2022-12-09 19:50 ` syzbot
2022-12-09 19:57 ` Matthew Wilcox [this message]
2022-12-10 18:06 ` syzbot
[not found] <20221210011440.2050-1-hdanton@sina.com>
2022-12-10 7:24 ` syzbot
[not found] <20221211002908.2210-1-hdanton@sina.com>
2022-12-11 2:30 ` syzbot
2022-12-11 2:52 ` Al Viro
2022-12-11 7:56 ` Hillf Danton
2022-12-11 8:39 ` Al Viro
2022-12-11 10:22 ` Hillf Danton
2022-12-11 15:46 ` Matthew Wilcox
2022-12-11 20:54 ` Al Viro
2022-12-12 3:29 ` Hillf Danton
2022-12-12 18:58 ` Theodore Ts'o
2022-12-12 19:29 ` Marco Elver
2022-12-13 1:44 ` Al Viro
2022-12-13 2:25 ` Hillf Danton
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
2022-12-13 1:47 ` Hillf Danton
2022-12-13 3:36 ` Al Viro
2022-12-13 4:12 ` Hillf Danton
2022-12-13 11:05 ` Alexander Potapenko
[not found] <20221215235133.1097-1-hdanton@sina.com>
2022-12-16 7:53 ` 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=Y5OTDzE6grKZWrH6@casper.infradead.org \
--to=willy@infradead.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=hdanton@sina.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.