| 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
| ||
|
Date: Mon, 25 Feb 2013 23:39:52 +0100 From: Kay Sievers <kay@...y.org> To: Greg KH <greg@...ah.com> Cc: Rusty Russell <rusty@...tcorp.com.au>, Milos Vyletel <milos.vyletel@....cz>, linux-kernel@...r.kernel.org, linux-hotplug@...r.kernel.org, virtualization@...ts.linux-foundation.org, mst@...hat.com Subject: Re: [PATCH] virtio-blk: emit udev event when device is resized On Mon, Feb 25, 2013 at 11:12 PM, Greg KH <greg@...ah.com> wrote: > Hm, I thought we were frowning apon running binaries from udev rules > these days, especially ones that might have big consequences (like > resizing a disk image) like this. > > Kay, am I right? We removed most of them from the default setups, yes. But there is nothing wrong if people want to ship that in some package or as custom rules. It looks fine to me, we would just not add such things to the default set of of rules these days. > We already emit KOBJECT_CHANGE events when block devices change, from > within the block core code. Why is the patch below needed instead of > using these events that are already generated? How are virtio block > devices special? I think we only do that for dm and md and a couple of special cases like loop and read-only settings. Kay -- 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/
Powered by blists - more mailing lists