public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: aoe: print warning regarding a common reason for dropped transmits
Date: Wed, 24 Oct 2012 06:26:08 +0000	[thread overview]
Message-ID: <20121024062608.GE20754@mwanda> (raw)
In-Reply-To: <20121023172810.GA12454@elgon.mountain>

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.
> 
> Thanks for the report.  The Documentation/SubmittingPatches says,
> 
>     Please note that this tag should not be added without the
>     reporter's permission, especially if the problem was not
>     reported in a public forum.
> 
> Which surprisingly means that I should ask you for permission before
> mentioning you in a "Reported-by:" tag, even though you reported it in
> a public forum.  So is it OK?

Yes.  Reported-by credits are always welcome.

I think that documentation is wrong.  If the email was reported to a
mailing list or bugzilla then we normally add a reported-by by
default.

regards,
dan carpenter


  parent reply	other threads:[~2012-10-24  6:26 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 [this message]
2012-10-24 18:22 ` Ed Cashin

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=20121024062608.GE20754@mwanda \
    --to=dan.carpenter@oracle.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