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] [day] [month] [year] [list]
Message-ID: <CAMArcTX6tGkUSik9+HCo0hrmdp2P273YF44ihNmeMEVbP3UxuA@mail.gmail.com>
Date:   Wed, 19 Dec 2018 17:03:20 +0900
From:   Taehee Yoo <ap420073@...il.com>
To:     David Miller <davem@...emloft.net>
Cc:     Netdev <netdev@...r.kernel.org>,
        Daniel Borkmann <daniel@...earbox.net>, ast@...nel.org
Subject: Re: [PATCH net 1/2] net: bpfilter: restart bpfilter_umh when error occurred

On Wed, 19 Dec 2018 at 07:51, David Miller <davem@...emloft.net> wrote:
>
> 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?
>

This idea is clear and I will try to make an infrastructure code
to clean up when UMH type process is killed.

Thanks a lot for the suggestion!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ