linux-kernel - Re: [PATCH v13 2/5] xenbus/backend: Protect xenbus callback with lock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <08256095-3b19-8041-9ceb-e9caa77ed4c5@suse.com>
Date:   Fri, 20 Dec 2019 12:42:11 +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 v13 2/5] xenbus/backend: Protect xenbus callback with lock

On 18.12.19 19:37, SeongJae Park wrote:
> From: SeongJae Park <sjpark@...zon.de>
> 
> A driver's 'reclaim_memory' callback can race with 'probe' or 'remove'
> because it will be called whenever memory pressure is detected.  To
> avoid such race, this commit embeds a spinlock in each 'xenbus_device'
> and make 'xenbus' to hold the lock while the corresponded callbacks are
> running.
> 
> Signed-off-by: SeongJae Park <sjpark@...zon.de>

Reviewed-by: Juergen Gross <jgross@...e.com>


Juergen