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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 05 Jul 2007 04:07:07 -0700
From:	Divy Le Ray <>
To:	Andi Kleen <>
CC:	Brice Goglin <>,
Subject: Re: Who's allowed to set a skb destructor?

Andi Kleen wrote:
> Brice Goglin <> writes:
>> I am trying to understand whether I can setup a skb destructor in my
>> code (which is basically a protocol above dev_queue_xmit() and co). From
>> what I see in many parts in the current kernel code, the "protocol" (I
>> mean, the one who actually creates the skb) may setup a destructor.
> The socket layer generally needs it for its own accounting.
> Unless you never pass it up you can't use it.
>> However, I also see some places where some low-level drivers might be
>> using a destructor too , without apparently checking whether an upper
>> layer already uses one. For instance, write_ofld_wr() in cxgb3/sge.c.
> Likely a bug. Normally that should not slip past code review.


The destructor method is set and used for skbs originating from the RDMA 
driver sitting above cxgb3.

The patch introducing this code was discussed at the time.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists