[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <027a402d-029a-e6c4-9f07-98728a161f22@suse.com>
Date: Tue, 17 Dec 2019 17:15:12 +0100
From: Jürgen Groß <jgross@...e.com>
To: SeongJae Park <sjpark@...zon.com>, axboe@...nel.dk,
konrad.wilk@...cle.com, roger.pau@...rix.com
Cc: SeongJae Park <sjpark@...zon.de>, pdurrant@...zon.com,
sj38.park@...il.com, xen-devel@...ts.xenproject.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v11 4/6] xen/blkback: Protect 'reclaim_memory()' with
'reclaim_lock'
On 17.12.19 17:07, SeongJae Park wrote:
> From: SeongJae Park <sjpark@...zon.de>
>
> The 'reclaim_memory()' callback of blkback could race with
> 'xen_blkbk_probe()' and 'xen_blkbk_remove()'. In the case, incompletely
> linked 'backend_info' and 'blkif' might be exposed to the callback, thus
> result in bad results including NULL dereference. This commit fixes the
> problem by applying the 'reclaim_lock' protection to those.
>
> Note that this commit is separated for review purpose only. As the
> previous commit might result in race condition and might make bisect
> confuse, please squash this commit into previous commit if possible.
>
> Signed-off-by: SeongJae Park <sjpark@...zon.de>
Please merge this patch into patch 2.
Juergen
Powered by blists - more mailing lists