Re: [PATCH? 3/3] move daemonized kernel threads into the swapper's session

[email protected] (Eric W. Biederman) writes:


> Hmm.  I wonder if we could ensure kernel_thread always
> returns a global pid_t, and then reallocate the struct
> pid for the task we have just daemonized so that it only
> has a single pid in the init_pid_ns.

Well we can't reallocate the struct pid, if anyone was using
it we would have problems, but we can certainly remove all
pid_t values except for those in the init_pid_ns.

We definitely have some serious issues with kernel_thread
and signal sending though.

Eric

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

---

• References:
  • [PATCH? 3/3] move daemonized kernel threads into the swapper's session
    • From: Oleg Nesterov <[email protected]>
  • Re: [PATCH? 3/3] move daemonized kernel threads into the swapper's session
    • From: [email protected] (Eric W. Biederman)

• Prev by Date: Re: [PATCHv4 5/6] Allow setting O_NONBLOCK flag for new sockets
• Next by Date: Re: 2.6.24-rc3-mm1
• Previous by thread: Re: [PATCH? 3/3] move daemonized kernel threads into the swapper's session
• Next by thread: [PATCH 2/3] teach set_special_pids() to use struct pid
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]