Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CAE=gft4_WiL87FtZnVmZok+oXPjK=GUb5tDUPGQFijddrB0Pbg@mail.gmail.com>
 <1550172827.93548.5.camel@acm.org>
In-Reply-To: <1550172827.93548.5.camel@acm.org>
From:   Evan Green <evgreen@google.com>
Date:   Thu, 14 Feb 2019 12:45:41 -0800
Message-ID: <CAE=gft5GR1xEM1gNQjMyo_wfhs_JUAc2AUHHk5qr36EjaWv1hg@mail.gmail.com>
Subject: Re: KASAN warning in bt_for_each
To:     Bart Van Assche <bvanassche@acm.org>
Cc:     linux-block <linux-block@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Feb 14, 2019 at 11:33 AM Bart Van Assche <bvanassche@acm.org> wrote:
>
> 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/

Oh, yep, that's totally it. Did that patch make it in anywhere?
-Evan