From: syzbot <syzbot+7229071b47908b19d5b7@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, amir73il@gmail.com, axboe@kernel.dk,
brauner@kernel.org, cem@kernel.org, chandan.babu@oracle.com,
djwong@kernel.org, jack@suse.cz, josef@toxicpanda.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-xfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] WARNING in fsnotify_file_area_perm
Date: Fri, 07 Mar 2025 08:49:02 -0800 [thread overview]
Message-ID: <67cb237e.050a0220.15b4b9.0083.GAE@google.com> (raw)
In-Reply-To: <CAOQ4uxjxbhJPDCBnuMMmkPchFiDOwX82-35jbhbrQkbp2Rsy6g@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+7229071b47908b19d5b7@syzkaller.appspotmail.com
Tested-by: syzbot+7229071b47908b19d5b7@syzkaller.appspotmail.com
Tested on:
commit: ea33db4d fsnotify: avoid possible deadlock with HSM ho..
git tree: https://github.com/amir73il/linux fsnotify-fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=12494878580000
kernel config: https://syzkaller.appspot.com/x/.config?x=afb3000d0159783f
dashboard link: https://syzkaller.appspot.com/bug?extid=7229071b47908b19d5b7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-03-07 16:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 9:59 [syzbot] [mm?] " syzbot
2025-02-07 0:54 ` Andrew Morton
2025-02-07 8:45 ` Christian Brauner
2025-02-07 19:33 ` Amir Goldstein
2025-03-02 16:32 ` [syzbot] [xfs?] " syzbot
2025-03-04 11:06 ` Jan Kara
2025-03-04 15:09 ` Amir Goldstein
2025-03-04 16:15 ` Josef Bacik
2025-03-04 20:27 ` Amir Goldstein
2025-03-04 20:36 ` Josef Bacik
2025-03-04 21:13 ` Amir Goldstein
2025-03-07 15:46 ` Josef Bacik
2025-03-07 16:07 ` Amir Goldstein
2025-03-07 16:21 ` syzbot
2025-03-07 16:22 ` Amir Goldstein
2025-03-07 16:49 ` syzbot [this message]
2025-03-07 17:45 ` Amir Goldstein
2025-03-09 12:09 ` Amir Goldstein
2025-03-09 15:03 ` Amir Goldstein
2025-03-09 16:20 ` 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=67cb237e.050a0220.15b4b9.0083.GAE@google.com \
--to=syzbot+7229071b47908b19d5b7@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@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