linux-kernel - Last ioctl bkl pushdown in the LogFS tree, but no pull request?

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>] [day] [month] [year] [list]

Message-ID: <20100812141629.GA5369@nowhere>
Date:	Thu, 12 Aug 2010 16:16:32 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Arnd Bergmann <arnd@...db.de>, Joern Engel <joern@...fs.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Last ioctl bkl pushdown in the LogFS tree, but no pull request?

Joern,

The Logfs tree contains the last ioctl bkl pushdown that is not yet upstream.

git://git.kernel.org/pub/scm/linux/kernel/git/joern/logfs.git
	ddbb5dd99c40a695d5d75645b5a18bef394acb16
	"logfs: kill BKL"

This patch seems to have missed the 2.6.35 merge window already. Do you
plan to make a pull request for 2.6.36 that includes this patch?

In fact the merge window is almost closed now. Since this is delaying
the final removal of struct file_operations:ioctl, the only solution
for us would be to cherry pick this patch from your tree. But
really I would hate to do that behind your back.

Please tell us what are your plans.

Thanks.

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