linux-kernel - Re: [PATCH 0/6] percpu: Implement Preemption checks for __this

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, 15 Oct 2013 10:23:16 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Christoph Lameter <cl@...ux.com>
Cc:	Ingo Molnar <mingo@...nel.org>, David Miller <davem@...emloft.net>,
	tj@...nel.org, akpm@...uxfoundation.org, srostedt@...hat.com,
	linux-kernel@...r.kernel.org, tglx@...utronix.de
Subject: Re: [PATCH 0/6] percpu: Implement Preemption checks for __this_cpu
 operations V4

On Mon, Oct 14, 2013 at 07:02:29PM +0000, Christoph Lameter wrote:
> On Mon, 14 Oct 2013, Peter Zijlstra wrote:
> 
> > > Most kernel developers tend to use 'git send-email' to send patches to
> > > lkml, and that method is working pretty reliably.
> >
> > I always use quilt mail, it typically adds a reference to the 0/0 email
> > and ensures the time of each msg is one second ahead of the previous one
> > to ensure order is correct.
> 
> Yes that I also what I expected to happen and what always happened in the
> past.
> 
> > I've no idea how Christoph managed to wreck this, but normally quilt
> > mail DTRT (as opposed to git send-email which used to default to
> > endlessly deep threads -- got fixed in 1.6 or 1.7 or thereabouts).
> 
> Well this is going through Amazon cloud email which may be wrecking
> things. Had a number of issues already with messages being delayed etc. I
> can try to revert to my home setup and see if that fixes things.

So your 0/x has:

Message-ID: <00000141a8a7ea27-4ab5f822-e15f-4789-a5cf-f313c402a901-000000@...il.amazonses.com>
Date: Fri, 11 Oct 2013 17:54:38 +0000

1/x has:

Message-Id: <00000141a8a7eb8a-370733b2-d230-4567-96e1-74c028998bff-000000@...il.amazonses.com>
References: <20131011175518.634285474@...ux.com>
Date: Fri, 11 Oct 2013 17:54:39 +0000

2/x has:

Message-Id: <00000141a8a7ecfe-16f29a32-36eb-4588-a87e-6ba8e0b3a91c-000000@...il.amazonses.com>
References: <20131011175518.634285474@...ux.com>
Date: Fri, 11 Oct 2013 17:54:39 +0000

3/x has:

Message-Id: <00000141a8a7fa10-998dfc65-4d07-4d83-999e-31cb0056cfb3-000000@...il.amazonses.com>
References: <20131011175518.634285474@...ux.com>
Date: Fri, 11 Oct 2013 17:54:42 +0000


So yes, Amazon is fucking with your email, not only the msgids
(obviously) but also the date stamps are not what quilt generates.

If someone from Amazon is reading this; please comment.
--
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/