mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Dmitry Vyukov <dvyukov@google.com>,
	linux-block@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Cc: syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	syzbot <syzbot+4df6ca820108fd248943@syzkaller.appspotmail.com>,
	Ming Lei <ming.lei@redhat.com>
Subject: Re: upstream boot error: can't ssh into the instance (2)
Date: Sun, 27 Jan 2019 06:35:18 -0700	[thread overview]
Message-ID: <ace6b631-3e4b-3da5-f280-463a1bb41d97@kernel.dk> (raw)
In-Reply-To: <CACT4Y+aH2wo8rdaiZJd7s6Ct3b8mDeuvOj8CsvystV9T10+b-g@mail.gmail.com>

On 1/27/19 1:05 AM, Dmitry Vyukov wrote:
> On Sun, Jan 27, 2019 at 9:01 AM syzbot
> <syzbot+4df6ca820108fd248943@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:    7930851ef10c Merge tag 'scsi-fixes' of git://git.kernel.or..
>> git tree:       upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=1002c77f400000
>> kernel config:  https://syzkaller.appspot.com/x/.config?x=505743eba4e4f68
>> dashboard link: https://syzkaller.appspot.com/bug?extid=4df6ca820108fd248943
>> compiler:       gcc (GCC) 9.0.0 20181231 (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+4df6ca820108fd248943@syzkaller.appspotmail.com
> 
> 
> Mainline tree crashes on boot.
> +generic_make_request maintainers
> 
> [    7.485069] ==================================================================
> [    7.486411] BUG: KASAN: use-after-free in generic_make_request+0x14dd/0x1810
> [    7.487539] Read of size 2 at addr ffff8880a39618d4 by task swapper/0/1
> [    7.488689]

Ah duh, not sure how I missed that:

+                       bio_set_flag(bio, BIO_QUEUE_ENTERED);
                        ret = q->make_request_fn(q, bio);
+                       bio_clear_flag(bio, BIO_QUEUE_ENTERED);

Ming, we can't touch bio after ->make_request_fn(), it could very well be
completed already.

-- 
Jens Axboe


      reply	other threads:[~2019-01-27 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-27  8:01 syzbot
2019-01-27  8:05 ` Dmitry Vyukov
2019-01-27 13:35   ` Jens Axboe [this message]

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=ace6b631-3e4b-3da5-f280-463a1bb41d97@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=dvyukov@google.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=syzbot+4df6ca820108fd248943@syzkaller.appspotmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®