[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <66f67a76.050a0220.46d20.0014.GAE@google.com>
Date: Fri, 27 Sep 2024 02:27:18 -0700
From: syzbot <syzbot+1b2d1134e0b675176a15@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org
Subject: Re: [syzbot] Re: [keyrings?] [lsm?] [ext4?] possible deadlock in
keyring_clear (2)
For archival purposes, forwarding an incoming command email to
linux-kernel@...r.kernel.org.
***
Subject: Re: [keyrings?] [lsm?] [ext4?] possible deadlock in keyring_clear (2)
Author: lizhi.xu@...driver.com
tmp no use nofs
#syz test
diff --git a/init/main.c b/init/main.c
index c4778edae797..7e08a69fc432 100644
--- a/init/main.c
+++ b/init/main.c
@@ -1261,12 +1261,15 @@ int __init_or_module do_one_initcall(initcall_t fn)
int count = preempt_count();
char msgbuf[64];
int ret;
+ unsigned int nofs_flag;
if (initcall_blacklisted(fn))
return -EPERM;
do_trace_initcall_start(fn);
+ nofs_flag = memalloc_nofs_save();
ret = fn();
+ memalloc_nofs_restore(nofs_flag);
do_trace_initcall_finish(fn, ret);
msgbuf[0] = 0;
Powered by blists - more mailing lists