[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200901070841.GA29847@lst.de>
Date: Tue, 1 Sep 2020 09:08:41 +0200
From: Christoph Hellwig <hch@....de>
To: kernel test robot <rong.a.chen@...el.com>
Cc: Christoph Hellwig <hch@....de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
Michael Ellerman <mpe@...erman.id.au>, x86@...nel.org,
linux-fsdevel@...r.kernel.org, linux-arch@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, Kees Cook <keescook@...omium.org>,
linux-kernel@...r.kernel.org, 0day robot <lkp@...el.com>,
lkp@...ts.01.org, rui.zhang@...el.com, yu.c.chen@...el.com
Subject: Re: [fs] ef30fb3c60: kernel write not supported for file
/sys/kernel/softlockup_panic
Looks like since the start of this series we've grown new code to
use kernel_write on sysctl files based on boot parameters. The good
news is that this just means I need to resurrect the sysctl series
as all that work was done already.
Powered by blists - more mailing lists