From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 4.14 00/46] 4.14.169-stable review
Date: Fri, 31 Jan 2020 04:45:19 -0500 (EST) [thread overview]
Message-ID: <1480601816.5094241.1580463919045.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CA+G9fYvMc73OCXNz_9Ks-GqE828Vd3YFeX_iOrWq3bobGpgUtQ@mail.gmail.com>
----- Original Message -----
> On Wed, 29 Jan 2020 at 14:46, Jan Stancek <jstancek@redhat.com> wrote:
> >
> >
> >
> > ----- Original Message -----
> > > NOTE:
> > > LTP fs test read_all_proc fails intermittently on 4.9 and 4.14 branches.
> >
> > [trim CC list to LTP]
> >
> > Naresh, do you have some examples of these failures?
>
> Yes.
> I have posted the links below.
>
> > Has it started recently or do you see it long-term?
>
> We have seen this from a this test is introduced.
> Not specific to any branch. This failure is intermittent and found on
> multiple trees and branches.
Those look like kernel bugs, but it's hard to see what /proc entries
trigger it.
I've been running v5.5 and read_all_proc for ~24 hours on aarch64,
but so far no crashes.
prev parent reply other threads:[~2020-01-31 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200128135749.822297911@linuxfoundation.org>
2020-01-29 4:53 ` [LTP] [PATCH 4.14 00/46] 4.14.169-stable review Naresh Kamboju
2020-01-29 9:16 ` Jan Stancek
2020-01-29 10:27 ` Naresh Kamboju
2020-01-31 9:45 ` Jan Stancek [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=1480601816.5094241.1580463919045.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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