On czw, 2014-11-27 at 16:17 +0100, Richard Weinberger wrote: > Am 27.11.2014 um 16:11 schrieb Lukasz Pawelczyk: > > On czw, 2014-11-27 at 16:01 +0100, Richard Weinberger wrote: > >> Am 27.11.2014 um 15:44 schrieb Lukasz Pawelczyk: > >>> True, the last one is 0x80000000. I did not notice that. Thanks for > >>> pointing out. > >> > >> Isn't this CLONE_IO? > > > > Yes, I was merely noticing out loud that it's the last bit of 32bit. > > > > After close look though the 0x00001000 appears to be unused > > This was CLONE_PID. > I'm not sure if we can reuse this. man 2 clone states "It disappeared in Linux 2.5.16.". > Maybe one of the CC'd parties can tell more... Would really like someone to comment on this. I'd like to avoid creating a new syscall at this point. According to clone(2): CLONE_STOPPED has been removed in 2.6.38 and can be reused. CLONE_PID as you mentioned has been removed in 2.5.16 but since 2.3.21 it could only be used by boot process (PID 0). So this was really long time ago and effectively regular user space cannot use it since 2.3.21. -- Lukasz Pawelczyk Samsung R&D Institute Poland Samsung Electronics -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
