linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+5e3f9b2a67b45f16d4e6@syzkaller.appspotmail.com>
To: amir73il@gmail.com, hdanton@sina.com, jack@suse.cz,
	 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: Tue, 16 Apr 2024 19:03:02 -0700	[thread overview]
Message-ID: <000000000000340f260616414106@google.com> (raw)
In-Reply-To: <CAOQ4uxg_qkqos7pXaTRAL++wYfuWZCWVcn64XK2g=GKR3zpOzQ@mail.gmail.com>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to apply patch:
checking file fs/notify/fsnotify.c
Hunk #1 FAILED at 103.
Hunk #2 succeeded at 510 (offset 4 lines).
Hunk #3 succeeded at 540 (offset 4 lines).
Hunk #4 succeeded at 569 (offset 4 lines).
1 out of 4 hunks FAILED
checking file include/linux/fsnotify_backend.h



Tested on:

commit:         2f012b22 fsnotify: fix UAF from FS_ERROR event on a sh..
git tree:       https://github.com/amir73il/linux fsnotify-fixes
kernel config:  https://syzkaller.appspot.com/x/.config?x=16ca158ef7e08662
dashboard link: https://syzkaller.appspot.com/bug?extid=5e3f9b2a67b45f16d4e6
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10103657180000


  reply	other threads:[~2024-04-17  2:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00000000000095bb400615f4b0ed@google.com>
2024-04-13  8:45 ` [syzbot] Re: [syzbot] [ext4?] KASAN: slab-use-after-free Read in fsnotify 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 [this message]
2024-04-16 13:22         ` 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
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 ` Hillf Danton
2024-04-13  6:42   ` Amir Goldstein
2024-04-13  8:58     ` syzbot
2024-04-13  8:40   ` 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=000000000000340f260616414106@google.com \
    --to=syzbot+5e3f9b2a67b45f16d4e6@syzkaller.appspotmail.com \
    --cc=amir73il@gmail.com \
    --cc=hdanton@sina.com \
    --cc=jack@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).