linux-kernel - Re: [PATCH] xen blkfront: Delay wait for block devices until after the disk is added.

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] [day] [month] [year] [list]

Message-ID: <47E336D6.4020807@goop.org>
Date:	Thu, 20 Mar 2008 21:17:26 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Mark McLoughlin <markmc@...hat.com>
CC:	linux-kernel@...r.kernel.org,
	Christian Limpach <Christian.Limpach@...source.com>
Subject: Re: [PATCH] xen blkfront: Delay wait for block devices until after
 the disk is added.

Mark McLoughlin wrote:
> From: Christian Limpach <Christian.Limpach@...source.com>
>
> When the xen block frontend driver is built as a module the module load
> is only synchronous up to the point where the frontend and the backend
> become connected rather than when the disk is added.
>
> This means that there can be a race on boot between loading the module and
> loading the dm-* modules and doing the scan for LVM physical volumes (all
> in the initrd). In the failure case the disk is not present until after the
> scan for physical volumes is complete.
>   

Thanks, I've queued this.

    J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/