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]
Date:	Thu, 6 Dec 2012 11:50:24 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Dave Chinner <david@...morbit.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Martin Steigerwald <Martin@...htvoll.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate
 UAPI

On Thu, Dec 06, 2012 at 07:06:45AM -0500, Christoph Hellwig wrote:
> 
> Also the only conference outcome I remember is that everyone at LSF
> except for Ted basically said "no fucking way".
> 

At LSF, that's correct.  And as a result, the people who need this --
Google and Tao Bao -- have decided to keep the patch as an out-of-tree
patch, much like the Android wakelock patch was out of tree, and for
similar reasons --- because the community has rejected the
functionality.

At this point, I've only asked that the bit be reserved, so we don't
have to worry about codepoint collisions.  (We'd have the same issue
with an ioctl, BTW --- we would need to reserve an ioctl number to
avoid collisions, although granted there are ways to cleverly choose
an ioctl number that would reduce the chance of collisions even if it
isn't formally reserved.)

Note that this is not a kernel fork the same way the android wakelock
is not a kernel fork.  It's an out of tree patch which has been
rejected by upstream.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ