[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ab5v9381.fsf@devron.myhome.or.jp>
Date: Sat, 02 May 2009 20:03:10 +0900
From: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To: tridge@...ba.org
Cc: Dave Kleikamp <shaggy@...ux.vnet.ibm.com>,
Steve French <sfrench@...ibm.com>,
Mingming Cao <cmm@...ibm.com>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option
tridge@...ba.org writes:
> OGAWA Hirofumi writes:
> > Um.., probably, this patch would be handle the invalid chars for 8.3 alias.
> > Otherwise, it'll try to create ~<num> postfix, and I guess it'll become
> > the dcache problem.
>
> Do you think that will cause problems?
Yes. E.g. "test=.txt" will replace with "test_.txt" or such. But, dcache
still has "test=.txt". It means "test=.txt" would disappear with memory
pressure.
> If it will, then we could add something like this after the
> vfat_create_shortname() call:
>
> if (strncasecmp(name, msdos_name, MSDOS_NAME) != 0) {
> err = -EINVAL;
> goto out_free;
> }
>
> or would the potential case change still be a problem?
It may be ok. However, of course, it should consider other than
ascii. Well, I think the patch should be allow only perfect 8.3 name in
vfat_create_shortname(). (i.e. is_shortname && base/ext_info.valid)
Thanks.
--
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
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