linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Ying Han <yinghan@google.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Lee Schermerhorn <lee.schermerhorn@hp.com>,
	Oleg Nesterov <oleg@redhat.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Paul Menage <menage@google.com>,
	Rohit Seth <rohitseth@google.com>
Subject: Re: [PATCH][V6]make get_user_pages interruptible
Date: Wed,  3 Dec 2008 13:17:50 +0900 (JST)	[thread overview]
Message-ID: <20081203131522.1D41.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <604427e00812021957m44549252k21e1b617ba9e78c3@mail.gmail.com>


> > more unfortunately, this patch break kernel compatibility.
> > To read /proc file invoke calling get_user_page().
> > however, "man 2 read" doesn't describe ERESTARTSYS.
> yeah, that seems to be right..
> >
> > IOW, this patch can break /proc reading user application.
> >
> > May I ask why fatal_signal_pending(tsk) is needed ?
> > at least, you need to cc to linux-api@vger.kernel.org IMHO.
> all the problems seems to be caused by the fatal_signal_pending(tsk),
> i can either make the change like
> if (fatal_signal_pending(tsk))
>    return i ? i : EINTR
> 
> or remove the check for fatal_signal_pending(tsk) which is mainly used in
> the case you mentioned above. Afterward, the intial point of the patch is to
> avoid proccess hanging in the mlock (for example) under memory
> pressure while it has SIGKILL pending. Now sounds to me the second option is
> better. any comments?

it seems both reasonable.
in my personal feeling, I like simple removing than EINTR.



> > Am I talking about pointless?
> thanks for comments. :-)

Could you please cc to me at posting v7.
maybe, I can ack.


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2008-12-03  4:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 19:30 Ying Han
2008-12-02 21:26 ` Pekka Enberg
2008-12-02 22:00   ` Ying Han
2008-12-03  2:24 ` KOSAKI Motohiro
2008-12-03  3:57   ` Ying Han
2008-12-03  4:17     ` KOSAKI Motohiro [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=20081203131522.1D41.KOSAKI.MOTOHIRO@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-mm@kvack.org \
    --cc=menage@google.com \
    --cc=oleg@redhat.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=rohitseth@google.com \
    --cc=yinghan@google.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