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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181218.145146.244782972476250812.davem@davemloft.net>
Date:   Tue, 18 Dec 2018 14:51:46 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     ap420073@...il.com
Cc:     netdev@...r.kernel.org, daniel@...earbox.net, ast@...nel.org
Subject: Re: [PATCH net 1/2] net: bpfilter: restart bpfilter_umh when error
 occurred

From: Taehee Yoo <ap420073@...il.com>
Date: Mon, 17 Dec 2018 16:31:04 +0900

> But I don't know how cleanup callback is invoked when
> bpfilter_umh process is killed.

I am suggesting that a new piece of generic infrastructure might
be needed, but it would need to be carefully designed.

The task_struct would get a piece of state, and at exit() time
the kernel would check that state and use it to invoke exit()
time cleanups for UMH type processes.

Is the idea clearer now?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ