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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16869.1392917423@warthog.procyon.org.uk>
Date:	Thu, 20 Feb 2014 17:30:23 +0000
From:	David Howells <dhowells@...hat.com>
To:	David Miller <davem@...emloft.net>
Cc:	dhowells@...hat.com, hannes@...essinduktion.org,
	netdev@...r.kernel.org
Subject: Re: Getting a NIC's MTU size

David Miller <davem@...emloft.net> wrote:

> > One further question: If I want to get the MTU size of the NIC through
> > which packets will go to get to a particular peer, can I do:
> 
> As has been suggested or at least hinted to by others, you have to use
> the route dst's device pointer.

So I gather.  My query was intended to be about the safety of accessing the
dst->dev pointer.  Can I just dereference it?  Or do I need to take a lock or
use RCU?

David
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ