mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bryan Donlan <bdonlan@gmail.com>
To: Theodore Tso <tytso@mit.edu>, Bryan Donlan <bdonlan@gmail.com>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	sct@redhat.com, akpm@linux-foundation.org, adilger@sun.com
Subject: Re: [PATCH v2] ext[234]: Return -EIO not -ESTALE on directory  traversal through deleted inode
Date: Sat, 21 Feb 2009 02:35:02 -0500	[thread overview]
Message-ID: <3e8340490902202335i2b01cd63gd685efeab64ad338@mail.gmail.com> (raw)
In-Reply-To: <20090220175900.GA18522@mini-me.lan>

On Fri, Feb 20, 2009 at 12:59 PM, Theodore Tso <tytso@mit.edu> wrote:
> On Fri, Feb 20, 2009 at 12:53:39PM -0500, Bryan Donlan wrote:
>> On Mon, Feb 16, 2009 at 8:10 PM, Bryan Donlan <bdonlan@gmail.com> wrote:
>>
>> > +               if (unlikely(IS_ERR(inode))) {
>> > +                       if (PTR_ERR(inode) == -ESTALE) {
>> > +                               ext3_error(dir->i_sb, "ext2_lookup",
>> > +                                               "deleted inode referenced: %lu",
>> > +                                               ino);
>> > +                               return ERR_PTR(-EIO);
>> > +                       } else {
>> > +                               return ERR_CAST(inode);
>> > +                       }
>> > +               }
>>
>> I just noticed that I forgot to edit the function name in the
>> ext3_error and ext4_error invocations... Would it be better to send a
>> delta to fix this or resubmit the whole thing?
>
> It's already been pulled into akpm's tree as separate patches.  I'll
> fix up the ext4 one by hand; probably better for you to send
> replacement patches for ext3 separately to akpm and ask him to replace.
>
> I'd suggest using __FUNC__ instead of hard-coding the function name, BTW...

akpm's already fixed up his copies. Sorry for the inconvenience there
- I made sure to get the printf format specifiers right but on the
other hand completely missed the comparatively obvious function name
:)

Thanks,

Bryan Donlan

  reply	other threads:[~2009-02-21  7:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1234588099-8445-1-git-send-email-bdonlan@fushizen.net>
2009-02-14  5:18 ` [RESEND/PATCH] ext[234]: Return -EIO not -ESTALE on directory traversal missing inode Bryan Donlan
2009-02-14 14:14   ` Theodore Tso
2009-02-15  4:53     ` Bryan Donlan
2009-02-15  5:39       ` Theodore Tso
2009-02-17  1:10     ` [PATCH v2] ext[234]: Return -EIO not -ESTALE on directory traversal through deleted inode Bryan Donlan
2009-02-20 17:53       ` Bryan Donlan
2009-02-20 17:59         ` Theodore Tso
2009-02-21  7:35           ` Bryan Donlan [this message]
2009-02-20 18:25         ` Andrew Morton

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=3e8340490902202335i2b01cd63gd685efeab64ad338@mail.gmail.com \
    --to=bdonlan@gmail.com \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®