From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754636AbcBXCPn (ORCPT ); Tue, 23 Feb 2016 21:15:43 -0500 Received: from terminus.zytor.com ([198.137.202.10]:54102 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753353AbcBXCPm (ORCPT ); Tue, 23 Feb 2016 21:15:42 -0500 User-Agent: K-9 Mail for Android In-Reply-To: <718FE8BC-2CF1-410E-98AF-AD99EAD6E033@zytor.com> References: <1455712566-16727-4-git-send-email-matt@codeblueprint.co.uk> <718FE8BC-2CF1-410E-98AF-AD99EAD6E033@zytor.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: [tip:efi/core] x86/mm/pat: Use _PAGE_GLOBAL bit for EFI page table mappings From: "H. Peter Anvin" Date: Tue, 23 Feb 2016 18:13:40 -0800 To: Linus Torvalds , Andy Lutomirski CC: "Ravi V. Shankar" , Toshi Kani , Brian Gerst , Thomas Gleixner , Ingo Molnar , Sai Praneeth Prakhya , Luis Rodriguez , Andrew Morton , Denys Vlasenko , Matt Fleming , "linux-kernel@vger.kernel.org" , Peter Zijlstra , Borislav Petkov , ricardo.neri@intel.com, Hugh Dickins , Ard Biesheuvel Message-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On February 23, 2016 6:09:19 PM PST, "H. Peter Anvin" wrote: >On February 23, 2016 10:08:06 AM PST, Linus Torvalds > wrote: >>On Tue, Feb 23, 2016 at 9:47 AM, Andy Lutomirski >>wrote: >>> On Feb 23, 2016 1:09 AM, <"tip-bot for Sai Praneeth >>> <tipbot@zytor.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 >> 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==?=@zytor.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. For the record: I implemented escaping only to placate vger's spam filters... -- Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.