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: <MW2PR2101MB1052D49DFD8B107E82819D23D7E40@MW2PR2101MB1052.namprd21.prod.outlook.com>
Date:   Sun, 15 Nov 2020 22:11:33 +0000
From:   Michael Kelley <mikelley@...rosoft.com>
To:     Matheus Castello <matheus@...tello.eng.br>,
        KY Srinivasan <kys@...rosoft.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        Stephen Hemminger <sthemmin@...rosoft.com>,
        "wei.liu@...nel.org" <wei.liu@...nel.org>
CC:     "sashal@...nel.org" <sashal@...nel.org>,
        Tianyu Lan <Tianyu.Lan@...rosoft.com>,
        Dexuan Cui <decui@...rosoft.com>,
        Sunil Muthuswamy <sunilmut@...rosoft.com>,
        "linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/6] drivers: hv: Fix hyperv_record_panic_msg path on
 comment

From: Matheus Castello <matheus@...tello.eng.br>  Sent: Sunday, November 15, 2020 11:57 AM
> 
> Fix the kernel parameter path in the comment, in the documentation the
> parameter is correct but if someone who is studying the code and see
> this first can get confused and try to access the wrong path/parameter
> 
> Signed-off-by: Matheus Castello <matheus@...tello.eng.br>
> ---
>  drivers/hv/vmbus_drv.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> index 4fad3e6745e5..9ed7e3b1d654 100644
> --- a/drivers/hv/vmbus_drv.c
> +++ b/drivers/hv/vmbus_drv.c
> @@ -55,7 +55,7 @@ int vmbus_interrupt;
>  /*
>   * Boolean to control whether to report panic messages over Hyper-V.
>   *
> - * It can be set via /proc/sys/kernel/hyperv/record_panic_msg
> + * It can be set via /proc/sys/kernel/hyperv_record_panic_msg
>   */
>  static int sysctl_record_panic_msg = 1;
> 
> --
> 2.28.0

Reviewed-by: Michael Kelley <mikelley@...rosoft.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ