Messages in this thread | | | Subject | Re: [PATCH 1/4] Move check for invalid chars to vfat_valid_longname() | From | OGAWA Hirofumi <> | Date | Wed, 10 Nov 2004 03:41:32 +0900 |
| |
Rene Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
> But doesn't imply this we can't do any of our checks on the VFS > string?
Basically yes.
> A dot (0x2E) at the end of a filename could be the half of some other > character in some encoding, right?
'.'/' ' is not contained as second byte by any encodings, at least current nls is supporting encodings.
> And the same could be said about the checks in > vfat_valid_longname(), no?
These are string, not char. These should be unique.
> The patch you asked for converting IS_BADCHAR to an inline function > follows. I rolled it together with the other conversions from patch 3. > Applies directly on top of 2.6.10-rc1-bk18.
Thanks. -- OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |