public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	jeyu@kernel.org, corbet@lwn.net, mchehab+samsung@kernel.org,
	tglx@linutronix.de, akpm@linux-foundation.org,
	gregkh@linuxfoundation.org, pawan.kumar.gupta@linux.intel.com,
	jgross@suse.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] module: Allow to disable modsign in kernel cmdline
Date: Tue, 28 Apr 2020 14:01:37 +0800	[thread overview]
Message-ID: <aecb37fd-e99e-c6e2-ac80-ccf1ae2b0295@linux.alibaba.com> (raw)
In-Reply-To: <aff03dbb-a1a3-c95e-1c24-60279b14970a@infradead.org>



On 2020/4/28 13:52, Randy Dunlap wrote:
> Hi,
> 
> On 4/27/20 10:05 PM, Tianjia Zhang wrote:
>> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
>> index 7bc83f3d9bdf..00ed7566959f 100644
>> --- a/Documentation/admin-guide/kernel-parameters.txt
>> +++ b/Documentation/admin-guide/kernel-parameters.txt
>> @@ -3190,6 +3190,12 @@
>>   	noirqdebug	[X86-32] Disables the code which attempts to detect and
>>   			disable unhandled interrupt sources.
>>   
>> +	no_modsig_enforce
>> +			[KNL] When CONFIG_MODULE_SIG_FORCE is set, this option
>> +			allows to disable modsign completely at the beginning.
>> +			This means that modules without (valid) signatures will
>> +			success to load.
> 
> 			succeed to load.
> 
> 			succeed in loading.
> 
> 			load successfully.
> I prefer this one.....  ^^^^^^^^^^^^^^^^^^^^^
> 
> 			be loaded successfully.
> 
> 
>> +
>>   	no_timer_check	[X86,APIC] Disables the code which tests for
>>   			broken timer IRQ sources.
>>   
> 
> thanks.
> 

v3 patch has been submitted, thank you for your suggestion.

Thanks,
Tianjia

      reply	other threads:[~2020-04-28  6:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28  5:05 [PATCH v2] module: Allow to disable modsign in kernel cmdline Tianjia Zhang
2020-04-28  5:52 ` Randy Dunlap
2020-04-28  6:01   ` Tianjia Zhang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aecb37fd-e99e-c6e2-ac80-ccf1ae2b0295@linux.alibaba.com \
    --to=tianjia.zhang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeyu@kernel.org \
    --cc=jgross@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox