From: Hillf Danton <hdanton@sina.com>
To: Jan Kara <jack@suse.cz>
Cc: Amir Goldstein <amir73il@gmail.com>,
syzbot <syzbot+5e3f9b2a67b45f16d4e6@syzkaller.appspotmail.com>,
linux-fsdevel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: Re: [syzbot] Re: [syzbot] [ext4?] KASAN: slab-use-after-free Read in fsnotify
Date: Wed, 17 Apr 2024 06:50:27 +0800 [thread overview]
Message-ID: <20240416225027.2499-1-hdanton@sina.com> (raw)
In-Reply-To: <20240416173211.4lnmgctyo4jn5fha@quack3>
On Tue, 16 Apr 2024 19:32:11 +0200 Jan Kara <jack@suse.cz>
>
> Hum, thinking about this some more - what if we just freed sb_info from
> destroy_super_work()? By then we definitely are not getting fsnotify()
> calls for the superblock so all the problems are solved.
>
Sounds better :)
prev parent reply other threads:[~2024-04-16 22:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 8:11 syzbot
2024-04-11 12:13 ` Jan Kara
2024-04-11 16:07 ` Amir Goldstein
2024-04-11 19:25 ` Gabriel Krisman Bertazi
2024-04-11 20:27 ` Khazhy Kumykov
2024-04-12 10:24 ` Amir Goldstein
2024-04-11 20:06 ` syzbot
2024-04-12 7:52 ` Amir Goldstein
2024-04-12 14:30 ` syzbot
2024-04-12 14:32 ` Aleksandr Nogikh
2024-04-13 1:40 ` [syzbot] " syzbot
2024-04-13 6:42 ` syzbot
2024-04-13 8:45 ` Hillf Danton
2024-04-13 9:32 ` Amir Goldstein
2024-04-13 12:04 ` Hillf Danton
2024-04-15 14:03 ` [syzbot] " Jan Kara
2024-04-15 14:47 ` Amir Goldstein
2024-04-16 10:47 ` Amir Goldstein
2024-04-17 2:03 ` syzbot
2024-04-16 13:22 ` [syzbot] " Jan Kara
2024-04-16 16:27 ` Amir Goldstein
2024-04-16 17:32 ` Jan Kara
2024-04-16 17:55 ` Amir Goldstein
2024-04-16 22:50 ` Hillf Danton [this message]
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=20240416225027.2499-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+5e3f9b2a67b45f16d4e6@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
all inboxes | Powered by JetHome®