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]

Message-ID: <20090502124436.GA14621@infradead.org>
Date:	Sat, 2 May 2009 08:44:36 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	tridge@...ba.org
Cc:	Christoph Hellwig <hch@...radead.org>,
	Matthew Wilcox <matthew@....cx>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	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>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option

On Sat, May 02, 2009 at 07:30:02PM +1000, tridge@...ba.org wrote:
> The non-technical reasons for this patch are available to anyone who
> cares to read any of the many news sites that discuss recent
> events. The fact that I can't discuss those reasons shouldn't preclude
> me from proposing a technical solution which tries to minimise the
> impact on Linux users.

Yes, the fact that you let someone else send a patch for you, refuse to
state any reason for it and when asked for it talk around the problems
is a very good reason not to bother with a patch.

If you think there is a patent problem with long file names and have
a good argument for it we should just make the reduce functionality
the default until it's settled.  If you do not have a good argument
we should drop this completely.

> I'm hoping that you and others will look at the proposed technical
> solution to the non-technical problem, and perhaps suggest better
> approaches. There are a wide variety of approaches to avoiding this
> problem, and we need to work out which, if any, should be part of the
> kernel.org releases.

Sorting out a problem starts with clearly stating what the problem is.

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