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]
Date:	Tue, 05 Jun 2007 08:34:54 -0400
From:	jamal <>
To:	Jens Axboe <>
Subject: Re: [PATCH][RFC] network splice receive

On Tue, 2007-05-06 at 14:20 +0200, Jens Axboe wrote:

> > 
> > 0000 1800 4ff3 937f e000 6381 7275 0008
> > 
> > Perhaps that hex pattern rings a bell with someone intimate with the
> > networking. The remaining wrong bytes don't seem to have anything in
> > common.
> Ok, the source mac address is 00:18:F3:4F:7F:93 and the destination is
> 00:E0:81:63:75:72 which are the middle 12 bytes of the 16.

It appears you may have endianness issues and perhaps a 16 bit
mis-offset. the 0008 at the end looks like a swapped 0x800 which
is the ethernet type for IPV4.

> Hope that helps someone clue me in as to which network part is reusing
> the data. Do I need to 'pin' the sk_buff until the pipe data has been
> consumed?

I would worry about the driver level first - likely thats where your
corruption is.


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