From: Hideo AOKI <haoki@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>, haoki@redhat.com
Cc: netdev <netdev@vger.kernel.org>, David Miller <davem@davemloft.net>
Subject: Re: [RFC] [NET] [0/2] pskb_expand_head() bugfix
Date: Fri, 28 Mar 2008 21:01:04 -0400 [thread overview]
Message-ID: <47ED94D0.7060902@redhat.com> (raw)
In-Reply-To: <20080327001349.GA8569@gondor.apana.org.au>
Hello,
Herbert Xu wrote:
> On Wed, Mar 26, 2008 at 04:47:35PM -0400, Hideo AOKI wrote:
>> Or, should I simply add truesize calculation after
>> pskb_expand_head() calls which change truesize?
>
> Can you do an audit first and tell us how many sites are currently
> buggy?
Sure. I find 24 spots.
Here is the list of caller functions which don't update turesize
or do update turesize without alignment. But I don't confirm yet
if alignment is really needed in each case.
* macro: 1
- Missing truesize update
linux/skbuff.h:1369: __skb_cow()
* kernel: 1
- Missing alignment:
audit.c:1121: audit_expand()
* ipv4: 5
- Missing truesize update:
ipvs/ip_vs_app.c:597: ip_vs_skb_replace()
netfilter/nf_nat_helper.c:119: enlarge_skb()
netfilter.c:72: ip_route_me_harder()
netfilter.c:105: ip_xfrm_me_harder()
- Missing alignment:
ipcomp.c:63: ipcomp_decompress()
* core: 5
- Missing truesize update:
skbuff.c:741: skb_realloc_headroom()
skbuff.c:840: skb_pad()
skbuff.c:979: __pskb_pull_tail()
skbuff.c:2393: skb_cow_data()
pktgen.c:2402: process_ipsec()
* netlink: 1
- Missing alignment:
af_netlink.c:838: netlink_trim()
* ipv6: 1
- Missing alignment:
ipcomp6.c:106: ipcomp6_input()
* netfilter: 1
- Missing alignment:
xt_TCPMSS.c:122: tcpmss_mangle_packet()
* max80211: 8
- Missing truesize update:
tx.c:1246: ieee80211_master_start_xmit()
tx.c:1503: ieee80211_subif_start_xmit()
wpa.c:103: ieee80211_tx_h_michael_mic_add()
wpa.c:207: tkip_encrypt_skb()
wpa.c:458: ccmp_encrypt_skb()
wep.c:99: ieee80211_wep_add_iv()
rx.c:146: ieee80211_rx_monitor()
rx.c:905: ieee80211_rx_h_defragment()
* xfrm: 1
- Missing truesize update:
xfrm_output.c:30: xfrm_state_check_space()
Many thanks,
Hideo
--
Hitachi Computer Products (America) Inc.
next prev parent reply other threads:[~2008-03-29 1:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 18:39 [RFC] [NET] [0/2] pskb_expand_head() bugfix Hideo AOKI
2008-03-25 18:41 ` [RFC PATCH] [NET] [1/2] revert audit_expand() Hideo AOKI
2008-03-25 18:41 ` [RFC PATCH] [NET] [2/2] pskb_expand_head() updates truesize Hideo AOKI
2008-03-25 23:55 ` [RFC] [NET] [0/2] pskb_expand_head() bugfix Herbert Xu
2008-03-26 20:47 ` Hideo AOKI
2008-03-27 0:13 ` Herbert Xu
2008-03-29 1:01 ` Hideo AOKI [this message]
2008-03-27 23:49 ` David Miller
2008-03-29 1:14 ` Hideo AOKI
2008-03-27 23:48 ` David Miller
2008-03-29 1:02 ` Hideo AOKI
2008-03-29 1:11 ` David Miller
2008-03-29 1:21 ` Hideo AOKI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47ED94D0.7060902@redhat.com \
--to=haoki@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).