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-next>] [day] [month] [year] [list]
Message-ID: <eb1bf67b-7f38-a3b5-4974-6ee1d198887f@gmail.com>
Date:   Mon, 23 Apr 2018 23:40:20 +0200
From:   Emanuele <e.emanuelegiuseppe@...il.com>
To:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: dev_loopback_xmit parameters

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.

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