public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Richard Weinberger <richard@nod.at>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC] coredump: Ensure that the coredump helper has stdout and stderr
Date: Thu, 04 Oct 2012 13:07:09 +0200	[thread overview]
Message-ID: <506D6DDD.6050405@nod.at> (raw)
In-Reply-To: <1348849971-23412-1-git-send-email-richard@nod.at>

On 28.09.2012 18:32, Richard Weinberger wrote:
> Currently only stdin is available in the coredump helper process.
> If the process opens a file and then issues a printf(),
> printf() will write to that opened file instead to a console.
>
> Therefore open /dev/console and create fd 1 and 0 as init/main.c does.
> sys_close(0) is only needed if sys_open() succeeds.
> Before this patch it was in vain and returned always -EBADF because nobody
> opened fd 0.
>
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
>   fs/exec.c | 8 +++++++-
>   1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/fs/exec.c b/fs/exec.c
> index 574cf4d..2912fec 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -2079,7 +2079,13 @@ static int umh_pipe_setup(struct subprocess_info *info, struct cred *new)
>
>   	cp->file = files[1];
>
> -	sys_close(0);
> +	/* Ensure that the process has stdout and stderr */
> +	if (sys_open((const char __user *) "/dev/console", O_RDWR, 0) == 0) {
> +		sys_dup(0);
> +		sys_dup(0);
> +		sys_close(0);
> +	}
> +
>   	fd_install(0, files[0]);
>   	spin_lock(&cf->file_lock);
>   	fdt = files_fdtable(cf);
>

Ping?

      reply	other threads:[~2012-10-04 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28 16:32 [PATCH] [RFC] coredump: Ensure that the coredump helper has stdout and stderr Richard Weinberger
2012-10-04 11:07 ` Richard Weinberger [this message]

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=506D6DDD.6050405@nod.at \
    --to=richard@nod.at \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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