From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5543DC43331 for ; Sun, 29 Mar 2020 18:04:10 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id E329520774 for ; Sun, 29 Mar 2020 18:04:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="ZYZwf5y5" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E329520774 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 4F1AA6B0010; Sun, 29 Mar 2020 14:04:09 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 4A0BF6B0032; Sun, 29 Mar 2020 14:04:09 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 392AB6B0036; Sun, 29 Mar 2020 14:04:09 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0039.hostedemail.com [216.40.44.39]) by kanga.kvack.org (Postfix) with ESMTP id 217AB6B0010 for ; Sun, 29 Mar 2020 14:04:09 -0400 (EDT) Received: from smtpin05.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id D658C181AC9BF for ; Sun, 29 Mar 2020 18:04:08 +0000 (UTC) X-FDA: 76649173776.05.wind55_70bc143cfa04 X-HE-Tag: wind55_70bc143cfa04 X-Filterd-Recvd-Size: 7042 Received: from us-smtp-delivery-74.mimecast.com (us-smtp-delivery-74.mimecast.com [216.205.24.74]) by imf33.hostedemail.com (Postfix) with ESMTP for ; Sun, 29 Mar 2020 18:04:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1585505047; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZxhBLF6botxgoIFtRAoStDWDXAmoSPUdiuvVxOV9ZXY=; b=ZYZwf5y58Ccf3FKTVuZq1X3l9FDAddGKH8e3bPs6ksJJCfcHLfYO48uOcs3qEDzxJYkWrE NYkS6mPIlhYAu4jmSVuGQwui1Xhqr0EUtbpCIfYMDXRkRzOlh8ilRkylQ02HvBgbVHuIgc 9y+hDAHlDKpMdqje7b6X8UVDYM3bgug= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-191-qkLuSjyxM2eIdRdq4PsWmA-1; Sun, 29 Mar 2020 14:03:59 -0400 X-MC-Unique: qkLuSjyxM2eIdRdq4PsWmA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D82BA100551A; Sun, 29 Mar 2020 18:03:56 +0000 (UTC) Received: from [10.36.112.50] (ovpn-112-50.ams2.redhat.com [10.36.112.50]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5465260BEC; Sun, 29 Mar 2020 18:03:53 +0000 (UTC) Subject: Re: [patch 2/5] drivers/base/memory.c: indicate all memory blocks as removable To: Linus Torvalds , Andrew Morton Cc: Dan Williams , Greg Kroah-Hartman , Heiko Carstens , Karel Zak , Linux-MM , Michal Hocko , Michal Hocko , mm-commits@vger.kernel.org, ndfont@gmail.com, pbadari@us.ibm.com, Rafael Wysocki , rcj@linux.vnet.ibm.com, stable , steve.scargall@intel.com References: <20200328191456.4fc0b9ca86780f26c122399e@linux-foundation.org> <20200329021719.MBKzW0xSl%akpm@linux-foundation.org> From: David Hildenbrand Organization: Red Hat GmbH Message-ID: Date: Sun, 29 Mar 2020 20:03:52 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 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: On 29.03.20 18:46, Linus Torvalds wrote: > Please, David H - whatever you do with email is WRONG. > > Fix your completely broken email client. Stop doing this. I'm really sorry this happened again - but I am afraid it's not my email client that's broken :( I've been using bare "git format-patch" + "git send-email" to send out patches for years now, so I don't see what's wrong about that. Now, I took a look at what arrived in my mail box (via cc) without doing round trips through the RH mailing infrastructure and what arrived via the mailing list: What I received via CC (without anybody messing with my mail content): Message-Id: <20200128093542.6908-1-david@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 [...] And none of that "=" MIME crap. 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: [...] 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. > > On Sat, Mar 28, 2020 at 7:17 PM Andrew Morton wrote: >> >> From: David Hildenbrand >> [...] >> According to Nathan Fontenot, DLPAR on powerpc is nowadays no longer >> driven from userspace via the drmgr command (powerpc-utils). Nowadays >> it's managed in the kernel - including onlining/offlining of memory >> blocks - triggered by drmgr writing to /sys/kernel/dlpar. So the >> affected legacy userspace handling is only active on old kernels. Only ve= >> ry >> old versions of drmgr on a new kernel (unlikely) might execute slower - >> totally acceptable. >> >> With CONFIG_MEMORY_HOTREMOVE, always indicating "removable" should not >> break any user space tool. We implement a very bad heuristic now. Withou= >> t >> CONFIG_MEMORY_HOTREMOVE we cannot offline anything, so report >> "not removable" as before. > > Notice the bogus MIME line continuation left-overs? > > [...] Only ve= > ry > > and > > [...] Withou= > t > > is just completely wrong. Yes, absolutely broken. > You either have a completely broken email client that doesn't handle > MIME at all - get rid of it - or you're then dealing with raw mbox > data in a completely broken manner without handling MIME wrapping. Again, just using git send-email :/ > > I can't figure out _what_ you're doing wrong, but the pattern is clear > by now: it's not Andrew (although Andrew should check explanations > better!), since it _only_ happens with patches from David Hildenbrand. > > Fix your workflow. Because it's broken. Let's have a look at some stuff I sent out during the last weeks: https://lkml.kernel.org/r/20200319131221.14044-1-david@redhat.com Already the cover letter looks horrible: https://lore.kernel.org/linux-hyperv/20200319131221.14044-1-david@redhat.com/raw And *again* does not match at all what I received directly via cc in my mail box (== what I expect was sent via "git send-email"). Even the patch content has been partially converted https://lore.kernel.org/linux-hyperv/20200319131221.14044-2-david@redhat.com/raw 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? I'll double check if any other patches still queued in -next are similarly broken. I guess so. -- Thanks, David / dhildenb