linux-kernel - Re: [PATCH] Update email address for stable patch submission

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]

Date:	Tue, 18 Oct 2011 10:49:02 -0400
From:	Josh Boyer <jwboyer@...hat.com>
To:	Greg KH <greg@...ah.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	"David S. Miller" <davem@...emloft.net>,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] Update email address for stable patch submission

On Tue, Oct 18, 2011 at 07:13:50AM -0700, Greg KH wrote:
> On Tue, Oct 18, 2011 at 02:58:52AM -0400, Christoph Hellwig wrote:
> > On Mon, Oct 17, 2011 at 09:16:39PM -0400, Josh Boyer wrote:
> > > The stable@...nel.org email address has been replaced with the
> > > stable@...r.kernel.org mailing list.  Change the stable kernel rules to
> > > reference the new list instead of the semi-defunct email alias.
> > 
> > Does this mean it already stopped working?  I recently sent pathces
> > there but neither got an ACK nor a bounce or similar.
> 
> It should have bounced.

It doesn't bounce anymore.  The alias exists again, and it forwards to
the vger list.  However, there are some configuration issues where some
kind of email loop (I'm very fuzzy on the details) can/does occur
between the two, and as far as I know anything getting sent to
stable@...nel.org is getting dropped on the floor.

> But, if you put a "Cc: stable@...nel.org" in the patch, I'm still
> picking that up properly when it goes to Linus's tree.
> 
> If I haven't responded to any patches you have sent to stable@ already,
> please resend them to stable@...r.kernel.org and cc: me to ensure it
> gets here.

As Christoph said, that doesn't help patches that need to be
retro-actively submitted.  I sent a couple last night before I
remembered the problems, hence this patch.

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