All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Borisov <ext-roman.borisov@nokia.com>
To: ext Eric Sandeen <sandeen@redhat.com>, jack@suse.cz
Cc: Aaro Koskinen <aaro.koskinen@nokia.com>,
	tytso@mit.edu, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org, ext-phil.2.carmody@nokia.com
Subject: Re: [PATCH] ext4: fix typo in ext4_find_entry()
Date: Thu, 16 Dec 2010 16:41:13 +0300	[thread overview]
Message-ID: <4D0A16F9.9000503@nokia.com> (raw)
In-Reply-To: <4CFFC609.1090506@redhat.com>

On 12/08/2010 08:53 PM, ext Eric Sandeen wrote:
> On 12/08/2010 10:33 AM, Aaro Koskinen wrote:
>> There should be a check for NUL character instead of '0'.
>>
>> Reported-by: Phil Carmody<ext-phil.2.carmody@nokia.com>
>> Signed-off-by: Aaro Koskinen<aaro.koskinen@nokia.com>
>> ---
>>   fs/ext4/namei.c |    2 +-
>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
>> index 92203b8..dc40e75 100644
>> --- a/fs/ext4/namei.c
>> +++ b/fs/ext4/namei.c
>> @@ -872,7 +872,7 @@ static struct buffer_head * ext4_find_entry (struct inode *dir,
>>   	if (namelen>  EXT4_NAME_LEN)
>>   		return NULL;
>>   	if ((namelen<= 2)&&  (name[0] == '.')&&
>> -	    (name[1] == '.' || name[1] == '0')) {
>> +	    (name[1] == '.' || name[1] == '\0')) {
>>   		/*
>>   		 * "." or ".." will only be in the first block
>>   		 * NFS may look up ".."; "." should be handled by the VFS
>
> Yep, as it was reviewed on the list when originally sent, oops! ;)
>
> -Eric

Hi,

the same fix should be done for ext3 patch which is planned to be in 
mainline: http://www.spinics.net/lists/linux-ext4/msg21215.html

Roman

      reply	other threads:[~2010-12-16 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 16:33 [PATCH] ext4: fix typo in ext4_find_entry() Aaro Koskinen
2010-12-08 17:53 ` Eric Sandeen
2010-12-16 13:41   ` Roman Borisov [this message]

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=4D0A16F9.9000503@nokia.com \
    --to=ext-roman.borisov@nokia.com \
    --cc=aaro.koskinen@nokia.com \
    --cc=ext-phil.2.carmody@nokia.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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.