From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ravishankar N <cyberax82@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] fat: Fix bug in enforcing Long File Name length.
Date: Sun, 04 Mar 2012 06:07:39 +0900 [thread overview]
Message-ID: <87wr71tmuc.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <878vjhv1t7.fsf@devron.myhome.or.jp> (OGAWA Hirofumi's message of "Sun, 04 Mar 2012 05:59:00 +0900")
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
> Namjae Jeon <linkinjeon@gmail.com> writes:
>
>> Since '*outlen' is initialized to zero,it is currently possible to
>> create a f ilename of length (FAT_LFN_LEN +1) when utf8 is not
>> enabled.To enforce the FA T_LFN_LEN limit, we must perform one less
>> iteration.
>
> Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Please forward this too.
>> Signed-off-by: Namjae Jeon <linkinjeon@gmail.com>
>> Signed-off-by: Ravishankar N <cyberax82@gmail.com>
>> ---
>> fs/fat/namei_vfat.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/fs/fat/namei_vfat.c b/fs/fat/namei_vfat.c
>> index aae3b4e..98ae804 100644
>> --- a/fs/fat/namei_vfat.c
>> +++ b/fs/fat/namei_vfat.c
>> @@ -522,7 +522,7 @@ xlate_to_uni(const unsigned char *name, int len, unsigned char *outname,
>> op = &outname[*outlen * sizeof(wchar_t)];
>> } else {
>> for (i = 0, ip = name, op = outname, *outlen = 0;
>> - i < len && *outlen <= FAT_LFN_LEN;
>> + i < len && *outlen < FAT_LFN_LEN;
>> *outlen += 1) {
>> if (escape && (*ip == ':')) {
>> if (i > len - 5)
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2012-03-03 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 1:16 [PATCH 2/2] fat: Fix bug in enforcing Long File Name length Namjae Jeon
2012-03-03 20:59 ` OGAWA Hirofumi
2012-03-03 21:07 ` OGAWA Hirofumi [this message]
2012-03-04 5:20 ` Namjae Jeon
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=87wr71tmuc.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=cyberax82@gmail.com \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.