linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+2a73a6ea9507b7112141@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, amir73il@gmail.com,
	gregkh@linuxfoundation.org, kstewart@linuxfoundation.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	mark.rutland@arm.com, mszeredi@redhat.com, oleg@redhat.com,
	paulmck@linux.vnet.ibm.com, syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de, viro@zeniv.linux.org.uk
Subject: Re: possible deadlock in acct_pin_kill
Date: Wed, 27 Mar 2019 08:18:01 -0700	[thread overview]
Message-ID: <0000000000008738e9058514f19c@google.com> (raw)
In-Reply-To: <CAOQ4uxgUNDTWvFzFJR_OENBZ_hYtwLGHem_yUd406hr7f5QX+g@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger  
crash:

Reported-and-tested-by:  
syzbot+2a73a6ea9507b7112141@syzkaller.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.

  reply	other threads:[~2019-03-27 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0000000000007dedf00576dd53eb@google.com>
2019-03-27  3:53 ` possible deadlock in acct_pin_kill syzbot
2019-03-27  7:16   ` Amir Goldstein
2019-03-27 15:18     ` syzbot [this message]
2019-03-28  8:23     ` Dmitry Vyukov
2019-04-19  7:52       ` Amir Goldstein

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=0000000000008738e9058514f19c@google.com \
    --to=syzbot+2a73a6ea9507b7112141@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=amir73il@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mszeredi@redhat.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).