linux-kernel - Why create_kthread passes SIGCHLD to kernel

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>] [day] [month] [year] [list]

Message-ID: <CA+a=Yy5FkgAK5Cr_qQ7jTSZbWCDA073VJ9b3nVqA9M6J=Sy=iw@mail.gmail.com>
Date:	Wed, 27 Feb 2013 18:37:00 +0800
From:	Peng Tao <lkml.bergwolf@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Why create_kthread passes SIGCHLD to kernel_thread?

Hello,

Looking at do_fork(), it seems that SIGCHLD is used to tell what kind
of trace event to report but kernel_thread() certainly doesn't want
any of it. So what does this SIGCHLD mean for create_kthread?

-- 
Thanks,
Tao
--
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/