mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
	Roland McGrath <roland@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: fix leakage of -ERESTARTSYS to userland
Date: Thu, 31 May 2007 09:48:16 +0900	[thread overview]
Message-ID: <87wsypakdr.wl%takeuchi_satoru@jp.fujitsu.com> (raw)
In-Reply-To: <20070530191849.GB85@tv-sign.ru>

At Wed, 30 May 2007 23:18:49 +0400,
Oleg Nesterov wrote:
> 
> On 05/30, Andrew Morton wrote:
> > On Tue, 29 May 2007 22:44:35 +0400
> > Oleg Nesterov <oleg@tv-sign.ru> wrote:
> > 
> > > --- t/drivers/char/n_tty.c~	2007-04-05 12:18:26.000000000 +0400
> > > +++ t/drivers/char/n_tty.c	2007-05-28 10:57:58.000000000 +0400
> > > @@ -1191,6 +1191,7 @@ static int job_control(struct tty_struct
> > >  			    is_current_pgrp_orphaned())
> > >  				return -EIO;
> > >  			kill_pgrp(task_pgrp(current), SIGTTIN, 1);
> > > +			set_thread_flag(TIF_SIGPENDING);
> > >  			return -ERESTARTSYS;
> > >  		}
> > >  	}
> > 
> > Are there other callers of kill_pgrp() which have the same problem?
> 
> Hopefully no.
> 
> > Perhaps we should have a kill_pgrp_self() which takes care of doing
> > this, rather than open-coding it.  Something with a comment which
> > explains what's going on ;)
> 
> This set_thread_flag(TIF_SIGPENDING) is "connected" to "return -ERESTARTSYS",
> not to kill_pgrp(), imho the new helper is not so suitable.
> 
> Perhaps it makes sense to add the comment into include/linux/errno.h, to
> explain that -ERESTART... codes are only valid when signal_pending() == true.

Like this?

Satoru

---
Add comment for errnos related to restart syscall to avoid the leakage of
kernel only errnos.

Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>

Index: linux-2.6.22-rc3/include/linux/errno.h
===================================================================
--- linux-2.6.22-rc3.orig/include/linux/errno.h	2007-04-26 12:08:32.000000000 +0900
+++ linux-2.6.22-rc3/include/linux/errno.h	2007-05-31 09:44:27.000000000 +0900
@@ -5,7 +5,11 @@
 
 #ifdef __KERNEL__
 
-/* Should never be seen by user programs */
+/*
+ * Should never be seen by user programs. Please note that returing
+ * `ERESTART*' errnos when `!signal_pending()' incurs the leakage of these
+ * errnos to user space.
+ */
 #define ERESTARTSYS	512
 #define ERESTARTNOINTR	513
 #define ERESTARTNOHAND	514	/* restart if no handler.. */

  reply	other threads:[~2007-05-31  0:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 18:44 Oleg Nesterov
2007-05-30 18:05 ` Andrew Morton
2007-05-30 19:18   ` Oleg Nesterov
2007-05-31  0:48     ` Satoru Takeuchi [this message]
2007-05-31  1:08       ` Roland McGrath
2007-05-31  1:55         ` Satoru Takeuchi
2007-05-31  7:40           ` Roland McGrath

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=87wsypakdr.wl%takeuchi_satoru@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    --cc=roland@redhat.com \
    /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®