From: Mark Mielke <mark@mark.mielke.cc>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Malcolm Smith <msmith@operamail.com>,
linux-kernel@vger.kernel.org, chaffee@cs.berkeley.edu
Subject: Re: [RFC] FAT extension filters
Date: Wed, 15 May 2002 14:05:43 -0400 [thread overview]
Message-ID: <20020515140542.A3621@mark.mielke.cc> (raw)
In-Reply-To: <87u1p960va.fsf@devron.myhome.or.jp> <200205151749.g4FHnkt183716@saturn.cs.uml.edu>
On Wed, May 15, 2002 at 01:49:46PM -0400, Albert D. Cahalan wrote:
> I think the problem is in fs/fat/dir.c where
> it does:
> for (i = 0; i < 8; i++) {
> /* see namei.c, msdos_format_name */
> if (de->name[i] == 0x05)
> work[i] = 0xE5;
> else
> work[i] = de->name[i];
> }
> That should be:
> for (i = 0; i < 8; i++) work[i] = 0xE5;
> /* see namei.c, msdos_format_name */
> if (*work == 0x05) *work = 0xE5;
I assume that should be:
> for (i = 0; i < 8; i++) work[i] = de->name[i];
> /* see namei.c, msdos_format_name */
> if (*work == 0x05) *work = 0xE5;
The comment from msdos/namei.c reads:
/* 0xE5 is legal as a first character, but we must substitute 0x05 */
/* because 0xE5 marks deleted files. Yes, DOS really does this. */
/* It seems that Microsoft hacked DOS to support non-US characters */
/* after the 0xE5 character was already in use to mark deleted files. */
A question for the long-time kernel developers who are kind enough to
spend time on a question such as this:
Should the code:
> for (i = 0; i < 8; i++) work[i] = de->name[i];
Be written as some sort of memcpy()? I would expect the inlined
version to do two 32-bit copies, or one 64-bit copy operation for
64-bit platforms for the above piece of code. Is much of the code
written as the above? Or is effort made to try and inline it
in some better architecture-specific way?
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2002-05-15 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 2:38 Malcolm Smith
2002-05-15 3:18 ` Albert D. Cahalan
2002-05-15 12:39 ` OGAWA Hirofumi
2002-05-15 17:49 ` Albert D. Cahalan
2002-05-15 18:05 ` Mark Mielke [this message]
2002-05-15 18:42 ` Albert D. Cahalan
2002-05-16 13:46 ` OGAWA Hirofumi
2002-05-15 12:49 ` Xavier Bestel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020515140542.A3621@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=acahalan@cs.uml.edu \
--cc=chaffee@cs.berkeley.edu \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=msmith@operamail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®