lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3795ab1d-5282-458b-6199-91e3def32463@acm.org>
Date:   Mon, 10 Feb 2020 14:37:39 -0800
From:   Bart Van Assche <bvanassche@....org>
To:     John Garry <john.garry@...wei.com>, jejb@...ux.vnet.ibm.com,
        martin.petersen@...cle.com
Cc:     linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scsi: Delete scsi_use_blk_mq

On 2/10/20 9:33 AM, John Garry wrote:
> -module_param_named(use_blk_mq, scsi_use_blk_mq, bool, S_IWUSR | S_IRUGO);

Will this change cause trouble to shell scripts that set or read this 
parameter (/sys/module/scsi_mod/parameters/use_blk_mq)? What will the 
impact be on systems where scsi_mod.use_blk_mq=Y is passed by GRUB to 
the kernel at boot time, e.g. because it has been set in the 
GRUB_CMDLINE_LINUX variable in /etc/default/grub?

Thanks,

Bart.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ