From: Miklos Szeredi <miklos@szeredi.hu>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: SElinux list <selinux@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Paul Moore <paul@paul-moore.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: ❌ FAIL: Test report for kernel 5.7.0-f359287.cki (mainline.kernel.org)
Date: Tue, 2 Jun 2020 14:37:05 +0200 [thread overview]
Message-ID: <CAJfpegvF+vJ9DAmAD7mTcuT2pvPMC1foWs9yuTFjSmkkQ6w3KQ@mail.gmail.com> (raw)
In-Reply-To: <CAFqZXNtdwMAiu65Ne0HLyY5JO-QK=cqT-OF_=6mdnGVo8XA9Eg@mail.gmail.com>
On Tue, Jun 2, 2020 at 11:27 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> I haven't tried to reproduce/debug it locally yet. Just posting here
> as a heads-up. The last known good commit is c2b0fc847f31 ("Merge tag
> 'for-linus' of git://git.armlinux.org.uk/~rmk/linux-arm"), first known
> failing is f359287765c0 ("Merge branch 'from-miklos' of
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs").
Likely culprit is:
a3c751a50fe6 ("vfs: allow unprivileged whiteout creation")
And the change of behavior vs. LSM are expected due to the fact that
now whiteout creation calls the security_inode_mknod() whereas before
the patch that hook wasn't called. This was discussed here:
https://lore.kernel.org/linux-fsdevel/20200409212859.GH28467@miu.piliscsaba.redhat.com/
Thanks,
Miklos
prev parent reply other threads:[~2020-06-02 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cki.F472C8C7F2.AWNOVIOTU4@redhat.com>
2020-06-02 9:27 ` Fwd: ❌ FAIL: Test report for kernel 5.7.0-f359287.cki (mainline.kernel.org) Ondrej Mosnacek
2020-06-02 12:37 ` Miklos Szeredi [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=CAJfpegvF+vJ9DAmAD7mTcuT2pvPMC1foWs9yuTFjSmkkQ6w3KQ@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.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).