linux-kernel - Re: possible deadlock in blk_trace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1512359270.8335.7.camel@gmx.de>
Date:   Mon, 04 Dec 2017 04:47:50 +0100
From:   Mike Galbraith <efault@....de>
To:     Jens Axboe <axboe@...nel.dk>, Eric Biggers <ebiggers3@...il.com>
Cc:     syzbot 
        <bot+583353673e394aa41e5fb68ddc8b8d9d5c8d576f@...kaller.appspotmail.com>,
        linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
        mingo@...hat.com, rostedt@...dmis.org,
        syzkaller-bugs@...glegroups.com
Subject: Re: possible deadlock in blk_trace_remove

On Sun, 2017-12-03 at 17:47 -0700, Jens Axboe wrote:
> On 12/03/2017 05:44 PM, Eric Biggers wrote:
> > 
> >>> #syz fix: blktrace: fix trace mutex deadlock
> >>
> >> This is fixed in current -git.
> >>
> > 
> > I know, but syzbot needed to be told what commit fixes the bug.
> > See https://github.com/google/syzkaller/blob/master/docs/syzbot.md
> 
> Ah gotcha.

"@syzbot fix: bla" syntax would have been intuitive.

	-Mike