From: David Miller <davem@davemloft.net>
To: julia@diku.dk
Cc: jdike@karaya.com, wangchen@cn.fujitsu.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/3] Fix use of skb after netif_rx
Date: Mon, 10 Dec 2007 17:15:00 -0800 (PST) [thread overview]
Message-ID: <20071210.171500.07031787.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0712092101160.11165@ask.diku.dk>
From: Julia Lawall <julia@diku.dk>
Date: Sun, 9 Dec 2007 21:02:31 +0100 (CET)
> From: Julia Lawall <julia@diku.dk>
>
> Recently, Wang Chen submitted a patch
> (d30f53aeb31d453a5230f526bea592af07944564) to move a call to netif_rx(skb)
> after a subsequent reference to skb, because netif_rx may call kfree_skb on
> its argument. The same problem occurs in some other drivers as well.
>
> This was found using the following semantic match.
> (http://www.emn.fr/x-info/coccinelle/)
...
> Signed-off-by: Julia Lawall <julia@diku.dk>
Patch applied, thanks.
prev parent reply other threads:[~2007-12-11 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 20:02 [PATCH 1/3] Fix use of skb after netif_rx Julia Lawall
2007-12-10 18:03 ` Jeff Dike
2007-12-11 1:15 ` David Miller [this message]
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=20071210.171500.07031787.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jdike@karaya.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangchen@cn.fujitsu.com \
/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