public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mike Snitzer" <snitzer@gmail.com>
To: duaneg@dghda.com
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux-ext4@vger.kernel.org
Subject: Re: [patch 069/283] ext3: handle corrupted orphan list at mount
Date: Fri, 25 Jul 2008 14:43:01 -0400	[thread overview]
Message-ID: <170fa0d20807251143r5603313fv44dac30247365c65@mail.gmail.com> (raw)
In-Reply-To: <170fa0d20807251141v4f0edfax958639b53daf7666@mail.gmail.com>

On Fri, Jul 25, 2008 at 2:41 PM, Mike Snitzer <snitzer@gmail.com> wrote:
> On Fri, Jul 25, 2008 at 2:33 PM, Mike Snitzer <snitzer@gmail.com> wrote:
>> On Fri, Jul 25, 2008 at 3:02 AM,  <akpm@linux-foundation.org> wrote:
>>> From: "Duane Griffin" <duaneg@dghda.com>
>>>
>>> If the orphan node list includes valid, untruncatable nodes with nlink > 0
>>> the ext3_orphan_cleanup loop which attempts to delete them will not do so,
>>> causing it to loop forever. Fix by checking for such nodes in the
>>> ext3_orphan_get function.
>>>
>>> This patch fixes the second case (image hdb.20000009.softlockup.gz)
>>> reported in http://bugzilla.kernel.org/show_bug.cgi?id=10882.
>>>
>>> [akpm@linux-foundation.org: coding-style fixes]
>>> [akpm@linux-foundation.org: printk warning fix]
>>> Signed-off-by: Duane Griffin <duaneg@dghda.com>
>>> Cc: <linux-ext4@vger.kernel.org>
>>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>>
>>> diff -puN fs/ext3/inode.c~ext3-handle-corrupted-orphan-list-at-mount fs/ext3/inode.c
>>> --- a/fs/ext3/inode.c~ext3-handle-corrupted-orphan-list-at-mount
>>> +++ a/fs/ext3/inode.c
>>> @@ -2253,6 +2253,19 @@ static void ext3_free_branches(handle_t
>>>        }
>>>  }
>>>
>>> +int ext3_can_truncate(struct inode *inode)
>>> +{
>>> +       if (IS_APPEND(inode) || IS_IMMUTABLE(inode))
>>> +               return 0;
>>> +       if (S_ISREG(inode->i_mode))
>>> +               return 1;
>>> +       if (S_ISDIR(inode->i_mode))
>>> +               return 1;
>>> +       if (S_ISLNK(inode->i_mode))
>>> +               return !ext3_inode_is_fast_symlink(inode);
>>> +       return 0;
>>> +}
>>> +
>>>  /*
>>>  * ext3_truncate()
>>>  *
>>> @@ -2297,12 +2310,7 @@ void ext3_truncate(struct inode *inode)
>>>        unsigned blocksize = inode->i_sb->s_blocksize;
>>>        struct page *page;
>>>
>>> -       if (!(S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode) ||
>>> -           S_ISLNK(inode->i_mode)))
>>> -               return;
>>> -       if (ext3_inode_is_fast_symlink(inode))
>>> -               return;
>>> -       if (IS_APPEND(inode) || IS_IMMUTABLE(inode))
>>> +       if (!ext3_can_truncate(inode))
>>>                return;
>>
>> I may be missing something here but doesn't the above change the logic
>> that was used in ext3_truncate for the S_ISDIR and S_ISLNK cases?
>>
>> Before ext3_truncate would be short-circuited if S_ISDIR or S_ISLNK,
>> now it won't... is that intended?
>
> Gah, I mistakenly read it as only being !S_ISDIR

heh.. I read it as only being !S_ISREG .. again sorry.

      reply	other threads:[~2008-07-25 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25  7:02 [patch 069/283] ext3: handle corrupted orphan list at mount akpm
2008-07-25 18:33 ` Mike Snitzer
2008-07-25 18:41   ` Mike Snitzer
2008-07-25 18:43     ` Mike Snitzer [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=170fa0d20807251143r5603313fv44dac30247365c65@mail.gmail.com \
    --to=snitzer@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=duaneg@dghda.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox