linux-kernel - Re: possible deadlock in shmem_file

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJWu+oo1g3oAuDQAbmB+vyX4tX+7y24Wj5LqXGnt9eFFRsFdUw@mail.gmail.com>
Date:   Wed, 24 Jan 2018 13:11:38 -0800
From:   Joel Fernandes <joelaf@...gle.com>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        syzbot <syzbot+8ec30bb7bf1a981a2012@...kaller.appspotmail.com>,
        Hugh Dickins <hughd@...gle.com>, Linux-MM <linux-mm@...ck.org>,
        syzkaller-bugs@...glegroups.com
Subject: Re: possible deadlock in shmem_file_llseek

On Wed, Jan 24, 2018 at 10:40 AM, Dmitry Vyukov <dvyukov@...gle.com> wrote:
> On Wed, Jan 24, 2018 at 6:47 PM, Joel Fernandes <joelaf@...gle.com> wrote:
>>
>> #syz test: https://github.com/joelagnel/linux.git test-ashmem
>
>
> Oops, this email somehow ended up without Content-Type header, which
> was unexpected on syzbot side. Now should be fixed with:
> https://github.com/google/syzkaller/commit/866f1102f786c19a67e3857f891eaf5107550663
>
> Let's try again:
>
> #syz test: https://github.com/joelagnel/linux.git test-ashmem

Hehe glad I could trigger the syzcaller side bug ;D I actually edited
the email in plain text to be more git send-email friendly... sorry
I'm old fashioned but in this case it worked out for the better ;)

- Joel