linux-kernel - RE: which signal is sent to freeze process?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Jul 2007 21:52:24 +0200
From:	Manfred Spraul <manfred@...orfullife.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	linux-kernel@...r.kernel.org,
	"Agarwal, Lomesh" <lomesh.agarwal@...el.com>,
	Nigel Cunningham <nigel@...el.suspend2.net>
Subject: RE: which signal is sent to freeze process?

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?

--
    Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/