Roland, Linus, I'm sorry for being offtopic, but there is something I can't understand from the very beginning, when TIF_RESTORE_SIGMASK was introduced. On 03/28, Linus Torvalds wrote:Yes! Why do we need any flag? It looks a bit ugly. Isn't it better to introduce the new magic ERESTART_XXX which means ERESTARTNOHAND + restore-sigmask ? We only need this flag as an implicit parameter to the arch dependent do_signal() which we can't call directly, and thus it must imply TIF_SIGPENDING, and it is not valid after do_signal() (should be cleared). This all looks like ERESTART_ magic, why should we add something else ? See also http://marc.info/?l=linux-kernel&m=113734458516136 Of course, probably it is too late to change the implementation even if I am right, the question is: what I am missed? Oleg. --
| Al Boldi | Re: [ck] Re: [ANNOUNCE] RSDL completely fair starvation free interactive cpu sched... |
| Ingo Molnar | Re: [patch] sched_clock(): cleanups |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
| Denys Vlasenko | [PATCH 1/2] bnx2: factor out gzip unpacker |
