linux-kernel - Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH

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:	Sat, 2 May 2009 02:38:46 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Theodore Tso <tytso@....edu>,
	Christoph Hellwig <hch@...radead.org>,
	Steve French <smfrench@...il.com>,
	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>,
	Ogawa Hirofumi <hirofumi@...l.parknet.co.jp>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Michael Tokarev <mjt@....msk.ru>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	Andrew Tridgell <tridge@...ba.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option

On Fri, May 01, 2009 at 10:12:58PM -0400, Theodore Tso wrote:
> So I don't believe removing the code is the right thing to do.  I do
> believe that giving people who build and use the Linux kernel choice
> is a good thing; consider that digital cameras manufactures have
> adhered to a 8.3 filenames, which is encoded in the DCIM standard, for
> 15+ years --- and I don't believe that's an accident.  What might lead
> one company to settle and another one to fight and another to decide
> to evade the issue, may depend on many things, and may have very
> little have to do with Truth or Ethics or Morality.  Welcome to the
> law and business as practiced in our civilized society.

Still not reason to make this a config option.  There's not reason Tom
Tom can't just put a patch in to disable what they want.

Then again I have the feeling this whole thing goes deeper than people
want to make it appear.  When a patch authored by person A gets sent by
person B with a total nonsense patch description talking around the
reason why it's submitted Ccing a dozend people something is fishy and I
want this resolved first.

> (But hey, at least we don't torture people!  :-)

We don't?  Guess I missed the memo..

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