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
| ||
|
Message-ID: <20170504142432.Horde.g9y26Ryxbtg1EIl_cnsdbbw@gator4166.hostgator.com> Date: Thu, 04 May 2017 14:24:32 -0500 From: "Gustavo A. R. Silva" <garsilva@...eddedor.com> To: Joe Perches <joe@...ches.com> Cc: David Miller <davem@...emloft.net>, kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org, kaber@...sh.net, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [net-ipv4] question about arguments position Quoting Joe Perches <joe@...ches.com>: [] >> > > +/* >> > > + * Ignore the position of the arguments req->id.idiag_dport and >> > > + * req->id.idiag_sport in both calls to inet_lookup() and >> inet6_lookup() >> > > + * functions, once this is a locked in behavior exposed to user space. >> > > + * Changing this will break things for people. >> > > + */ >> > > struct sock *inet_diag_find_one_icsk(struct net *net, >> > > struct inet_hashinfo *hashinfo, >> > > const struct >> inet_diag_req_v2 *req) >> > > >> > >> > Seems sensible. Thanks. >> >> Should I resend it in a full and proper format or it can taken from here? > > If you want it applied, it should be resent as a full patch > with your sign-off. I'll send it shortly. Thanks for clarifying -- Gustavo A. R. Silva
Powered by blists - more mailing lists