From: syzbot <syzbot+c679f13773f295d2da53@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [squashfs?] possible deadlock in fsnotify_destroy_mark
Date: Fri, 27 Sep 2024 00:00:05 -0700 [thread overview]
Message-ID: <66f657f5.050a0220.46d20.000f.GAE@google.com> (raw)
In-Reply-To: <000000000000ae63710620417f67@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [squashfs?] possible deadlock in fsnotify_destroy_mark
Author: lizhi.xu@windriver.com
Use NOFS to replace
#syz test
diff --git a/fs/notify/inotify/inotify_user.c b/fs/notify/inotify/inotify_user.c
index c7e451d5bd51..3d0dde410b04 100644
--- a/fs/notify/inotify/inotify_user.c
+++ b/fs/notify/inotify/inotify_user.c
@@ -596,7 +596,7 @@ static int inotify_new_watch(struct fsnotify_group *group,
struct idr *idr = &group->inotify_data.idr;
spinlock_t *idr_lock = &group->inotify_data.idr_lock;
- tmp_i_mark = kmem_cache_alloc(inotify_inode_mark_cachep, GFP_KERNEL);
+ tmp_i_mark = kmem_cache_alloc(inotify_inode_mark_cachep, GFP_NOFS);
if (unlikely(!tmp_i_mark))
return -ENOMEM;
next prev parent reply other threads:[~2024-09-27 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 8:32 [syzbot] [squashfs?] possible deadlock in fsnotify_destroy_mark syzbot
2024-09-27 7:00 ` syzbot [this message]
2024-09-27 8:38 ` [syzbot] " syzbot
2024-09-27 9:12 ` [PATCH] inotify: Fix " Lizhi Xu
2024-09-27 9:31 ` Amir Goldstein
2024-09-27 10:20 ` Jan Kara
2024-09-27 13:38 ` [PATCH V2] " Lizhi Xu
2024-09-27 13:59 ` Amir Goldstein
2024-09-27 14:36 ` [PATCH V3] " Lizhi Xu
2024-09-27 14:58 ` Amir Goldstein
2024-10-02 13:23 ` Jan Kara
2024-09-27 14:42 ` [syzbot] Re: [syzbot] [squashfs?] " 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=66f657f5.050a0220.46d20.000f.GAE@google.com \
--to=syzbot+c679f13773f295d2da53@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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.