From: Casey Schaufler <casey@schaufler-ca.com>
To: Al Viro <viro@zeniv.linux.org.uk>, Ondrej Mosnacek <omosnace@redhat.com>
Cc: Paul Moore <paul@paul-moore.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
selinux@vger.kernel.org, linux-fsdevel@vger.kernel.org,
LSM <linux-security-module@vger.kernel.org>
Subject: Re: linux-next: manual merge of the selinux tree with the vfs tree
Date: Wed, 5 Dec 2018 13:58:41 -0800 [thread overview]
Message-ID: <eae92504-4c1d-2430-4d5b-b5b1f4af45ce@schaufler-ca.com> (raw)
In-Reply-To: <20181205161601.GW2217@ZenIV.linux.org.uk>
On 12/5/2018 8:16 AM, Al Viro wrote:
> On Wed, Dec 05, 2018 at 10:37:56AM +0100, Ondrej Mosnacek wrote:
>
>> I just tested the Q28 branch rebased onto a recent Fedora rawhide
>> kernel (4.20.0-0.rc5.git0.1) and that code seems to be working fine.
Not so good with Smack.
# mount -t tmpfs -o size=512m,smackfsroot=Pop tmpfs /mnt
# attr -S -g SMACK64 /mnt
Attribute "SMACK64" had a 1 byte value for /mnt:
_
#
attr should have reported a 3 byte value "Pop".
prev parent reply other threads:[~2018-12-05 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181127115246.00967523@canb.auug.org.au>
[not found] ` <CAFqZXNs6XTOx2-EQ5P9bK3vPsPby7rzryHPqzqsVD9XsbsG20w@mail.gmail.com>
[not found] ` <20181127225013.133adc7d@canb.auug.org.au>
[not found] ` <CAHC9VhSFSxBc+-O=GQMkiyiQz3S+_ZreicLhsoAuvR-oq2mi6g@mail.gmail.com>
[not found] ` <CAFqZXNuZCof=7CtyMq8JDyAgRmONYRZhhqr6bFVy9-F70-Uwrw@mail.gmail.com>
[not found] ` <CAHC9VhRthWKfgYenGq6Az+jVQ+76wCeBhBcMyo9zZwv+nBhy3A@mail.gmail.com>
[not found] ` <20181129235130.GI2217@ZenIV.linux.org.uk>
2018-11-30 0:57 ` linux-next: manual merge of the selinux tree with the vfs tree Casey Schaufler
2018-11-30 1:27 ` Al Viro
2018-11-30 1:36 ` Al Viro
[not found] ` <CAFqZXNu_=MxcX5jvX4y=5nrCqi7_btOGVccbH1NZ=xm3TGvaYQ@mail.gmail.com>
[not found] ` <CAFqZXNv642dfT0PpB0M7sO5J90cAM7Luv0A8nX7JtEXqw=yu1w@mail.gmail.com>
[not found] ` <CAFqZXNuv_mF8Yt50J3giZjxzZX_WwCOePZeEtmR-G_m+vRyPrQ@mail.gmail.com>
[not found] ` <20181203215639.GV2217@ZenIV.linux.org.uk>
[not found] ` <CAFqZXNvSOzyhnTUxF2mP4BTFMVQ8H1uh-Yyn2fH2K=4yRDX-tQ@mail.gmail.com>
[not found] ` <20181205161601.GW2217@ZenIV.linux.org.uk>
2018-12-05 21:58 ` Casey Schaufler [this message]
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=eae92504-4c1d-2430-4d5b-b5b1f4af45ce@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).