From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: David Hildenbrand <david@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Karel Zak <kzak@redhat.com>, Linux-MM <linux-mm@kvack.org>,
Michal Hocko <mhocko@kernel.org>, Michal Hocko <mhocko@suse.com>,
mm-commits@vger.kernel.org, ndfont@gmail.com, pbadari@us.ibm.com,
Rafael Wysocki <rafael@kernel.org>,
rcj@linux.vnet.ibm.com, stable <stable@vger.kernel.org>,
steve.scargall@intel.com
Subject: Re: [patch 2/5] drivers/base/memory.c: indicate all memory blocks as removable
Date: Sun, 29 Mar 2020 15:43:54 -0400 [thread overview]
Message-ID: <20200329194354.xrbzlvlbjimy3pzz@chatter.i7.local> (raw)
In-Reply-To: <b80d7cea-a8f7-11c9-66fa-bdc272bdf099@redhat.com>
On Sun, Mar 29, 2020 at 08:03:52PM +0200, David Hildenbrand wrote:
> > Please, David H - whatever you do with email is WRONG.
> >
> > Fix your completely broken email client. Stop doing this.
To butt in uninvited into this conversation, it doesn't look like
there's anything really wrong with what David sends, except for the
quoted-printable formatting, which is probably converted automatically
by one of Red Hat's relay MTAs.
> What I received via the mailing list (e.g., linux-mm@kvack.org)
>
> Message-Id: <20200128093542.6908-1-david@redhat.com>
> MIME-Version: 1.0
> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
> X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4
> Sender: owner-linux-mm@kvack.org
> Precedence: bulk
> X-Loop: owner-majordomo@kvack.org
> List-ID: <linux-mm.kvack.org>
> [...]
> X-Mimecast-Spam-Score: 1
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: quoted-printable
> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4
> [...]
>
> And a lot of this MIME crap.
>
> I have no idea if such a conversion is expected to be done.
In theory, it doesn't really matter, as mail clients are supposed to be
properly undoing all this 7-bit legacy madness. When we run that thread
through "b4 am" to get things back into 8bit, everything looks just
fine. You can try it yourself:
b4 am 20200128093542.6908-1-david@redhat.com
> Unless I am missing something important, the issue is not in mail client
> setup, but there is something in the mailing infrastructure horribly
> messing with my mails. Red Hat has recently switched to Mimecast and
> there have been plenty of issues, maybe this is one of these.
>
> I guess the only thing I can do is sending mails via a different mail
> server / different email address?
It would appear that the workflow Andrew uses to queue up patches from
you isn't expecting quoted-printable formatting, which is why when Linus
gets them, they are mangled.
We would either need to switch Andrew to a set of tools that handle 7bit
legacy formats better, or figure out how you can send things via MTAs
that won't convert from 8bit to quoted-printable. Maybe you can convince
Red Hat to set up their relays to always preserve 8bit?
-K
next prev parent reply other threads:[~2020-03-29 19:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 2:14 incoming Andrew Morton
2020-03-29 2:17 ` [patch 1/5] mm/swapfile.c: move inode_lock out of claim_swapfile Andrew Morton
2020-03-29 2:17 ` [patch 2/5] drivers/base/memory.c: indicate all memory blocks as removable Andrew Morton
2020-03-29 16:46 ` Linus Torvalds
2020-03-29 18:03 ` David Hildenbrand
2020-03-29 18:28 ` Linus Torvalds
2020-03-29 19:11 ` David Hildenbrand
2020-03-29 19:15 ` Linus Torvalds
2020-03-29 19:43 ` Konstantin Ryabitsev [this message]
2020-03-29 19:55 ` Linus Torvalds
2020-03-29 19:56 ` Linus Torvalds
2020-03-30 14:46 ` Konstantin Ryabitsev
2020-03-30 14:54 ` David Hildenbrand
2020-04-01 13:35 ` David Hildenbrand
2020-04-01 15:33 ` Konstantin Ryabitsev
2020-04-01 15:40 ` David Hildenbrand
2020-03-29 2:17 ` [patch 3/5] hugetlb_cgroup: fix illegal access to memory Andrew Morton
2020-03-29 2:17 ` [patch 4/5] mm: fork: fix kernel_stack memcg stats for various stack implementations Andrew Morton
2020-03-29 16:41 ` Linus Torvalds
2020-03-29 2:17 ` [patch 5/5] mm/sparse: fix kernel crash with pfn_section_valid check Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200329194354.xrbzlvlbjimy3pzz@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=kzak@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=ndfont@gmail.com \
--cc=pbadari@us.ibm.com \
--cc=rafael@kernel.org \
--cc=rcj@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=steve.scargall@intel.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).