All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Veronika Kabatova <vkabatov@redhat.com>
Cc: Linux Stable maillist <stable@vger.kernel.org>,
	Memory Management <mm-qe@redhat.com>,
	Jan Stancek <jstancek@redhat.com>,
	CKI Project <cki-project@redhat.com>
Subject: Re: ❎ FAIL: Stable queue: queue-5.0
Date: Mon, 6 May 2019 14:36:37 +0200	[thread overview]
Message-ID: <20190506123637.GC26360@kroah.com> (raw)
In-Reply-To: <190144458.18224981.1557141968068.JavaMail.zimbra@redhat.com>

On Mon, May 06, 2019 at 07:26:08AM -0400, Veronika Kabatova wrote:
> 
> 
> ----- Original Message -----
> > From: "CKI Project" <cki-project@redhat.com>
> > To: "Linux Stable maillist" <stable@vger.kernel.org>
> > Cc: "Memory Management" <mm-qe@redhat.com>, "Jan Stancek" <jstancek@redhat.com>
> > Sent: Monday, May 6, 2019 1:16:03 PM
> > Subject: ❎ FAIL: Stable queue: queue-5.0
> > 
> > Hello,
> > 
> > We ran automated tests on a patchset that was proposed for merging into this
> > kernel tree. The patches were applied to:
> > 
> >        Kernel repo:
> >        git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> >             Commit: e5b9547b1aa3 - Linux 5.0.13
> > 
> > The results of these automated tests are provided below.
> > 
> >     Overall result: FAILED (see details below)
> >              Merge: OK
> >            Compile: OK
> >              Tests: FAILED
> > 
> 
> Hi,
> 
> we have recently started seeing an mtest06 LTP failure on aarch64. The failure
> is reproducible, as you can see in both reports. Jan Stancek took care of
> debugging it (we weren't sure if it's a test or kernel problem at first) and
> thinks it's a kernel issue.
> 
> You can find his findings and failure log here for more info:
> 
> https://github.com/linux-test-project/ltp/issues/528
> https://lore.kernel.org/linux-mm/1817839533.20996552.1557065445233.JavaMail.zimbra@redhat.com/T/#u

Thanks for the link, hopefully we can get this resolved in Linus's tree
and then we can backport the needed fix here as well.

thanks,

greg k-h

  reply	other threads:[~2019-05-06 12:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 11:16 ❎ FAIL: Stable queue: queue-5.0 CKI Project
2019-05-06 11:26 ` Veronika Kabatova
2019-05-06 12:36   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-02 12:32 CKI Project
2019-05-02 12:39 ` Major Hayden
2019-05-02 14:08   ` Greg KH
2019-04-30 12:32 CKI Project
2019-04-30 12:35 ` Major Hayden
2019-04-30 13:03   ` Sasha Levin
2019-04-30 13:27     ` Greg KH
2019-04-30 13:41       ` Sasha Levin
2019-04-30 14:01         ` Greg KH
2019-04-30 15:17           ` Major Hayden
2019-04-30 15:58             ` Sasha Levin
2019-04-30 18:44               ` Sven Joachim
2019-04-29 13:36 CKI Project
2019-04-29 12:50 CKI Project
2019-04-29 12:38 CKI Project
2019-04-29 12:42 ` Major Hayden
2019-04-29 13:10   ` Greg KH
2019-04-29 12:37 CKI Project
2019-04-04 18:00 CKI Project

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=20190506123637.GC26360@kroah.com \
    --to=greg@kroah.com \
    --cc=cki-project@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=mm-qe@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=vkabatov@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 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.