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: <20121024150807.82ce2677.akpm@linux-foundation.org>
Date:	Wed, 24 Oct 2012 15:08:07 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ed Cashin <ecashin@...aid.com>
Cc:	dan.carpenter@...cle.com, kernel-janitors@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] aoe: avoid using skb member after dev_queue_xmit

On Wed, 24 Oct 2012 14:26:13 -0400
Ed Cashin <ecashin@...aid.com> wrote:

> After calling dev_queue_xmit it is no longer safe to access the
> members of the skb.
> 
> Reported-by: Dan Carpenter <dan.carpenter@...cle.com>

hm, that was clever.  How did Dan detect this bug?

> --- a/drivers/block/aoe/aoenet.c
> +++ b/drivers/block/aoe/aoenet.c
> @@ -55,12 +55,14 @@ static int
>  tx(void) __must_hold(&txlock)
>  {
>  	struct sk_buff *skb;
> +	struct net_device *ifp;
>  
>  	while ((skb = skb_dequeue(&skbtxq))) {
>  		spin_unlock_irq(&txlock);
> +		ifp = skb->dev;
>  		if (dev_queue_xmit(skb) == NET_XMIT_DROP && net_ratelimit())
>  			pr_warn("aoe: packet could not be sent on %s.  %s\n",
> -				skb->dev ? skb->dev->name : "netif",
> +				ifp ? ifp->name : "netif",
>  				"consider increasing tx_queue_len");
>  		spin_lock_irq(&txlock);
>  	}

Queued as a fix against the not-yet-upstream
aoe-print-warning-regarding-a-common-reason-for-dropped-transmits.patch,
thanks.

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ