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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED 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 70928C433B4 for ; Thu, 1 Apr 2021 20:59:42 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id ECC536105A for ; Thu, 1 Apr 2021 20:59:41 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org ECC536105A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=mit.edu Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 5A4E56B00B9; Thu, 1 Apr 2021 16:59:41 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 52D9F6B00BB; Thu, 1 Apr 2021 16:59:41 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 37FF46B00BC; Thu, 1 Apr 2021 16:59:41 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0212.hostedemail.com [216.40.44.212]) by kanga.kvack.org (Postfix) with ESMTP id 1588D6B00B9 for ; Thu, 1 Apr 2021 16:59:41 -0400 (EDT) Received: from smtpin40.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id C0B9B824C454 for ; Thu, 1 Apr 2021 20:59:40 +0000 (UTC) X-FDA: 77985014520.40.56ACE74 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by imf15.hostedemail.com (Postfix) with ESMTP id 008F4A0003A5 for ; Thu, 1 Apr 2021 20:59:39 +0000 (UTC) Received: from cwcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 131KxKua015368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 1 Apr 2021 16:59:21 -0400 Received: by cwcc.thunk.org (Postfix, from userid 15806) id 3E36F15C3A90; Thu, 1 Apr 2021 16:59:20 -0400 (EDT) Date: Thu, 1 Apr 2021 16:59:20 -0400 From: "Theodore Ts'o" To: Roy Yang Cc: Al Viro , keescook@chromium.org, akpm@linux-foundation.org, alex.popov@linux.com, ard.biesheuvel@linaro.org, catalin.marinas@arm.com, corbet@lwn.net, david@redhat.com, elena.reshetova@intel.com, Alexander Potapenko , Jann Horn , kernel-hardening@lists.openwall.com, linux-arm-kernel@lists.infradead.org, linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, luto@kernel.org, mark.rutland@arm.com, peterz@infradead.org, rdunlap@infradead.org, rppt@linux.ibm.com, tglx@linutronix.de, vbabka@suse.cz, will@kernel.org, x86@kernel.org Subject: Re: [PATCH v8 0/6] Optionally randomize kernel stack offset each syscall Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 008F4A0003A5 X-Stat-Signature: dugkrydn9giphhjjm3mkdr6ohf63fu5s Received-SPF: none (mit.edu>: No applicable sender policy available) receiver=imf15; identity=mailfrom; envelope-from=""; helo=outgoing.mit.edu; client-ip=18.9.28.11 X-HE-DKIM-Result: none/none X-HE-Tag: 1617310779-558482 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 Thu, Apr 01, 2021 at 01:49:17PM -0700, Roy Yang wrote: > Thanks Ted, Casey and Al Viro. I am sorry for the inconvenience. > > I tried to follow the instructions listed under > https://lore.kernel.org/lkml/20210330205750.428816-1-keescook@chromium.org/ > using git-send-email > > Thought that will reply to the original thread with the original > subject . Let me know what I can do to correct this to avoid > confusion. It did chain to the original thread; that's how I was able to figure out the context. However, it looks like in your reply, you set the subject to be: [PATCH] Where we are for this patch? And the problem is if someone had deleted the original e-mail chain --- for example, optimizing the kernel stack is not one of the subjects that I normally closely track, I had already deleted those e-mail chains. So all I saw (and I suspect all Al saw) was a message with the above subject line, and no context. If you had kept the original subject line, then those of us who mostly focus on file system stuff would have known that it's an area which is covered by other maintainers, and we wouldn't have deleted your query and let someone else respond. Cheers, - Ted P.S. I personally find the use "git-send-email" to reply to be so much of a pain that I just use a non-google.com address to which I can use a traditional threaded mail-reader (such as mutt) and I can send e-mail without having to worry about the DMARC nonsense. :-)