From: Jan Stancek <jstancek@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: alsa-devel@alsa-project.org, Memory Management <mm-qe@redhat.com>,
Linux Stable maillist <stable@vger.kernel.org>,
Jaroslav Kysela <jkysela@redhat.com>,
CKI Project <cki-project@redhat.com>,
LTP Mailing List <ltp@lists.linux.it>
Subject: Re: [alsa-devel] ❌ FAIL: Test report for kernel 5.3.9-rc1-dfe283e.cki (stable)
Date: Mon, 4 Nov 2019 09:28:10 -0500 (EST) [thread overview]
Message-ID: <1341418315.10342806.1572877690830.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191104135135.GA2162401@kroah.com>
----- Original Message -----
> On Mon, Nov 04, 2019 at 08:35:51AM -0500, Jan Stancek wrote:
> >
> >
> > ----- Original Message -----
> > >
> > > Hello,
> > >
> > > We ran automated tests on a recent commit from this kernel tree:
> > >
> > > Kernel repo:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > > Commit: dfe283e9fdac - Linux 5.3.9-rc1
> > >
> > > The results of these automated tests are provided below.
> > >
> > > Overall result: FAILED (see details below)
> > > Merge: OK
> > > Compile: OK
> > > Tests: FAILED
> > >
> > > All kernel binaries, config files, and logs are available for download
> > > here:
> > >
> > > https://artifacts.cki-project.org/pipelines/262380
> > >
> > > One or more kernel tests failed:
> > >
> > > x86_64:
> > > ❌ LTP lite
> > >
> >
> > Not a 5.3 -stable regression.
> >
> > Failure comes from test that sanity checks all /proc files by doing
> > 1k read from each. There are couple issues it hits wrt. snd_hda_*.
> >
> > Example reproducer:
> > dd if=/sys/kernel/debug/regmap/hdaudioC0D3-hdaudio/access of=out.txt
> > count=1 bs=1024 iflag=nonblock
>
> That's not a proc file :)
Right. It's same test that's used for /proc too.
>
> > It's slow and triggers soft lockups [1]. And it also requires lot
> > of memory, triggering OOMs on smaller VMs:
> > 0x0000000024f0437b-0x000000001a32b1c8 1073745920 seq_read+0x131/0x400
> > pages=262144 vmalloc vpages N0=262144
> >
> > I'm leaning towards skipping all regmap entries in this test.
> > Comments are welcomed.
>
> Randomly poking around in debugfs is a sure way to cause crashes and
> major problems. Also, debugfs files are NOT stable and only for
> debugging and should never be enabled on "real" systems.
>
> So what exactly is the test trying to do here?
It's (unprivileged) user trying to open/read anything it can (/proc, /sys)
to see if that triggers anything bad.
It can run as privileged user too, which was the case above.
[1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/fs/read_all/read_all.c
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-04 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cki.1210A7ECB0.BD9Q3APV4K@redhat.com>
2019-11-04 13:35 ` [alsa-devel] ❌ FAIL: Test report for kernel 5.3.9-rc1-dfe283e.cki (stable) Jan Stancek
2019-11-04 13:51 ` Greg KH
2019-11-04 14:28 ` Jan Stancek [this message]
2019-11-04 14:59 ` Greg KH
2019-11-04 15:25 ` Jan Stancek
2019-11-04 16:30 ` Greg KH
2019-11-04 17:02 ` Jan Stancek
2019-11-04 20:32 ` Greg KH
2019-11-07 11:05 ` [alsa-devel] [LTP] " Richard Palethorpe
2019-11-05 8:15 ` [alsa-devel] " Takashi Iwai
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=1341418315.10342806.1572877690830.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=alsa-devel@alsa-project.org \
--cc=cki-project@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkysela@redhat.com \
--cc=ltp@lists.linux.it \
--cc=mm-qe@redhat.com \
--cc=stable@vger.kernel.org \
/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).