[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000000000008738e9058514f19c@google.com>
Date: Wed, 27 Mar 2019 08:18:01 -0700
From: syzbot <syzbot+2a73a6ea9507b7112141@...kaller.appspotmail.com>
To: akpm@...ux-foundation.org, amir73il@...il.com,
gregkh@...uxfoundation.org, kstewart@...uxfoundation.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
mark.rutland@....com, mszeredi@...hat.com, oleg@...hat.com,
paulmck@...ux.vnet.ibm.com, syzkaller-bugs@...glegroups.com,
tglx@...utronix.de, viro@...iv.linux.org.uk
Subject: Re: possible deadlock in acct_pin_kill
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+2a73a6ea9507b7112141@...kaller.appspotmail.com
Tested on:
commit: 6c66f635 kernel/acct.c: fix locking order when switching a..
git tree: https://github.com/amir73il/linux.git acct_pin_kill_deadlock
kernel config: https://syzkaller.appspot.com/x/.config?x=bd771c0a1616f2b7
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Note: testing is done by a robot and is best-effort only.
Powered by blists - more mailing lists