From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org, "Agarwal,
Lomesh" <lomesh.agarwal@intel.com>,
Nigel Cunningham <nigel@nigel.suspend2.net>
Subject: Re: which signal is sent to freeze process?
Date: Mon, 23 Jul 2007 22:11:14 +0200 [thread overview]
Message-ID: <200707232211.15543.rjw@sisk.pl> (raw)
In-Reply-To: <46A506F8.2020206@colorfullife.com>
On Monday, 23 July 2007 21:52, Manfred Spraul wrote:
> Rafael wrote:
> > On Monday, 23 July 2007 20:38, Agarwal, Lomesh wrote:
> > > The other problem I am facing that read from socket returns with ENODATA
> > > when resuming. any ideas?
> >
> > It's of similar kind: the system call checks signal_pending(current) and exit
> > with an error if that's true.
> >
> > Well, I'm afraid we can't place try_to_freeze() in every system call that
> > does something like that ...
> >
> I don't understand why the poll() system call returns to user space.
> poll() uses ERESTARTNOHAND, thus it should not return to user space.
> Any ideas why ERESTARTNOHAND doesn't work?
Well, look at the code in fs/select.c:do_poll() . If signal_pending(current)
is true, the main loop breaks and count is returned to do_sys_poll(). If
zero is returned and signal_pending(current) is still true, do_sys_poll()
returns -EINTR.
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
next prev parent reply other threads:[~2007-07-23 20:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 19:52 which signal is sent to freeze process? Manfred Spraul
2007-07-23 20:11 ` Rafael J. Wysocki [this message]
2007-07-23 20:09 ` Manfred Spraul
2007-07-24 18:48 ` Manfred Spraul
2007-07-25 19:19 ` Rafael J. Wysocki
2007-07-26 21:12 ` Agarwal, Lomesh
2007-07-31 7:55 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2007-07-18 23:42 Agarwal, Lomesh
2007-07-19 2:18 ` Nigel Cunningham
2007-07-19 4:09 ` Agarwal, Lomesh
2007-07-19 4:59 ` Nigel Cunningham
2007-07-19 21:06 ` Agarwal, Lomesh
2007-07-19 22:02 ` Rafael J. Wysocki
2007-07-19 22:19 ` Nigel Cunningham
2007-07-19 23:22 ` Agarwal, Lomesh
2007-07-20 11:24 ` Rafael J. Wysocki
2007-07-20 18:07 ` Agarwal, Lomesh
2007-07-20 22:10 ` Rafael J. Wysocki
2007-07-23 18:38 ` Agarwal, Lomesh
2007-07-23 19:25 ` Rafael J. Wysocki
2007-07-23 19:31 ` Agarwal, Lomesh
2007-07-24 16:54 ` Pavel Machek
2007-07-23 20:57 ` Agarwal, Lomesh
2007-07-23 21:50 ` Rafael J. Wysocki
2007-07-23 22:18 ` Agarwal, Lomesh
2007-07-24 9:44 ` Rafael J. Wysocki
2007-07-19 22:02 ` Rafael J. Wysocki
2007-07-25 13:41 ` Pavel Machek
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=200707232211.15543.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lomesh.agarwal@intel.com \
--cc=manfred@colorfullife.com \
--cc=nigel@nigel.suspend2.net \
/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