netdev - Who's allowed to set a skb destructor?

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-next>] [day] [month] [year] [list]

Message-ID: <468B54A6.5090902@ens-lyon.org>
Date:	Wed, 04 Jul 2007 10:04:54 +0200
From:	Brice Goglin <Brice.Goglin@...-lyon.org>
To:	netdev@...r.kernel.org
Subject: Who's allowed to set a skb destructor?

Hi,

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.

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. I
found some old threads about adding support for multiple destructors but
I don't see anything like this in the current kernel.

So, I'd like to have a clear statement about who's allowed to use a
destructor :)

Thanks,
Brice

-
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