linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: CKI Project <cki-project@redhat.com>,
	Linux Stable maillist <stable@vger.kernel.org>,
	Milos Malik <mmalik@redhat.com>,
	Jeff Bastian <jbastian@redhat.com>,
	Major Hayden <major@redhat.com>, Xiaowu Wu <xiawu@redhat.com>,
	Rachel Sibley <rasibley@redhat.com>,
	David Arcari <darcari@redhat.com>,
	Miklos Szeredi <mszeredi@redhat.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: 💥 PANICKED: Test report for kernel 5.7.5-d1c48db.cki (stable-queue)
Date: Mon, 22 Jun 2020 18:20:39 -0400	[thread overview]
Message-ID: <20200622222039.GO1931@sasha-vm> (raw)
In-Reply-To: <CAFqZXNtj8aBpsHNXDcPsP26Xp3Fumx9e4-=dvOdATSGw6cxV3w@mail.gmail.com>

On Mon, Jun 22, 2020 at 11:23:32PM +0200, Ondrej Mosnacek wrote:
>On Mon, Jun 22, 2020 at 10:59 PM CKI Project <cki-project@redhat.com> wrote:
>> Hello,
>>
>> We ran automated tests on a recent commit from this kernel tree:
>>
>>        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>>             Commit: d1c48dba15e7 - pinctrl: qcom: ipq6018 Add missing pins in qpic pin group
>>
>> The results of these automated tests are provided below.
>>
>>     Overall result: FAILED (see details below)
>>              Merge: OK
>>            Compile: OK
>>              Tests: PANICKED
>>
>> All kernel binaries, config files, and logs are available for download here:
>>
>>   https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/06/22/607452
>>
>> One or more kernel tests failed:
>>
>>     s390x:
>>       selinux-policy: serge-testsuite
>>      ❌ stress: stress-ng
>>       Podman system integration test - as root
>>
>>     ppc64le:
>>       selinux-policy: serge-testsuite
>>       Podman system integration test - as root
>>
>>     aarch64:
>>       Podman system integration test - as root
>>       selinux-policy: serge-testsuite
>>
>>     x86_64:
>>       Podman system integration test - as root
>>       selinux-policy: serge-testsuite
>
>It seems the panics are caused by this commit:
>https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/fs?h=linux-5.7.y&id=7bdb075348e33d757bd8cdf017a255a090e87b8f
>
>Apparently, the "if (flags & ~(O_ACCMODE | O_LARGEFILE))" check is
>being hit during mount(2):
>https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/tree/fs/overlayfs/util.c?h=d1c48db#n465

I'll drop it for now, thanks!

-- 
Thanks,
Sasha

      reply	other threads:[~2020-06-22 22:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cki.F024F9B69C.ZR0DRUTWUW@redhat.com>
2020-06-22 21:23 ` 💥 PANICKED: Test report for kernel 5.7.5-d1c48db.cki (stable-queue) Ondrej Mosnacek
2020-06-22 22:20   ` Sasha Levin [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=20200622222039.GO1931@sasha-vm \
    --to=sashal@kernel.org \
    --cc=cki-project@redhat.com \
    --cc=darcari@redhat.com \
    --cc=jbastian@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=major@redhat.com \
    --cc=mmalik@redhat.com \
    --cc=mszeredi@redhat.com \
    --cc=omosnace@redhat.com \
    --cc=rasibley@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=xiawu@redhat.com \
    /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).