From: Ed Cashin <ecashin@coraid.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: aoe: print warning regarding a common reason for dropped transmits
Date: Wed, 24 Oct 2012 18:22:56 +0000 [thread overview]
Message-ID: <590150A2-9672-4046-9160-689F3B6A8048@coraid.com> (raw)
In-Reply-To: <20121023172810.GA12454@elgon.mountain>
On Oct 24, 2012, at 2:26 AM, Dan Carpenter wrote:
> On Tue, Oct 23, 2012 at 01:51:33PM -0500, Ed Cashin wrote:
>> On Oct 23, 2012, at 1:28 PM, Dan Carpenter wrote:
>>
>>> Hello Ed L. Cashin,
>>>
>>> The patch 6fde53abc51d: "aoe: print warning regarding a common reason
>>> for dropped transmits" from Oct 23, 2012, leads to the following
>>> warning:
>>> drivers/block/aoe/aoenet.c:62 tx()
>>> error: 'skb' was already used up by dev_queue_xmit()
>>>
>>> 61) if (dev_queue_xmit(skb) = NET_XMIT_DROP && net_ratelimit())
>>> 62) pr_warn("aoe: packet could not be sent on %s. %s\n",
>>> 63) skb->dev ? skb->dev->name : "netif",
>>> 64) "consider increasing tx_queue_len");
>>>
>>> It's a use after free bug.
By the way, what tool is generating that warning?
Thanks.
--
Ed Cashin
ecashin@coraid.com
prev parent reply other threads:[~2012-10-24 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 17:28 aoe: print warning regarding a common reason for dropped transmits Dan Carpenter
2012-10-23 18:51 ` Ed Cashin
2012-10-24 6:26 ` Dan Carpenter
2012-10-24 18:22 ` Ed Cashin [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=590150A2-9672-4046-9160-689F3B6A8048@coraid.com \
--to=ecashin@coraid.com \
--cc=kernel-janitors@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