linux-kernel - Re: WARNING in __put_task

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]

Date:   Wed, 10 Oct 2018 15:01:11 +0200
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Leon Romanovsky <leon@...nel.org>
Cc:     Jason Gunthorpe <jgg@...pe.ca>,
        syzbot <syzbot+1ed9dfaa984c88cf0ef8@...kaller.appspotmail.com>,
        dledford@...hat.com, swise@...ngridcomputing.com,
        markb@...lanox.com, linux-rdma@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Eric W. Biederman" <ebiederm@...ssion.com>, guro@...com,
        Kees Cook <keescook@...omium.org>,
        "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...capital.net>,
        Marcos Souza <marcos.souza.org@...il.com>,
        Michal Hocko <mhocko@...nel.org>,
        Rik van Riel <riel@...riel.com>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Will Drewry <wad@...omium.org>
Subject: Re: WARNING in __put_task_struct (2)

On Tue, Oct 9, 2018 at 1:30 PM, Leon Romanovsky <leon@...nel.org> wrote:
> On Mon, Oct 08, 2018 at 01:45:13PM -0600, Jason Gunthorpe wrote:
>> On Mon, Oct 08, 2018 at 06:15:22PM +0200, Dmitry Vyukov wrote:
>> > On Mon, Oct 8, 2018 at 6:12 PM, syzbot
>> > <syzbot+1ed9dfaa984c88cf0ef8@...kaller.appspotmail.com> wrote:
>> > > Hello,
>> > >
>> > > syzbot found the following crash on:
>> > >
>> > > HEAD commit:    ae16eea39a86 Add linux-next specific files for 20181008
>> > > git tree:       linux-next
>> > > console output: https://syzkaller.appspot.com/x/log.txt?x=12e7c6a1400000
>> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=42525ce985d1a955
>> > > dashboard link: https://syzkaller.appspot.com/bug?extid=1ed9dfaa984c88cf0ef8
>> > > compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
>> > >
>> > > Unfortunately, I don't have any reproducer for this crash yet.
>> > >
>> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> > > Reported-by: syzbot+1ed9dfaa984c88cf0ef8@...kaller.appspotmail.com
>> >
>> >
>> > This was triggered by the following program, all is rdma-related, so
>> > +rdma maintainers.
>> >
>> > 10:27:26 executing program 5:
>> > r0 = openat$rdma_cm(0xffffffffffffff9c,
>> > &(0x7f0000000380)='/dev/infiniband/rdma_cm\x00', 0x2, 0x0)
>> > write$RDMA_USER_CM_CMD_CREATE_ID(r0, &(0x7f0000000080)={0x0, 0x18,
>> > 0xfa00, {0x0, &(0x7f0000000040)={<r1=>0xffffffffffffffff}, 0x13f}},
>> > 0x12d)
>> > write$RDMA_USER_CM_CMD_RESOLVE_IP(r0, &(0x7f0000000200)={0x3, 0x40,
>> > 0xfa00, {{0xa, 0x4e21}, {0xa, 0x0, 0x0, @mcast1}, r1}}, 0x48)
>> > write$RDMA_USER_CM_CMD_CREATE_ID(r0, &(0x7f0000000340)={0x0, 0x18,
>> > 0xfa00, {0x0, &(0x7f0000000300)={<r2=>0xffffffffffffffff}, 0x13f}},
>> > 0x20)
>> > write$RDMA_USER_CM_CMD_SET_OPTION(r0, &(0x7f00000002c0)={0xe, 0x18,
>> > 0xfa00, @id_afonly={&(0x7f0000000000)=0x1, r1, 0x0, 0x2, 0x4}}, 0x20)
>> > write$RDMA_USER_CM_CMD_RESOLVE_IP(r0, &(0x7f0000000100)={0x3, 0x40,
>> > 0xfa00, {{0x2, 0x4e21}, {0xa, 0x0, 0x0, @local}, r2}}, 0x1ff)
>> > write$RDMA_USER_CM_CMD_DESTROY_ID(r0, &(0x7f0000000180)={0x1, 0x10,
>> > 0xfa00, {&(0x7f00000000c0), r2}}, 0x18)
>>
>> This might be fixed in Linux-next now by this commit:
>>
>> Author: Leon Romanovsky <leonro@...lanox.com>
>> Date:   Tue Oct 2 11:48:03 2018 +0300
>>
>>     RDMA/restrack: Release task struct which was hold by CM_ID object
>
> Jason,
>
> I afraid that the opposite it more accurate.
>
> This issue was introduced by that commit and According to linux-next
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next-history.git/tag/?h=next-20181008
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next-history.git/commit/?h=next-20181008&id=ae16eea39a86735f4ed0b5a6e9fe43c6cedb13b3
> The RDMA tree has commit ed7a01fd3fd77f40b4ef2562b966a5decd8928d2,
> which is exactly the one you cited above.
> https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/?h=for-next&id=ed7a01fd3fd77f40b4ef2562b966a5decd8928d2
>
> Any ideas how?

I marked another bug as dup of this because it looks like the same root cause:
https://syzkaller.appspot.com/bug?id=e1854417677586ce3d00f498f19816cb4fd15676
And that dup bug has a C reproducer.