Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: Missing param value! Expected 'rw=...value...'
To:     Heiner Kallweit <hkallweit1@gmail.com>,
        Xiaoming Ni <nixiaoming@huawei.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
References: <27b2e02f-0840-2686-7aad-16274519dcdc@gmail.com>
From:   Randy Dunlap <rdunlap@infradead.org>
Message-ID: <cb54e349-7147-0a1f-a349-1e16ba603fce@infradead.org>
Date:   Sat, 16 Jan 2021 15:39:15 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <27b2e02f-0840-2686-7aad-16274519dcdc@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 1/16/21 3:07 PM, Heiner Kallweit wrote:
> Since 60b7cab23e5e ("proc_sysctl: fix oops caused by incorrect command parameters.")
> I'm getting the following warning: Missing param value! Expected 'rw=...value...'
> AFAIK param rw doesn't require a value. That's what my command line looks like:
> Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img root=/dev/sda2 rw
> 

"rw" isn't a sysctl, so it looks like that added test is too early in
that function.


-- 
~Randy
You can't do anything without having to do something else first.
-- Belefant's Law