[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181015140201.elir7ettk7sz4aix@mac.bytemobile.com>
Date: Mon, 15 Oct 2018 16:02:01 +0200
From: Roger Pau Monné <roger.pau@...rix.com>
To: Vasilis Liaskovitis <vliaskovitis@...e.com>
CC: <xen-devel@...ts.xenproject.org>, <linux-kernel@...r.kernel.org>,
<linux-block@...r.kernel.org>, <jgross@...e.com>,
<boris.ostrovsky@...cle.com>, <konrad.wilk@...cle.com>,
<axboe@...nel.dk>
Subject: Re: [PATCH v2] xen/blkfront: avoid NULL blkfront_info dereference on
device removal
On Mon, Oct 15, 2018 at 03:25:08PM +0200, Vasilis Liaskovitis wrote:
> If a block device is hot-added when we are out of grants,
> gnttab_grant_foreign_access fails with -ENOSPC (log message "28
> granting access to ring page") in this code path:
>
> talk_to_blkback ->
> setup_blkring ->
> xenbus_grant_ring ->
> gnttab_grant_foreign_access
>
> and the failing path in talk_to_blkback sets the driver_data to NULL:
>
> destroy_blkring:
> blkif_free(info, 0);
>
> mutex_lock(&blkfront_mutex);
> free_info(info);
> mutex_unlock(&blkfront_mutex);
>
> dev_set_drvdata(&dev->dev, NULL);
>
> This results in a NULL pointer BUG when blkfront_remove and blkif_free
> try to access the failing device's NULL struct blkfront_info.
>
> Signed-off-by: Vasilis Liaskovitis <vliaskovitis@...e.com>
Reviewed-by: Roger Pau Monné <roger.pau@...rix.com>
Thanks.
I guess this is a candidate for backporting?
Powered by blists - more mailing lists