All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/3] orangefs: Remove useless defines
Date: Thu, 26 May 2016 21:05:26 +0100	[thread overview]
Message-ID: <20160526200526.GL14480@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAOg9mSTDt+Mk0raamO3ma5uen1hZCBVV2MvRK-2yOtznHc6PDw@mail.gmail.com>

On Thu, May 26, 2016 at 03:44:23PM -0400, Mike Marshall wrote:
> Hi Andreas...
> 
> I've looked over your patch series, and was about
> to apply it and run some tests... but the first patch
> "orangefs: Remove useless defines" won't apply.
> 
> I received your patch series a day or so after I merged
> our kernel.org tree up to 4.6, and at first I thought maybe
> you'd composed your patch during the long spell when
> the last commit in our tree was e56f49814250f4ca4b66ec7d3a71152846761d1b,
> resulting in some kind of conflict, but that's not it. Now
> that we're upstream, you're probably patching against
> the "real" Linux tree anyhow...
> 
> Here's where the fail happens:
> 
> @@ -470,7 +470,7 @@ static int orangefs_xattr_get_default(const struct
> xattr_handler *handler,
>                                       size_t size)
>  {
>         return orangefs_inode_getxattr(inode,
> -                                   ORANGEFS_XATTR_NAME_DEFAULT_PREFIX,
> +                                   "",
>                                     name,
>                                     buffer,
>                                     size);
> 
> "return orangefs_inode_getxattr(inode," should be
> "return orangefs_inode_getxattr(dentry->d_inode,"
> 
> I looked way back in time, and don't think it ever
> was "inode" instead of "dentry->d_inode", or how
> it could ever be.

Mainline has ->getxattr() called with dentry and inode passed separately;
moreover, dentry is *NOT* guaranteed to be already associated with the
inode.  See commit ce23e64 and, subsequently, b96809.

  reply	other threads:[~2016-05-26 20:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 10:29 [PATCH 0/3] Minor orangefs xattr cleanups Andreas Gruenbacher
2016-05-25 10:29 ` [PATCH 1/3] orangefs: Remove useless defines Andreas Gruenbacher
2016-05-26 19:44   ` Mike Marshall
2016-05-26 20:05     ` Al Viro [this message]
2016-05-26 22:24       ` Mike Marshall
2016-05-26 23:53         ` Al Viro
2016-05-27 21:24           ` Mike Marshall
2016-05-28 14:25             ` Mike Marshall
2016-05-25 10:29 ` [PATCH 2/3] orangefs: Remove redundant "trusted." xattr handler Andreas Gruenbacher
2016-05-25 10:29 ` [PATCH 3/3] orangefs: Remove useless xattr prefix arguments Andreas Gruenbacher
2016-05-25 15:21 ` [PATCH 0/3] Minor orangefs xattr cleanups Mike Marshall

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=20160526200526.GL14480@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=agruenba@redhat.com \
    --cc=hubcap@omnibond.com \
    --cc=linux-fsdevel@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.