UML: Fix block device setup User mode linux block devices start with ubd, e.g. ubda, ubdb, etc..

rules: block - add dasd to whitelist

Process cciss devices Do not skip the persistent storage rules for cciss devices

rules: re-add cciss rules The original commit (1aff206) doesn't explain why these were removed. This adds them back since they are in fact needed.

rules: whitelist xvd* devices Xen disks need to be whitelisted as well.

Add /dev/xvd* to 60-persistent-storage whitelist Without this, systemd-udevd does not create persistent storage symlinks for xen block devices.

udev: Bring back persistant storage symlinks for bcache https://bugs.debian.org/787367

rules: storage - support MemoryStick (non-Pro) cards These are handled by a different driver than MemoryStick Pro.

rules: storage - whitelist partitioned MS & MMC devices On Mon, Mar 23, 2015 at 8:55 AM, Mantas Mikulėnas <grawity@gmail.com> wrote: > On Tue, Mar 17, 2015 at 11:50 PM, Kay Sievers <kay@vrfy.org> wrote: >> On Tue, Mar 17, 2015 at 5:00 PM, Mantas Mikulėnas <grawity@gmail.com> >> wrote: >> > Accidentally dropped in 1aff20687f4868575. >> > --- >> > rules/60-persistent-storage.rules | 2 +- >> > 1 file changed, 1 insertion(+), 1 deletion(-) >> >> > +KERNEL!="loop*|mmcblk[0-9]*|mspblk[0-9]*|nvme*|sd*|sr*|vd*", >> > GOTO="persistent_storage_end" >> >> We can't do that, we need to ignore the mmc*rpmb devices: >> >> http://cgit.freedesktop.org/systemd/systemd/commit/?id=b87b01cf83947f467f3c46d9831cd67955fc46b9 >> >> Maybe "mmcblk*[0-9]" will work? > > Yeah, that would probably work (the names are like mmcblk0p1 etc.)

rules: storage - don't apply rules to remove events This line was accidentally lost in 52346b5f5424.

rules: move block device rules to its own rules file

rules: storage - relace blacklist with explicit whitelist Newly added kernel drivers repeatedly pass our blacklist and cause trouble for the devices, because they do not expect to be examined by udev's default rules which include blkid. This turns the blacklist into a whitelist. Device type which need support for additional symlinks need to be added to the whitelist now. Note, that the by-id, by-path symlinks are only intended for hotpluggable devices. There is no reason for exotic, or for statically configured devices to provide them.

rules: simplify mmc RPMB handling We don't actually want a by-path/ symlink for MMC RPMB devices, so just add them to the blacklist. This will prevent creating wrong by-path links and blkid'ing those.

rules: Fix by-path of mmc RPMB partitions and don't blkid them Linux 3.10+ exposes RPMB (Replay Protected Memory Block) partitions of MMC devices [1] ; trying to read them with blkid or other unspecific means will cause kernel buffer I/O errors and timeouts. So don't run blkid on these. Also ensure that /dev/disk/by-path creates proper symlinks and exposes the -rpmb partition separately, instead of letting the "normal" partition symlink point to the rpbm device (this is a race condition). [1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=090d25fe224c0 https://launchpad.net/bugs/1333140

gpt-auto-generator: rename root device node symlink to /dev/gpt-auto-root Before it was placed in /dev/disk/by-id, which makes it a bit too much API. However, it's mostly an implementation detail for now, hence move it out of the stable block device dir.

udev: automatically create a symlink /dev/disk/by-id/gpt-auto-root if there's a suitable root partition

doc: update punctuation Resolve spotted issues related to missing or extraneous commas, dashes.

udev: add zram to the list of devices inappropriate for symlinks udev seems to have a race condition with swapon to see which can open /dev/zram0 first, causing swapon to fail. Seems to be most noticeable on arm devices one out of every 7 times or something.

rules: there is no "ata" subsystem for ATA device

move imported udev into place

rules: move all rules to top level rules/ dir