linux-kernel - Re: [patch 114/123] dm ioctl: only issue uevent on resume if state changed

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: <20100322185409.GL919@agk-dp.fab.redhat.com>
Date:	Mon, 22 Mar 2010 18:54:09 +0000
From:	Alasdair G Kergon <agk@...hat.com>
To:	Greg KH <gregkh@...e.de>
Cc:	Mike Snitzer <snitzer@...hat.com>, linux-kernel@...r.kernel.org,
	stable@...nel.org, stable-review@...nel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk, Dave Wysochanski <dwysocha@...hat.com>,
	Peter Rajnoha <prajnoha@...hat.com>
Subject: Re: [patch 114/123] dm ioctl: only issue uevent on resume if state
	changed

On Mon, Mar 22, 2010 at 02:43:17PM -0400, Mike Snitzer wrote:
> The following upstream dm-ioctl patch also needs to go to stable now
 
Ack.

This is for the benefit of systems that have switched over to using udev
rules to manage dm devices (instead of dm/lvm2 code).  The userspace
code that issued the ioctl needs to be told whether or not a uevent was
issued so that it knows whether or not there is udev processing to wait
for.

Alasdair

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