linux-kernel - Re: [PATCHSET] block: convert block drivers to ->check

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: <20110201103143.GF14211@htj.dyndns.org>
Date:	Tue, 1 Feb 2011 11:31:43 +0100
From:	Tejun Heo <tj@...nel.org>
To:	axboe@...nel.dk, linux-kernel@...r.kernel.org,
	kay.sievers@...y.org, hch@...radead.org
Subject: Re: [PATCHSET] block: convert block drivers to ->check_events()

On Tue, Jan 25, 2011 at 02:06:38PM +0100, Tejun Heo wrote:
> Hello, Jens.
> 
> On Tue, Dec 28, 2010 at 06:28:56PM +0100, Tejun Heo wrote:
> >  0001-block-don-t-implicitly-trigger-event-check-on-disk_u.patch
> >  0002-block-don-t-check-events-on-close-unless-it-was-bloc.patch
> >  0003-block-don-t-check-events-while-open-is-in-progress.patch
> >  0004-ide-convert-to-bdops-check_events.patch
> >  0005-floppy-ami-ata-flop-convert-to-bdops-check_events.patch
> >  0006-gdrom-viocd-convert-to-bdops-check_events.patch
> >  0007-paride-convert-to-bdops-check_events.patch
> >  0008-dac960-convert-to-bdops-check_events.patch
> >  0009-swim-3-convert-to-bdops-check_events.patch
> >  0010-ub-convert-to-bdops-check_events.patch
> >  0011-xsysace-convert-to-bdops-check_events.patch
> >  0012-i2o_block-convert-to-bdops-check_events.patch
> >  0013-s390-tape_block-convert-to-bdops-check_events.patch
> >  0014-umem-drop-dummy-media_changed.patch
> >  0015-pktcdvd-convert-to-bdops-check_events.patch
> >  0016-staging-convert-to-bdops-check_events.patch
> 
> This series seems to have been forgotten.  I think 0001-0003 better go
> in for 2.6.38 as they affect user-visible behavior (in not too
> significant way but still).
> 
> The other patches can go in for 2.6.39.  0005 gets an easy-to-resolve
> context conflict but all other patches apply as-is.  I'll post the
> refreshed version of 0005 as a reply to the original patch.  If you
> want the whole series reposted, please let me know.

This will now create some minor conflicts on top of the mainline.
Please let me know when you're ready to apply this.  I'll refresh and
repost.

Thank you.

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