public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+1ed9dfaa984c88cf0ef8@syzkaller.appspotmail.com>,
	dledford@redhat.com, Leon Romanovsky <leon@kernel.org>,
	swise@opengridcomputing.com, markb@mellanox.com,
	linux-rdma@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	guro@fb.com, Kees Cook <keescook@chromium.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	marcos.souza.org@gmail.com, Michal Hocko <mhocko@kernel.org>,
	Rik van Riel <riel@surriel.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Will Drewry <wad@chromium.org>
Subject: Re: WARNING in __put_task_struct (2)
Date: Mon, 8 Oct 2018 13:45:13 -0600	[thread overview]
Message-ID: <20181008194513.GC27639@ziepe.ca> (raw)
In-Reply-To: <CACT4Y+bfqk8Fczw4dJHhVzM63YhYNSovEE-KygZ1XmgUQVGCWQ@mail.gmail.com>

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@syzkaller.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@syzkaller.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@mellanox.com>
Date:   Tue Oct 2 11:48:03 2018 +0300

    RDMA/restrack: Release task struct which was hold by CM_ID object
   

Jason

  reply	other threads:[~2018-10-08 19:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000000000000b3d5610577b9e12c@google.com>
2018-10-08 16:15 ` WARNING in __put_task_struct (2) Dmitry Vyukov
2018-10-08 19:45   ` Jason Gunthorpe [this message]
2018-10-09 11:30     ` Leon Romanovsky
2018-10-10 13:01       ` Dmitry Vyukov
2018-10-14 17:12 ` syzbot

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=20181008194513.GC27639@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=akpm@linux-foundation.org \
    --cc=dledford@redhat.com \
    --cc=dvyukov@google.com \
    --cc=ebiederm@xmission.com \
    --cc=guro@fb.com \
    --cc=keescook@chromium.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=marcos.souza.org@gmail.com \
    --cc=markb@mellanox.com \
    --cc=mhocko@kernel.org \
    --cc=riel@surriel.com \
    --cc=swise@opengridcomputing.com \
    --cc=syzbot+1ed9dfaa984c88cf0ef8@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=wad@chromium.org \
    /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