All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+65788f9af9d54844389e@syzkaller.appspotmail.com>
To: axboe@fb.com, hch@lst.de, james.smart@broadcom.com,
	johan.hedberg@gmail.com, jsmart2021@gmail.com,
	keith.busch@intel.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
	marcel@holtmann.org, sagi@grimberg.me,
	syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in skb_put
Date: Mon, 11 Mar 2019 06:20:00 -0700	[thread overview]
Message-ID: <000000000000032b7f0583d16e0e@google.com> (raw)
In-Reply-To: <000000000000b9e68e0581142f19@google.com>

syzbot has bisected this bug to:

commit 97faec531460c949d7120672b8c77e2f41f8d6d7
Author: James Smart <jsmart2021@gmail.com>
Date:   Thu Sep 13 23:17:38 2018 +0000

     nvme_fc: add 'nvme_discovery' sysfs attribute to fc transport device

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=121f55db200000
start commit:   97faec53 nvme_fc: add 'nvme_discovery' sysfs attribute to ..
git tree:       linux-next
final crash:    https://syzkaller.appspot.com/x/report.txt?x=111f55db200000
console output: https://syzkaller.appspot.com/x/log.txt?x=161f55db200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=59aefae07c771af6
dashboard link: https://syzkaller.appspot.com/bug?extid=65788f9af9d54844389e
userspace arch: amd64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=178e0798c00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11b4f0b0c00000

Reported-by: syzbot+65788f9af9d54844389e@syzkaller.appspotmail.com
Fixes: 97faec53 ("nvme_fc: add 'nvme_discovery' sysfs attribute to fc  
transport device")

WARNING: multiple messages have this Message-ID (diff)
From: syzbot+65788f9af9d54844389e@syzkaller.appspotmail.com (syzbot)
Subject: general protection fault in skb_put
Date: Mon, 11 Mar 2019 06:20:00 -0700	[thread overview]
Message-ID: <000000000000032b7f0583d16e0e@google.com> (raw)
In-Reply-To: <000000000000b9e68e0581142f19@google.com>

syzbot has bisected this bug to:

commit 97faec531460c949d7120672b8c77e2f41f8d6d7
Author: James Smart <jsmart2021 at gmail.com>
Date:   Thu Sep 13 23:17:38 2018 +0000

     nvme_fc: add 'nvme_discovery' sysfs attribute to fc transport device

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=121f55db200000
start commit:   97faec53 nvme_fc: add 'nvme_discovery' sysfs attribute to ..
git tree:       linux-next
final crash:    https://syzkaller.appspot.com/x/report.txt?x=111f55db200000
console output: https://syzkaller.appspot.com/x/log.txt?x=161f55db200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=59aefae07c771af6
dashboard link: https://syzkaller.appspot.com/bug?extid=65788f9af9d54844389e
userspace arch: amd64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=178e0798c00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11b4f0b0c00000

Reported-by: syzbot+65788f9af9d54844389e at syzkaller.appspotmail.com
Fixes: 97faec53 ("nvme_fc: add 'nvme_discovery' sysfs attribute to fc  
transport device")

  reply	other threads:[~2019-03-11 13:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 16:43 general protection fault in skb_put syzbot
2019-03-11 13:20 ` syzbot [this message]
2019-03-11 13:20   ` syzbot
2019-03-11 16:20   ` James Smart
2019-03-11 16:20     ` James Smart
2019-03-11 16:40     ` Dmitry Vyukov
2019-03-11 16:40       ` Dmitry Vyukov
2019-03-11 18:10       ` James Smart
2019-03-11 18:10         ` James Smart
2019-03-12 17:46         ` Dmitry Vyukov
2019-03-12 17:46           ` Dmitry Vyukov

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=000000000000032b7f0583d16e0e@google.com \
    --to=syzbot+65788f9af9d54844389e@syzkaller.appspotmail.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=james.smart@broadcom.com \
    --cc=johan.hedberg@gmail.com \
    --cc=jsmart2021@gmail.com \
    --cc=keith.busch@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=marcel@holtmann.org \
    --cc=sagi@grimberg.me \
    --cc=syzkaller-bugs@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.