From: Sasha Levin <sashal@kernel.org>
To: Samuel Dionne-Riel <samuel@dionne-riel.com>
Cc: Michal Hocko <mhocko@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Richard Weinberger <richard.weinberger@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
graham@grahamc.com, Oleg Nesterov <oleg@redhat.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: Userspace regression in LTS and stable kernels
Date: Fri, 15 Feb 2019 13:02:42 -0500 [thread overview]
Message-ID: <20190215180242.GC10616@sasha-vm> (raw)
In-Reply-To: <CAN1fySWnazf3Z7tCnK1p10+XYV1zGfBO-YqoE3LNoOfKpPO3zQ@mail.gmail.com>
On Fri, Feb 15, 2019 at 11:18:30AM -0500, Samuel Dionne-Riel wrote:
>I'm sorry to interject here, but the issue was reported on the
>Kernel.org Bugzilla on February 2nd
>
> - https://bugzilla.kernel.org/show_bug.cgi?id=202497
>
>In the interest of better communication, if the need arises again, how
>should bugs in the RC kernels be reported so they (1) are spotted by
>the right maintainers and (2) not backported even though they were
>reported as causing breaking changes?
Sadly our bugzilla is rarely used, even though the information in that
particular bug report is perfect.
Maybe pinging LKML and stable@vger.kernel.org would be enough, specially
if you know that it's a stable commit that caused the regression.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-02-15 18:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 17:57 Userspace regression in LTS and stable kernels Samuel Dionne-Riel
2019-02-13 18:00 ` Samuel Dionne-Riel
2019-02-13 23:36 ` Richard Weinberger
2019-02-14 0:41 ` Samuel Dionne-Riel
2019-02-14 0:54 ` Kees Cook
2019-02-14 1:27 ` Samuel Dionne-Riel
2019-02-14 1:35 ` Kees Cook
2019-02-14 3:16 ` Samuel Dionne-Riel
2019-02-14 0:41 ` Kees Cook
2019-02-14 17:56 ` Linus Torvalds
2019-02-14 20:20 ` Andrew Morton
2019-02-15 7:00 ` Greg Kroah-Hartman
2019-02-15 7:13 ` Greg Kroah-Hartman
2019-02-15 9:10 ` Michal Hocko
2019-02-15 9:20 ` Greg Kroah-Hartman
2019-02-15 9:42 ` Michal Hocko
2019-02-15 15:19 ` Sasha Levin
2019-02-15 15:52 ` Michal Hocko
2019-02-15 16:18 ` Samuel Dionne-Riel
2019-02-15 18:02 ` Sasha Levin [this message]
2019-02-15 18:00 ` Sasha Levin
2019-02-18 12:56 ` Michal Hocko
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=20190215180242.GC10616@sasha-vm \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=graham@grahamc.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=oleg@redhat.com \
--cc=richard.weinberger@gmail.com \
--cc=samuel@dionne-riel.com \
--cc=stable@vger.kernel.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 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.