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, 22 May 2014 21:21:55 +0100
From:	Jim Baxter <>
To:	David Miller <>
CC:	<>, <>,
	<>, <>,
	<>, <>,
	<>, <>
Subject: Re: skbuff truesize incorrect.

On 22/05/14 20:21, David Miller wrote:
> From: Jim Baxter <>
> Date: Thu, 22 May 2014 20:07:41 +0100
>> My questions are:
>> 1) Which buffer size does truesize represent, is it the total buffer or
>> just the data related to the relevant skb?
>> 2) If truesize is for the skb it is contained within should it be
>> updated during the call to skb_trim?
>> 3) Why does the truesize default to 32960?
> skb->truesize represents the total amount of memory that the SKB
> is holding up.
> This is the size of the sk_buff metadata plus all of the buffer
> memory.
> For example, if the buffer is using 16K buffer yet only 1500 of it is
> actually used for the packet, 16K is what should be plugged into the
> equation to compute truesize.
> Otherwise it would be easy to compromise a system by sending lots of 1
> byte packets to a socket, even though the actual memory consumed by
> that "1 byte" packet is significantly larger.

OK, so it is the value of the memory that has been allocated for the SKB.
If there are multiple clones for an skb all pointing at the same data,
will that distort the memory used when they all have the same truesize?

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

Powered by blists - more mailing lists