From: "Madhani, Himanshu" <Himanshu.Madhani@cavium.com>
To: Max Kellermann <mk@cm4all.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Dept-Eng QLA2xxx Upstream <qla2xxx-upstream@cavium.com>,
"max.kellermann@gmail.com" <max.kellermann@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/scsi/qla2xxx: fix double free bug after firmware timeout
Date: Mon, 15 Jan 2018 19:58:47 +0000 [thread overview]
Message-ID: <13B82B86-8810-4722-97F9-EC5B862ECC76@cavium.com> (raw)
In-Reply-To: <151603716189.28707.13105191089826357709.stgit@rabbit.intern.cm-ag>
Hi Max,
> On Jan 15, 2018, at 9:26 AM, Max Kellermann <mk@cm4all.com> wrote:
>
> When the qla2xxx firmware is unavailable, eventually
> qla2x00_sp_timeout() is reached, which calls the timeout function and
> frees the srb_t instance.
>
> The timeout function always resolves to qla2x00_async_iocb_timeout(),
> which invokes another callback function called "done". All of these
> qla2x00_*_sp_done() callbacks also free the srb_t instance; after
> returning to qla2x00_sp_timeout(), it is freed again.
>
> The fix is to remove the "sp->free(sp)" call from qla2x00_sp_timeout()
> and add it to those code paths in qla2x00_async_iocb_timeout() which
> do not already free the object.
>
> This is how it looks like with KASAN:
>
> BUG: KASAN: use-after-free in qla2x00_sp_timeout+0x228/0x250
> Read of size 8 at addr ffff88278147a590 by task swapper/2/0
>
> Allocated by task 1502:
> save_stack+0x33/0xa0
> kasan_kmalloc+0xa0/0xd0
> kmem_cache_alloc+0xb8/0x1c0
> mempool_alloc+0xd6/0x260
> qla24xx_async_gnl+0x3c5/0x1100
>
> Freed by task 0:
> save_stack+0x33/0xa0
> kasan_slab_free+0x72/0xc0
> kmem_cache_free+0x75/0x200
> qla24xx_async_gnl_sp_done+0x556/0x9e0
> qla2x00_async_iocb_timeout+0x1c7/0x420
> qla2x00_sp_timeout+0x16d/0x250
> call_timer_fn+0x36/0x200
>
> The buggy address belongs to the object at ffff88278147a440
> which belongs to the cache qla2xxx_srbs of size 344
> The buggy address is located 336 bytes inside of
> 344-byte region [ffff88278147a440, ffff88278147a598)
>
> Signed-off-by: Max Kellermann <mk@cm4all.com>
> ---
> drivers/scsi/qla2xxx/qla_init.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/qla2xxx/qla_init.c b/drivers/scsi/qla2xxx/qla_init.c
> index b5b48ddca962..801890564e00 100644
> --- a/drivers/scsi/qla2xxx/qla_init.c
> +++ b/drivers/scsi/qla2xxx/qla_init.c
> @@ -58,7 +58,6 @@ qla2x00_sp_timeout(unsigned long __data)
> req->outstanding_cmds[sp->handle] = NULL;
> iocb = &sp->u.iocb_cmd;
> iocb->timeout(sp);
> - sp->free(sp);
> spin_unlock_irqrestore(&vha->hw->hardware_lock, flags);
> }
>
> @@ -121,9 +120,11 @@ qla2x00_async_iocb_timeout(void *data)
> ea.data[1] = lio->u.logio.data[1];
> ea.sp = sp;
> qla24xx_handle_plogi_done_event(fcport->vha, &ea);
> + sp->free(sp);
> break;
> case SRB_LOGOUT_CMD:
> qlt_logo_completion_handler(fcport, QLA_FUNCTION_TIMEOUT);
> + sp->free(sp);
> break;
> case SRB_CT_PTHRU_CMD:
> case SRB_MB_IOCB:
>
We have patch to prevent this double free in 4.16/scsi-queue already.
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.16/scsi-queue&id=045d6ea200af794ba15515984cff63787a7fc3c0
Thanks,
- Himanshu
next prev parent reply other threads:[~2018-01-15 19:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 17:26 Max Kellermann
2018-01-15 19:58 ` Madhani, Himanshu [this message]
2018-01-15 20:37 ` Max Kellermann
2018-01-15 21:03 ` Madhani, Himanshu
2018-01-18 1:02 ` Madhani, Himanshu
-- strict thread matches above, loose matches on Subject: below --
2017-12-07 14:46 Max Kellermann
2017-12-07 20:38 ` Madhani, Himanshu
2017-12-07 22:10 ` Max Kellermann
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=13B82B86-8810-4722-97F9-EC5B862ECC76@cavium.com \
--to=himanshu.madhani@cavium.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=max.kellermann@gmail.com \
--cc=mk@cm4all.com \
--cc=qla2xxx-upstream@cavium.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®