From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/5] kernfs: Switch to generic xattr handlers
Date: Sat, 30 Apr 2016 10:02:31 -0700 [thread overview]
Message-ID: <20160430170231.GA30451@kroah.com> (raw)
In-Reply-To: <1461939517-15497-4-git-send-email-agruenba@redhat.com>
On Fri, Apr 29, 2016 at 04:18:35PM +0200, Andreas Gruenbacher wrote:
> Unlike with most other filesystems, xattrs in kernfs are attached to the
> dentries (dentry->d_fsdata). Once security modules start calling get
> xattr handlers with a NULL dentry (because of an unknown dentry), we'll
> have to start check for that in kernfs_xattr_get.
>
> Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Note, I'm not the only maintainer of kernfs...
Anyway:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2016-04-30 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 14:18 [PATCH 0/5] Some more xattr cleanups Andreas Gruenbacher
2016-04-29 14:18 ` [PATCH 1/5] jffs2: Remove jffs2_{get,set,remove}xattr macros Andreas Gruenbacher
2016-04-29 14:18 ` [PATCH 2/5] hfs: Switch to generic xattr handlers Andreas Gruenbacher
2016-04-29 14:18 ` [PATCH 3/5] kernfs: " Andreas Gruenbacher
2016-04-30 17:02 ` Greg Kroah-Hartman [this message]
2016-04-30 17:25 ` Al Viro
2016-05-01 10:45 ` Andreas Grünbacher
2016-05-01 16:27 ` Greg Kroah-Hartman
2016-04-29 14:18 ` [PATCH 4/5] sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names Andreas Gruenbacher
2016-04-29 14:18 ` [PATCH 5/5] sockfs: Get rid of getxattr iop Andreas Gruenbacher
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=20160430170231.GA30451@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agruenba@redhat.com \
--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 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.