netdev - Re: Getting a NIC's MTU size

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: <20140220.134504.889753387361360927.davem@davemloft.net>
Date:	Thu, 20 Feb 2014 13:45:04 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	dhowells@...hat.com
Cc:	hannes@...essinduktion.org, netdev@...r.kernel.org
Subject: Re: Getting a NIC's MTU size

From: David Howells <dhowells@...hat.com>
Date: Thu, 20 Feb 2014 17:30:23 +0000

> 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?

If the dst is valid and you have a reference to it, dst->dev is good.
--
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