linux-kernel - Re: [PATCH 00/10] bkl: pushdowns from Arnd, and compile fixes

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: <i2rc62985531004270540g42d99595rc7c83dfa172f18e4@mail.gmail.com>
Date:	Tue, 27 Apr 2010 14:40:36 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	John Kacur <jkacur@...hat.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jan Blunck <jblunck@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 00/10] bkl: pushdowns from Arnd, and compile fixes

2010/4/27 Arnd Bergmann <arnd@...db.de>:
> On Tuesday 27 April 2010, John Kacur wrote:
>> These are bkl pushdowns from Arnd that conflicted with
>> Linus's "Preparation for BKL'ed ioctl removal patch". I fixed-up the merge
>> conflicts. In addition - during allyesconfig compile testing on x86_64 I found
>> a number of issues that I fixed-up
>
> Thanks for catching the scsi bugs! It was getting late yesterday night, so
> I didn't go through a full allyesconfig then.
>
>> I pushed these to my own new linus-bkl tree.
>> git://www.kernel.org/pub/scm/linux/kernel/git/jkacur/jk-2.6.git linux-bkl
>>
>> Frederic, if you want to grab those, pls do so. also, we might want to combine
>> my compile fixes with Arnd's push-down patches, for better git bisectability.
>
> Yes, your fixes (except the v4l2 patch, see comment there) should best be
> merged into the main patches.
>
> The idea was that if we manage to kill all fops->ioctl users right away,
> we wouldn't even need Linus' patch and move to dungeon level 2 directly.
> Either way works for me though.



Yeah. Since we are motivated enough to do the whole pushdown, I think we
should forget the .bkl_ioctl renaming.

This will let Greg take the staging part for example. I can take all
the unmainted rest
(basically most of the rest I guess).
--
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/