LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linuxppc-dev@lists.ozlabs.org, Jonathan Corbet <corbet@lwn.net>
Subject: Linux 4.16: Reported regressions as of Monday, 2018-02-19 (Was: Linux 4.16-rc2)
Date: Mon, 19 Feb 2018 14:58:43 +0100	[thread overview]
Message-ID: <8af706ec-e1a8-fe16-e11b-6422ac845239@leemhuis.info> (raw)
In-Reply-To: <CA+55aFwDnBq9V6TVbc82DzVYpf-ELF7UcYzHuY0ei1Xjnob+0A@mail.gmail.com>

Hi! Find below my first regression report for Linux 4.16. It lists 2
regressions I'm currently aware of.

Are you aware of any other regressions? Then please let me know by mail
(a simple bounce or forward to the email address is enough!).

For details see http://bit.ly/lnxregtrackid And please tell me if there
is anything in the report that shouldn't be there.

Ciao, Thorsten

P.S.: Sorry, I didn't find spare time to work on regression reporting
and related issues during the 4.15 cycle. I also have a huge todo list
after the regression tracking discussion during maintainer and kernel
summit last fall. I will try to work on that that sooner or later; that
in the end will change nearly all the aspects of regression tracking is
done currently. But that will take some time (which I struggle to find
currently :-/ ) to realize, so for this cycle  I'm continuing to do
regression reports like I used to do them.

== Current regressions ==

Debian kernel package tool make-kpkg stalls indefinitely during kernel
build due to commit "kconfig: remove check_stdin()"
Status: stalled after some discussions
Note: Shouldn't be a problem to back this one out either if it turns out
to cause massive amounts of pain in practice I guess, even if it's the
Debian tools doing something weird.
Reported: 2018-02-12
https://marc.info/?l=linux-kernel&m=151846414807219
Cause: d2a04648a5dbc3d1d043b35257364f0197d4d868
Linux-Regression-ID: 2fd778

DM Regression: read() returns data when it shouldn't
Status: Developers are looking into it
Reported: 2018-02-14
https://marc.info/?l=linux-kernel&m=151861337518109&w=2
Cause: 18a25da84354c6bb655320de6072c00eda6eb602
Linux-Regression-ID: 9e195f

           reply	other threads:[~2018-02-19 14:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CA+55aFwDnBq9V6TVbc82DzVYpf-ELF7UcYzHuY0ei1Xjnob+0A@mail.gmail.com>]

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=8af706ec-e1a8-fe16-e11b-6422ac845239@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=torvalds@linux-foundation.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