netdev - Re: [PATCH net] tg3: Fix deadlock in tg3_change

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: <52F43219.8010809@broadcom.com>
Date:	Thu, 6 Feb 2014 17:08:41 -0800
From:	Nithin Nayak Sujir <nsujir@...adcom.com>
To:	David Miller <davem@...emloft.net>
CC:	<netdev@...r.kernel.org>, <david.vrabel@...rix.com>,
	<stable@...r.kernel.org>, <mchan@...adcom.com>
Subject: Re: [PATCH net] tg3: Fix deadlock in tg3_change_mtu()

On 02/06/2014 04:54 PM, David Miller wrote:
>
> Networking patches should never be CC:'d to -stable.  And you should
> never add the:
>
> Cc: <stable@...r.kernel.org>
>
> tag to networking commit messages.
>
> Instead, after the "---" delimiter, you should kindly request that
> I queue up that patch for stable, and why.  I handle networking
> stable submissions on my own.
>

I apologize. For some reason, I was under the impression that the rule applied 
to core networking and not driver-only changes. Will keep this in mind.

How should I proceed with this? Should I resubmit?

Also, I'm a little confused as to why my previous submissions to net with stable 
Cc'd were ok. E.g. commit 375679104ab3ccfd18dcbd7ba503734fb9a2c63a - "tg3: 
Expand 4g_overflow_test workaround to skb fragments of any size.". Did it slip 
by because I didn't have the < >?

Thanks,
Nithin.
--
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