Bug 959479 - core_pattern's handling of %e is broken for process names with spaces when coredumps are piped to a process
Summary: core_pattern's handling of %e is broken for process names with spaces when co...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-03 15:20 UTC by Lennart Poettering
Modified: 2014-03-17 18:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-17 18:45:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lennart Poettering 2013-05-03 15:20:07 UTC
Currently, if the kernel generates one command line string from the core pattern (if it is one with a |) and then splits that up again where it finds spaces. This is really broken for %e if a process name contains spaces. (and presumably is broken for %h too).

Userspace shouldn't have to work around this, especially since it really can't if multiple spaces are used one after the other, or if both %e and %h are used in the same command line.

The kernel should properly create a command line as array of strings, so that this can be handled nicely.

Comment 1 Josh Boyer 2013-05-03 15:25:56 UTC
Oleg, I'm sure you're aware of this already on the upstream thread.  I'd suggest just continuing the discussion upstream.

Comment 2 Fedora End Of Life 2013-09-16 13:46:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 3 Justin M. Forbes 2014-02-24 13:56:01 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.13.4-200.fc20.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 4 Justin M. Forbes 2014-03-17 18:45:18 UTC
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.

Comment 5 Oleg Nesterov 2014-03-17 18:52:40 UTC
(In reply to Justin M. Forbes from comment #3)
>
> Please test this kernel
> update and let us know if you issue has been resolved or if it is still
> present with the newer kernel.

No, it was not resolved...

IIRC, I sent the patch upstream but it was ignored. I'll try to resend
when I have time. I agree with Lennart, this doesn't look right even if
the problem is minor.


Note You need to log in before you can comment on or make changes to this bug.