linux-kernel - Re: [PATCH 08/17] blkcg: shoot down blkio

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: <20120123204757.GM12652@google.com>
Date:	Mon, 23 Jan 2012 12:47:57 -0800
From:	Tejun Heo <tj@...nel.org>
To:	Lennart Poettering <mzxreary@...inter.de>
Cc:	Vivek Goyal <vgoyal@...hat.com>, axboe@...nel.dk,
	ctalbott@...gle.com, rni@...gle.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/17] blkcg: shoot down blkio_groups on elevator switch

Hello, Lennart.

On Mon, Jan 23, 2012 at 09:43:52PM +0100, Lennart Poettering wrote:
> I didn't really follow the whole discussion here, but if this is about
> adjusting parameters of a block device as the block device shows up this
> must necessarily happen in an udev rule (and not in a daemon watching
> block devices using libudev), since you most likely need the
> synchronicity: i.e. you want to avoid that normal (libudev-using)
> userspace code ever sees the device before those params are written to
> the device. A daemon asynchronously watching the devices with libudev
> for adjusting such tunables is necessarily racy.

Yeap, this needs to be synchronous so that it's configured before the
rest of system notices the device.  Vivek, can you please ask the
tuned guys to take a look?

Thanks.

-- 
tejun
--
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/