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: <CAMDZJNXno=SuK2bWMm8jt8d7g2BxgJ7daNOk=-j4CurBzKdi_g@mail.gmail.com>
Date:   Fri, 18 Jan 2019 09:43:17 +0800
From:   Tonghao Zhang <xiangxia.m.yue@...il.com>
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     Nicolas Dichtel <nicolas.dichtel@...nd.com>,
        David Miller <davem@...emloft.net>,
        Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH RESEND net-next v2] net: ipv4: allocate ipv4_devconf
 memory for init_net

On Fri, Jan 18, 2019 at 2:00 AM Cong Wang <xiyou.wangcong@...il.com> wrote:
>
> On Thu, Jan 17, 2019 at 3:12 AM Tonghao Zhang <xiangxia.m.yue@...il.com> wrote:
> >
> > so, we should support configuration for user, inherit _init_net_ value or not ?
>
> I already told you to introduce a new proc to control this behavior,
> you ignored my advice... :(
Sorry,  because I can not find the reason that we should  inherit
_init_net, and send that patch.
> I will send out a patch then, as I know what I want. :)
good, please cc to me.
> Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ