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: <c91f52c8-c7de-e555-a184-b62d39665b9f@gmail.com>
Date:   Mon, 23 Apr 2018 15:36:03 -0700
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Emanuele <e.emanuelegiuseppe@...il.com>,
        Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: dev_loopback_xmit parameters



On 04/23/2018 02:40 PM, Emanuele wrote:
> Hello,
> 
> I don't know if this is the right place where to ask, but I was wondering why the dev_loopback_xmit function defined in /net/core/dev.c takes struct net * and struct sock *  as parameters. They are never used, so I believe passing only the struct  sk_buff * should be enough.
> 

Look at net/ipv6/ip6_output.c where NF_HOOK() uses dev_loopback_xmit().

> In addition, it would like to know where I can read what is and how to set a skb dst_entry, since I don't really understand it.
> 
> Thanks a lot,
> 
> Emanuele
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ