[lkml]   [2007]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: dst_ifdown breaks infiniband?
    > Quoting Alexey Kuznetsov <>:
    > Subject: Re: dst_ifdown breaks infiniband?
    > Hello!
    > > infiniband sets parm->neigh_destructor, and I search for a way to prevent
    > > this destructor from being called after the module has been unloaded.
    > > Ideas?
    > It must be called in any case to update/release internal ipoib structures.

    I don't think there's a problem.
    All we do in destructor is release the ipoib_neigh resource.
    And on device unregister we release all resources anyway.

    > The idea is to move call of parm->neigh_destructor from neighbour destructor
    > to the moment when it is unhashed, right after n->dead is set.
    > infiniband is the only user (atm clip uses it too, but that use is obviously
    > dummy), so that nobody will be harmed.

    This might work. Could you post a patch to better show what you mean to do?

    > But ipoib will have to check for validity of skb->dst->neighbour before
    > attempt to reinitialize private data on dead (n->dead != 0) neighbour.

    We set a flag before unregister_netdev and test it in start_xmit so
    that's covered I think.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-03-19 16:15    [W:0.021 / U:1.700 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site