linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kbuild test robot <lkp@intel.com>,
	kbuild-all@01.org, miklos@szeredi.hu, sds@tycho.nsa.gov,
	pmoore@redhat.com, casey@schaufler-ca.com,
	linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
	linux-security-module@vger.kernel.org, dwalsh@redhat.com,
	dhowells@redhat.com, viro@ZenIV.linux.org.uk,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/7] security,overlayfs: Provide security hook for copy up of xattrs for overlay file
Date: Tue, 12 Jul 2016 10:02:03 +1000	[thread overview]
Message-ID: <20160712100203.0c644871@canb.auug.org.au> (raw)
In-Reply-To: <20160711134004.GA7728@redhat.com>

Hi Vivek,

On Mon, 11 Jul 2016 09:40:04 -0400 Vivek Goyal <vgoyal@redhat.com> wrote:
>
> On Sat, Jul 09, 2016 at 01:41:38AM +0800, kbuild test robot wrote:
> > Hi,
> > 
> > [auto build test ERROR on next-20160708]
> > [also build test ERROR on v4.7-rc6]
> > [cannot apply to pcmoore-selinux/next security/next v4.7-rc6 v4.7-rc5 v4.7-rc4]
> > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]  
> 
> These patches should be applied on top of overlayfs-next branch of
> miklos's vfs tree.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next

That is included in linux-next ...

-- 
Cheers,
Stephen Rothwell

  parent reply	other threads:[~2016-07-12  0:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 16:19 [RFC PATCH 0/7][V2] Overlayfs SELinux Support Vivek Goyal
2016-07-08 16:19 ` [PATCH 1/7] security, overlayfs: provide copy up security hook for unioned files Vivek Goyal
2016-07-11 15:24   ` Stephen Smalley
2016-07-11 16:54     ` Vivek Goyal
2016-07-08 16:19 ` [PATCH 2/7] selinux: Implementation for inode_copy_up() hook Vivek Goyal
2016-07-08 16:19 ` [PATCH 3/7] security,overlayfs: Provide security hook for copy up of xattrs for overlay file Vivek Goyal
2016-07-08 17:41   ` kbuild test robot
2016-07-11 13:40     ` Vivek Goyal
2016-07-11 13:50       ` [kbuild-all] [PATCH 3/7] security, overlayfs: " Fengguang Wu
2016-07-12  0:02       ` Stephen Rothwell [this message]
2016-07-11 15:31   ` [PATCH 3/7] security,overlayfs: " Stephen Smalley
2016-07-11 16:56     ` Vivek Goyal
2016-07-11 17:02     ` Vivek Goyal
2016-07-08 16:19 ` [PATCH 4/7] selinux: Implementation for inode_copy_up_xattr() hook Vivek Goyal
2016-07-08 16:19 ` [PATCH 5/7] selinux: Pass security pointer to determine_inode_label() Vivek Goyal
2016-07-08 16:19 ` [PATCH 6/7] security, overlayfs: Provide hook to correctly label newly created files Vivek Goyal
2016-07-08 16:19 ` [PATCH 7/7] selinux: Implement dentry_create_files_as() hook Vivek Goyal

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=20160712100203.0c644871@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=casey@schaufler-ca.com \
    --cc=dhowells@redhat.com \
    --cc=dwalsh@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=miklos@szeredi.hu \
    --cc=pmoore@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=vgoyal@redhat.com \
    --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).