From: Lennart Poettering <mzxreary@0pointer.de>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Colin Walters <walters@verbum.org>,
Denys Vlasenko <vda.linux@googlemail.com>,
systemd-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [systemd-devel] [PATCH 2/2] coredump: Handle programs with spaces in COMM
Date: Fri, 3 May 2013 17:08:24 +0200 [thread overview]
Message-ID: <20130503150824.GB24114@tango.0pointer.de> (raw)
In-Reply-To: <20130501164246.GA7647@redhat.com>
On Wed, 01.05.13 18:42, Oleg Nesterov (oleg@redhat.com) wrote:
> On 04/30, Colin Walters wrote:
> >
> > On Tue, 2013-04-30 at 19:47 +0200, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Tue, Apr 30, 2013 at 01:12:19PM -0400, Colin Walters wrote:
> > > > This patch makes systemd-coredump handle processes that have
> > > > whitespace in their COMM fields.
> > > >
> > > > fs/coredump.c when given %e (as systemd-coredump uses), will end up
> > > > joining the process arguments into a string (along with the other
> > > > fields), then will split the entire thing up on whitespace, and use
> > > > it as the arguments to the coredump pipe handler.
> > > > ---
> > > That's a workaround for a bug in the kernel. I think it makes sense, but
> > > it'd be nice to fix the kernel too.
>
> I wouldn't say this is bug... at least this is expected.
>
> Sure, it is possible to rewrite format_corename/argv_split interaction,
> but this is a bit painful and I am not sure it worth the trouble.
It sounds really wrong to first merge this into one string and then
split it up again. It sounds much more sensible to instead just pass the
string array around all the time. What's the reason to make this one
string first?
Lennart
--
Lennart Poettering - Red Hat, Inc.
next prev parent reply other threads:[~2013-05-03 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1367341939.6959.1.camel@localhost>
[not found] ` <20130430174731.GC3394@in.waw.pl>
[not found] ` <1367349331.6959.80.camel@localhost>
2013-05-01 16:42 ` [systemd-devel] [PATCH 2/2] coredump: Handle programs with spaces in COMM Oleg Nesterov
2013-05-03 15:08 ` Lennart Poettering [this message]
2013-05-05 0:04 ` Colin Walters
2013-05-09 18:10 ` Oleg Nesterov
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=20130503150824.GB24114@tango.0pointer.de \
--to=mzxreary@0pointer.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=systemd-devel@lists.freedesktop.org \
--cc=vda.linux@googlemail.com \
--cc=walters@verbum.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