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=-10.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 A7C7AC433E7 for ; Sun, 18 Oct 2020 07:22:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 781892222B for ; Sun, 18 Oct 2020 07:22:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726305AbgJRHWs (ORCPT ); Sun, 18 Oct 2020 03:22:48 -0400 Received: from verein.lst.de ([213.95.11.211]:39359 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725275AbgJRHWr (ORCPT ); Sun, 18 Oct 2020 03:22:47 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id D0B6F68B02; Sun, 18 Oct 2020 09:22:43 +0200 (CEST) Date: Sun, 18 Oct 2020 09:22:43 +0200 From: Christoph Hellwig To: Linus Torvalds Cc: Pavel Machek , Ian Kent , Ondrej Mosnacek , Christoph Hellwig , kernel list , autofs@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Borislav Petkov , the arch/x86 maintainers , Peter Anvin Subject: Re: autofs: use __kernel_write() for the autofs pipe writing causes regression in -next was Re: 5.9.0-next-20201015: autofs oops in update-binfmts Message-ID: <20201018072243.GA15356@lst.de> References: <20201016123530.GA30444@duo.ucw.cz> <20201017100234.GA3797@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 17, 2020 at 11:05:06AM -0700, Linus Torvalds wrote: > On Sat, Oct 17, 2020 at 3:02 AM Pavel Machek wrote: > > > > Bad Linus! > > Christ people. > > The bug is in linux-next, not in mainline. I've told the people > involved already over a week ago. > > I can't do anything about linux-next being broken and people not fixing it. While it took longer than I would have preferred, Al has commited the fix to his for-next tree a few days ago: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git/commit/?h=for-next&id=4c207ef48269377236cd38979197c5e1631c8c16