All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5e3f9b2a67b45f16d4e6@syzkaller.appspotmail.com>
To: amir73il@gmail.com, hdanton@sina.com,
	linux-fsdevel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] KASAN: slab-use-after-free Read in fsnotify
Date: Sat, 13 Apr 2024 01:58:04 -0700	[thread overview]
Message-ID: <0000000000001b9bda0615f69622@google.com> (raw)
In-Reply-To: <CAOQ4uxhJi_YT=AZOaJGH6tt9kM7kUoAF1uzVqfGBXjvc8S78Ug@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+5e3f9b2a67b45f16d4e6@syzkaller.appspotmail.com

Tested on:

commit:         9e589786 fsnotify: do not handle events on a shutting ..
git tree:       https://github.com/amir73il/linux fsnotify-fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=11cdb161180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9995779c8305f57e
dashboard link: https://syzkaller.appspot.com/bug?extid=5e3f9b2a67b45f16d4e6
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=14f52d33180000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2024-04-13  8:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  8:11 [syzbot] [ext4?] KASAN: slab-use-after-free Read in fsnotify 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 ` Hillf Danton
2024-04-13  6:42   ` Amir Goldstein
2024-04-13  8:58     ` syzbot [this message]
2024-04-13  8:40   ` syzbot
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

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=0000000000001b9bda0615f69622@google.com \
    --to=syzbot+5e3f9b2a67b45f16d4e6@syzkaller.appspotmail.com \
    --cc=amir73il@gmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.