linux-kernel - Re: [patch 0/4] Updated AN patches, now without gendisk

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: <3ae72650708110700x7ddf3d57ue9a8875761425f52@mail.gmail.com>
Date:	Sat, 11 Aug 2007 16:00:53 +0200
From:	"Kay Sievers" <kay.sievers@...y.org>
To:	"Kristen Carlson Accardi" <kristen.c.accardi@...el.com>
Cc:	jeff@...zik.org, James.Bottomley@...eleye.com,
	linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	"David Zeuthen" <david@...ar.dk>
Subject: Re: [patch 0/4] Updated AN patches, now without gendisk

On 8/8/07, Kristen Carlson Accardi <kristen.c.accardi@...el.com> wrote:
> Here is an updated set of patches that implement Asynchronous Notification
> support for ATAPI devices.  In this version I no longer export the AN
> capability through genhd, and the uevent is sent by the scsi_device
> instead of gendisk.  I added a generic SCSI device event mechanism so
> that it can be expanded in the future with other types of events.  Please
> let me know what you think.

Does that mean:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8ce7ad7b2d11fae2c3d285a6a0caea9322c0b8fc

will go away?

Then we will need to come up with an idea to propagate that to the
blockdev, it gets a bit nasty for userspace to find out which
blockdevice it should update. It's certainly possible, but just not as
easy as it is now, because userspace just doesn't really care in most
cases what kind of bus device a block device is coming from.

And it would also be nice to plug exactly the same kind of media
change notification for devices which only revalidate at open(). That
way we could unify all the removable media handling into a single code
path. We would just check if AN is supported, and wait for events, or
start polling the device if AN isn't supported. It would be great if
we can get the same events in both cases, so we don't need to keep two
completely different ways to implement this.

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