From: Paul Wise <pabs3@bonedaddy.net>
To: Matthew Ruffell <matthew.ruffell@canonical.com>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Neil Horman <nhorman@tuxdriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jakub Wilk <jwilk@jwilk.net>
Subject: Re: [PATCH 0/1] coredump: Fix null pointer dereference when kernel.core_pattern is "|"
Date: Sat, 22 Feb 2020 22:17:14 +0800 [thread overview]
Message-ID: <645fcbdfdd1321ff3e0afaafe7eccfd034e57748.camel@bonedaddy.net> (raw)
In-Reply-To: <20200220051015.14971-1-matthew.ruffell@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Thu, 2020-02-20 at 18:10 +1300, Matthew Ruffell wrote:
> A user was setting their kernel.core_pattern to "|" to disable coredumps
Hmm, that doesn't seem to be the right way to do that :)
> and encountered the following null pointer dereference
Thanks for forwarding that. I've bounced your mails to a few extra
folks, please include them in CC in future. Neil last touched the
coredump pipe stuff before me, Jakub reported the spaces in
core_pattern issue and Andrew merged my patch.
The patch seems like a reasonable approach but I don't have much
experience with Linux kernel internals.
--
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:[~2020-02-22 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 5:10 Matthew Ruffell
2020-02-20 5:10 ` [PATCH 1/1] " Matthew Ruffell
2020-02-22 14:17 ` Paul Wise [this message]
2020-03-09 22:34 ` [PATCH 0/1] " Matthew Ruffell
2020-03-14 0:28 ` Paul Wise
2020-03-14 21:35 ` Sudip Mukherjee
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=645fcbdfdd1321ff3e0afaafe7eccfd034e57748.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=matthew.ruffell@canonical.com \
--cc=nhorman@tuxdriver.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®