From: Bart Van Assche <bvanassche@acm.org>
To: Evan Green <evgreen@google.com>,
linux-block <linux-block@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>
Subject: Re: KASAN warning in bt_for_each
Date: Thu, 14 Feb 2019 11:33:47 -0800 [thread overview]
Message-ID: <1550172827.93548.5.camel@acm.org> (raw)
In-Reply-To: <CAE=gft4_WiL87FtZnVmZok+oXPjK=GUb5tDUPGQFijddrB0Pbg@mail.gmail.com>
On Thu, 2019-02-14 at 10:04 -0800, Evan Green wrote:
> Greetings, block experts!
>
> I'm trying to track down a KASAN warning I'm seeing in our downstream
> 4.19 kernel, and I could use a little help. The warning looks like
> this:
>
> [ 224.564894] BUG: KASAN: use-after-free in bt_for_each+0x1ac/0x28c
> [ 224.571195] Read of size 8 at addr ffffffc17c621340 by task fio/3851
> [ 224.577745]
> [ 224.579320] CPU: 2 PID: 3851 Comm: fio Tainted: G W 4.19.16 #398
Please have a look at this e-mail thread:
https://lore.kernel.org/linux-block/1545261885.185366.488.camel@acm.org/
Bart.
next prev parent reply other threads:[~2019-02-14 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 18:04 KASAN warning in bt_for_each Evan Green
2019-02-14 19:33 ` Bart Van Assche [this message]
2019-02-14 20:45 ` Evan Green
2019-02-14 20:50 ` Jens Axboe
2019-02-14 22:20 ` Bart Van Assche
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=1550172827.93548.5.camel@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=evgreen@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).