linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] sanitize xattr handler prototypes
Date: Wed, 11 Nov 2009 09:58:40 +0000	[thread overview]
Message-ID: <1257933520.2718.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20091110121941.c814d4c9.akpm@linux-foundation.org>

Hi,

On Tue, 2009-11-10 at 12:19 -0800, Andrew Morton wrote:
> On Tue, 03 Nov 2009 17:11:47 +0000
> Steven Whitehouse <swhiteho@redhat.com> wrote:
> 
> > Hi,
> > 
> > On Tue, 2009-11-03 at 16:44 +0100, Christoph Hellwig wrote:
> > > Add a flags argument to strcut xattr_handler and pass it to all xattr           
> > > handler methods.  This allows using the same methods for multiple               
> > > handlers, e.g. for the ACL methods which perform exactly the same action        
> > > for the access and default ACLs, just using a different underlying              
> > > attribute.  With a little more groundwork it'll also allow sharing the          
> > > methods for the regular user/trusted/secure handlers in extN, ocfs2 and         
> > > jffs2 like it's already done for xfs in this patch.
> > > 
> > > Also change the inode argument to the handlers to a dentry to allow             
> > > using the handlers mechnism for filesystems that require it later,              
> > > e.g. cifs. 
> > > 
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>                                   
> > > Reviewed-by: James Morris <jmorris@namei.org>
> > > Acked-by: Joel Becker <joel.becker@oracle.com>
> > > 
> > GFS2 bits Acked-by: Steven Whitehouse <swhiteho@redhat.com>
> > 
> 
> GFS2 bits Buggered-up-by: Steven Whitehouse <swhiteho@redhat.com>
> 
> patching file fs/gfs2/acl.c
> Hunk #1 FAILED at 185.
> Hunk #2 FAILED at 196.
> Hunk #3 FAILED at 205.
> Hunk #4 FAILED at 217.
> Hunk #5 FAILED at 231.
> 5 out of 5 hunks FAILED -- saving rejects to file fs/gfs2/acl.c.rej
> patching file fs/gfs2/inode.c
> patching file fs/gfs2/xattr.c
> Hunk #1 succeeded at 567 (offset 30 lines).
> Hunk #2 succeeded at 1118 (offset 30 lines).
> Hunk #3 succeeded at 1129 (offset 30 lines).
> Hunk #4 succeeded at 1154 (offset 30 lines).
> Hunk #5 succeeded at 1182 (offset 30 lines).
> Hunk #6 succeeded at 1222 (offset 30 lines).
> Hunk #7 FAILED at 1530.
> 1 out of 7 hunks FAILED -- saving rejects to file fs/gfs2/xattr.c.rej
> 
> linux-next changes have made rather a mess of this patch.

The changes required to allow the patch to apply are pretty small, but
I'm not really sure about the best path forward at this
point :( Updating the patch is easy, but the question is which tree
should it go in when its been updated?

Steve.



  reply	other threads:[~2009-11-11  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 15:44 [PATCH 1/2] sanitize xattr handler prototypes Christoph Hellwig
2009-11-03 17:11 ` Steven Whitehouse
2009-11-10 20:19   ` Andrew Morton
2009-11-11  9:58     ` Steven Whitehouse [this message]
2009-11-12 17:56       ` Christoph Hellwig
2009-11-13  9:52         ` Steven Whitehouse

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=1257933520.2718.6.camel@localhost.localdomain \
    --to=swhiteho@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).