linux-kernel - Re: trying to track a change to drivers/isdn/usb-gigaset.c

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: <20070507.034117.115910272.davem@davemloft.net>
Date:	Mon, 07 May 2007 03:41:17 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	tilman@...p.cc
Cc:	linux-kernel@...r.kernel.org, acme@...hat.com,
	netdev@...r.kernel.org
Subject: Re: trying to track a change to drivers/isdn/usb-gigaset.c

From: Tilman Schmidt <tilman@...p.cc>
Date: Mon, 07 May 2007 11:55:06 +0200

[ netdev@...r.kernel.org is the place to discuss kernel networking
  issues, thanks ]

> But I cannot remember seeing that patch via the maintainer
> addresses for ISDN or the Gigaset driver, and the LKML archive
> doesn't seem to have it either.
> 
> Where was that patch discussed? What is its rationale?

This was a wholesale change done across the entire tree, they were all
straightforward transformations that didn't change what the code did.

It was a change done so that we could hide the skb data buffering
details to the point where we could change the protocol header
pointers into 32-bit offsets which saves 4 bytes per such pointer per
protocol header stored in struct sk_buff.

We're not going to notify the maintainer of each of the hundreds of
source files we had to touch in order to pull this off, sorry.

These changes were posted to netdev@...r.kernel.org, they also
sat in Andrew Morton's -mm tree for quite some time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/