From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org ([198.137.202.133]:57386 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932728AbeFGQ7D (ORCPT ); Thu, 7 Jun 2018 12:59:03 -0400 Date: Thu, 7 Jun 2018 09:59:01 -0700 From: Matthew Wilcox To: Linus Torvalds Cc: Jan Kara , linux-fsdevel Subject: Re: [GIT PULL] UDF support for UTF-16 Message-ID: <20180607165901.GA12995@bombadil.infradead.org> References: <20180607153101.zaqogifrehyzdxpl@quack2.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Jun 07, 2018 at 09:50:00AM -0700, Linus Torvalds wrote: > On Thu, Jun 7, 2018 at 8:31 AM Jan Kara wrote: > > > > to get UDF support for UTF-16 characters in file names. > > Who uses UTF-16 in this day and age? > > It's a broken format. > > It's not mentioned in the commit logs *why* this is done. Here's some background: https://www.spinics.net/lists/linux-fsdevel/msg124310.html Yeah, it's a totally broken format, but we shouldn't be thinking that filenames which come to us in UTF16 are actually in UCS2.