LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: jim.cromie@gmail.com
To: Jens Axboe <axboe@kernel.dk>
Cc: Oleksandr Natalenko <oleksandr@natalenko.name>,
LKML <linux-kernel@vger.kernel.org>,
Paolo Valente <paolo.valente@linaro.org>,
linux-block@vger.kernel.org
Subject: Re: 5.14.0-rc1 KASAN use after free
Date: Fri, 23 Jul 2021 09:08:32 -0400 [thread overview]
Message-ID: <CAJfuBxwJam5=s3Rr06RyLoO19s3HTBomnNi6P3dw59s_b7we+Q@mail.gmail.com> (raw)
In-Reply-To: <98103103-c517-59d2-a4d6-9b0758cbdfc1@kernel.dk>
On Sun, Jul 18, 2021 at 5:58 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 7/18/21 3:08 PM, Oleksandr Natalenko wrote:
> > + Paolo, Jens et al.
> >
> > On čtvrtek 15. července 2021 16:32:29 CEST jim.cromie@gmail.com wrote:
> >> hi all,
> >>
> >> I noticed this report this morning, from 3 days ago,
> >> about 10 minutes after boot.
> >> Its easiest to ignore it, and I dont want to make a fuss,
> >> but it looks useful to someone
> >>
> >>
> >> [ 33.663464] Bluetooth: RFCOMM ver 1.11
> >> [ 646.343628]
> >> ================================================================== [
> >> 646.343649] BUG: KASAN: use-after-free in bfq_get_queue+0x47d/0x900 [
> >> 646.343680] Read of size 8 at addr ffff88810d864a00 by task
> >> journal-offline/1639
>
> There are only a few commits between 5.13 and master in this area, see
> attached. I'd just start reverting from the top, one by one, and see
> which one is causing the issue. Jim, would that be feasible?
>
oops, didn't see this earlier.
It hasnt happened since, I can try to recreate mid-next-week
> --
> Jens Axboe
>
next prev parent reply other threads:[~2021-07-23 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 14:32 5.14.0-rc1 KASAN use after free jim.cromie
2021-07-18 21:08 ` Oleksandr Natalenko
2021-07-18 21:58 ` Jens Axboe
2021-07-23 13:08 ` jim.cromie [this message]
2021-08-02 14:21 ` Paolo Valente
2021-08-02 18:22 ` jim.cromie
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='CAJfuBxwJam5=s3Rr06RyLoO19s3HTBomnNi6P3dw59s_b7we+Q@mail.gmail.com' \
--to=jim.cromie@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.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).