From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+fcb79916dcfe2a4ed10a@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_nfs_sync_lock
Date: Sat, 31 Aug 2024 20:27:56 +0800 [thread overview]
Message-ID: <20240831122756.1426-1-hdanton@sina.com> (raw)
In-Reply-To: <0000000000007c90b60620f79447@google.com>
On Sat, 31 Aug 2024 02:46:20 -0700
> syzbot found the following issue on:
>
> HEAD commit: a18093afa393 Merge tag 'nfsd-6.11-2' of git://git.kernel.o..
> git tree: upstream
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f51063980000
#syz test upstream a18093afa393
--- l/fs/ocfs2/suballoc.c
+++ k/fs/ocfs2/suballoc.c
@@ -962,8 +962,10 @@ int ocfs2_reserve_new_metadata_blocks(st
{
int status;
int slot = ocfs2_get_meta_steal_slot(osb);
+ unsigned int pff = memalloc_nofs_save();
*ac = kzalloc(sizeof(struct ocfs2_alloc_context), GFP_KERNEL);
+ memalloc_nofs_restore(pff);
if (!(*ac)) {
status = -ENOMEM;
mlog_errno(status);
--
next prev parent reply other threads:[~2024-08-31 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 9:46 syzbot
2024-08-31 12:27 ` Hillf Danton [this message]
2024-08-31 12:50 ` 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=20240831122756.1426-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+fcb79916dcfe2a4ed10a@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®