netdev - Re: [RFC 2/2] shrink size of scatterlist on common i386/x86-64

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070706.015417.74747276.davem@davemloft.net>
Date:	Fri, 06 Jul 2007 01:54:17 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rusty@...tcorp.com.au
Cc:	shemminger@...ux-foundation.org, netdev@...r.kernel.org
Subject: Re: [RFC 2/2] shrink size of scatterlist on common i386/x86-64

From: Rusty Russell <rusty@...tcorp.com.au>
Date: Fri, 06 Jul 2007 17:43:46 +1000

> On Thu, 2007-07-05 at 17:15 -0700, David Miller wrote:
> > Also even with the scatterlist idea, we'd still need to do two
> > map calls, one for skb->data and one for the page vector.
> 
> We could make skb->shinfo(skb)->frags[0] the first segment and deprecate
> skb->data and skb->len.
> 
> OK, you can stop hitting me now...

The fly in that ointment is that referencing the backing
page of kmalloc() data is not safe currently, especially
with SLUB.

Jens Axboe ran into this while trying to implement sendfile()
via splice() several weeks ago, it's an ongoing battle that
even C. Lameter is even involved in now :-)
-
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