On Wed, Jan 1, 2014 at 6:30 PM, Ryusuke Konishi <[email protected]> wrote: > On Wed, 1 Jan 2014 16:30:48 +0900, Hitoshi Mitake wrote: >> Current daemonize() function of cleanerd call _exit(2) only once during its >> process of becoming a daemon process. But in the linux environment, a daemon >> process should call _exit(2) twice for ensuring not being a session leader. >> If a >> process don't do that, unexpected SIGHUP can be sent to the process (though >> it >> happens rarely). The signal would be confusing event for cleanerd of nilfs. >> This >> patch removes this potential problem. >> >> Signed-off-by: Hitoshi Mitake <[email protected]> >> --- >> sbin/cleanerd/cleanerd.c | 10 ++++++++++ >> 1 file changed, 10 insertions(+) >> >> diff --git a/sbin/cleanerd/cleanerd.c b/sbin/cleanerd/cleanerd.c >> index 26067bd..edfa083 100644 >> --- a/sbin/cleanerd/cleanerd.c >> +++ b/sbin/cleanerd/cleanerd.c >> @@ -676,6 +676,16 @@ static int daemonize(int nochdir, int noclose, int >> nofork) >> >> /* umask(0); */ >> >> + /* for ensuring I'm not a session leader */ >> + if (!nofork) { >> + pid = fork(); >> + if (pid < 0) >> + return -1; >> + else if (pid != 0) >> + /* parent */ >> + _exit(0); >> + } >> + > > I tried your patch, but the cleaner daemon still was a session leader.
Thanks for your review and testing. > > This turned out because nilfs_cleanerd is usually executed by > mount.nilfs2 program with the nofork option (-n). > > To fix this problem, it looks like the above !nofork check of the > second fork() should be removed even though it becomes confusing. In > that case, we may need to add some explanation why fork() should be > called even if nofork is specified. For ensuring not being a session leader, fork() should be called twice. Removing the second condition of !nofork is not enough. For this purpose, we need to remove both of the conditions of !nofork. BTW, what is an intention of "-n" option of cleanerd? I read the code of nilfs_launch_cleanerd() but couldn't understand the reason of this option. If this option is aiming to reduce calling of fork(), I think this can be eliminated. Calling 3 fork()s (1 in mount.nilfs2, 2 in cleanerd) would be acceptable. Thanks, Hitoshi -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
