From: Paolo Valente <paolo.valente@linaro.org>
To: jim.cromie@gmail.com
Cc: Jens Axboe <axboe@kernel.dk>,
Oleksandr Natalenko <oleksandr@natalenko.name>,
LKML <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org
Subject: Re: 5.14.0-rc1 KASAN use after free
Date: Mon, 2 Aug 2021 16:21:20 +0200 [thread overview]
Message-ID: <FE6B2429-5846-4EE8-896A-691BD11C76D0@linaro.org> (raw)
In-Reply-To: <CAJfuBxwJam5=s3Rr06RyLoO19s3HTBomnNi6P3dw59s_b7we+Q@mail.gmail.com>
> Il giorno 23 lug 2021, alle ore 15:08, jim.cromie@gmail.com ha scritto:
>
> 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
>
Still nothing?
Thanks,
Paolo
>
>> --
>> Jens Axboe
next prev parent reply other threads:[~2021-08-02 14:24 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
2021-08-02 14:21 ` Paolo Valente [this message]
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=FE6B2429-5846-4EE8-896A-691BD11C76D0@linaro.org \
--to=paolo.valente@linaro.org \
--cc=axboe@kernel.dk \
--cc=jim.cromie@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
/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).