netdev - Re: [patch v2 1/1] fix error handle in ip_mc_add

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: <1322003302.4977.3.camel@barry.pixelworks.com>
Date:	Wed, 23 Nov 2011 07:08:21 +0800
From:	Jun Zhao <mypopydev@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	eric.dumazet@...il.com, netdev@...r.kernel.org,
	dlstevens@...ibm.com
Subject: Re: [patch v2 1/1] fix error handle in ip_mc_add_src()

On Tue, 2011-11-22 at 16:22 -0500, David Miller wrote:
> From: Jun Zhao <mypopydev@...il.com>
> Date: Tue, 22 Nov 2011 00:05:16 +0800
> 
> > from: Jun Zhao <mypopydev@...il.com>
> > 
> > When add sources to interface failure, need to roll back the sfcount[MODE] 
> > to before state. We need to match it corresponding. 
> > 
> > Acked-by: David L Stevens <dlstevens@...ibm.com>
> > Acked-by: Eric Dumazet <eric.dumazet@...il.com>
> > Signed-off-by: Jun Zhao <mypopydev@...il.com>
> 
> Please use an appropriate prefix in your subject line after the
> closing "]" bracket.  For example, something like "ipv4: " for this
> specific patch is fine.
> 
> Your patch has also been corrupted by your email client, it turned tab
> characters into spaces amongst other things.  Please correct this,
> email a test patch to yourself, and make absolutely sure you are able
> to successfully apply it before you retry submitting your fix here.
> 
> Thank you.

Ok, I will double-check this according to your comments, after that,
re-submit the patch, Tks.


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html