From: Paul Wise <pabs3@bonedaddy.net>
To: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Jakub Wilk <jwilk@jwilk.net>, Neil Horman <nhorman@tuxdriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.2 57/59] coredump: split pipe command whitespace before expanding template
Date: Wed, 07 Aug 2019 09:41:46 +0800 [thread overview]
Message-ID: <c835c71b722c3df3d11e7b7f8fd65bbd7da0d482.camel@bonedaddy.net> (raw)
In-Reply-To: <20190806213319.19203-57-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
On Tue, 2019-08-06 at 17:33 -0400, Sasha Levin wrote:
> From: Paul Wise <pabs3@bonedaddy.net>
>
> [ Upstream commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03 ]
The patch changes the behaviour of the interface between the Linux
kernel and userspace core dump handlers. The previous behaviour was
unlikely to be depended on by any core dump handler but it is still a
behaviour change, so I think it would be best to keep it out of the
stable branches and would prefer to have folks encounter the change as
Linux distros etc roll out 5.3 and later into their dev releases.
We discussed this on #kernelnewbies a while ago and gregkh agreed that
it should stew a while longer before reaching any stable releases.
In addition if it gets backported to stable releases, my patch for
core(5) from man-pages will have to get more complicated :)
--
bye,
pabs
https://bonedaddy.net/pabs3/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-07 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190806213319.19203-1-sashal@kernel.org>
2019-08-06 21:33 ` [PATCH AUTOSEL 5.2 57/59] coredump: split pipe command whitespace before expanding template Sasha Levin
2019-08-07 1:41 ` Paul Wise [this message]
2019-08-18 1:48 ` Sasha Levin
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=c835c71b722c3df3d11e7b7f8fd65bbd7da0d482.camel@bonedaddy.net \
--to=pabs3@bonedaddy.net \
--cc=akpm@linux-foundation.org \
--cc=jwilk@jwilk.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=sashal@kernel.org \
--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 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).