lkml.org 
[lkml]   [2006]   [Aug]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [RFC][PATCH 2/9] deadlock prevention core
    From
    From: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Date: Wed, 09 Aug 2006 16:07:20 +0200

    > Hmm, what does sk_buff::input_dev do? That seems to store the initial
    > device?

    You can run grep on the tree just as easily as I can which is what I
    did to answer this question. It only takes a few seconds of your
    time to grep the source tree for things like "skb->input_dev", so
    would you please do that before asking more questions like this?

    It does store the initial device, but as Thomas tried so hard to
    explain to you guys these device pointers in the skb are transient and
    you cannot refer to them outside of packet receive processing.

    The reason is that there is no refcounting performed on these devices
    when they are attached to the skb, for performance reasons, and thus
    the device can be downed, the module for it removed, etc. long before
    the skb is freed up.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-08-10 02:01    [W:4.392 / U:0.068 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site