[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <718FE8BC-2CF1-410E-98AF-AD99EAD6E033@zytor.com>
Date: Tue, 23 Feb 2016 18:09:19 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>
CC: "Ravi V. Shankar" <ravi.v.shankar@...el.com>,
Toshi Kani <toshi.kani@...com>,
Brian Gerst <brgerst@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Sai Praneeth Prakhya <sai.praneeth.prakhya@...el.com>,
Luis Rodriguez <mcgrof@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Denys Vlasenko <dvlasenk@...hat.com>,
Matt Fleming <matt@...eblueprint.co.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>, ricardo.neri@...el.com,
Hugh Dickins <hughd@...gle.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>
Subject: Re: [tip:efi/core] x86/mm/pat: Use _PAGE_GLOBAL bit for EFI page table mappings
On February 23, 2016 10:08:06 AM PST, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>On Tue, Feb 23, 2016 at 9:47 AM, Andy Lutomirski <luto@...capital.net>
>wrote:
>> On Feb 23, 2016 1:09 AM, <"tip-bot for Sai Praneeth
>> <tipbot@...or.com>"@zytor.com> wrote:
>>
>> Something's wrong with tip-bot. This should say:
>
>Yeah, there's about 50 tipbot emails that are just pure garbage. They
>don't even show in my mailers, because they are so corrupt.
>
>The raw email has some insane encoding too, for reasons I can't begin
>to fathom.
>
>This is an example of what tipbot *used* to send out in the headers:
>
> From: tip-bot for Dave Hansen <tipbot@...or.com>
> Subject: [tip:mm/pkeys] mm/core, x86/mm/pkeys:
> Add execute-only protection keys support
>
>and this is what it sent out in the last crazy setup:
>
>From:
>=?UTF-8?B?dGlwLWJvdCBmb3IgU2FpIFByYW5lZXRoIDx0aXBib3RAenl0b3IuY29tPg==?=@...or.com
> Subject:
>=?UTF-8?B?W3RpcDplZmkvY29yZV0geDg2L21tL3BhdDogVXNlIF9QQUdFX0dMT0JBTCBiaXQ=?=
> =?UTF-8?B?IGZvciBFRkkgcGFnZSB0YWJsZSBtYXBwaW5ncw==?=
>
>despite neither subject nor author having any odd characters in them.
>
>(That's just two header lines - all the other ones are corrupt in
>similar ways too)
>
>The thing that seems to really make things unreadable is that the
>content encoding lines have this corrupted quoting too:
>
> MIME-Version: =?UTF-8?B?MS4w?=
> Content-Transfer-Encoding: =?UTF-8?B?OGJpdA==?=
> Content-Type: =?UTF-8?B?dGV4dC9wbGFpbjsgY2hhcnNldD1VVEYtOA==?=
> Content-Disposition: =?UTF-8?B?aW5saW5l?=
>
>rather than what it *should* be:
>
> Content-Transfer-Encoding: 8bit
> Content-Type: text/plain; charset=UTF-8
> Content-Disposition: inline
>
>so the whole header situation is a complete mess.
>
>The fact that you can see the patch at all and comment on the
>*contents* of the email is impressive. My mail reader just says "this
>is garbage" and shows me nothing at all.
>
> Linus
Someone decided to change the behavior of the Perl module I used for encoding to unconditionally encode almost everything, claiming some kind of strict RFC compliance. An upgrade caused this to happen. I have switched modules to one which should do what one actually wants.
--
Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.
Powered by blists - more mailing lists