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] [day] [month] [year] [list]
Message-ID: <CAJedcCwqem-Hj=1fF0XsEfyaeA-eAP6B9R_o1AC5trt2ap+Cdw@mail.gmail.com>
Date:   Wed, 9 Nov 2022 17:42:31 +0800
From:   Zheng Hacker <hackerzheng666@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Zheng Wang <zyytlz.wz@....com>, zhengyejian1@...wei.com,
        dimitri.sivanich@....com, arnd@...db.de,
        linux-kernel@...r.kernel.org, alex000young@...il.com,
        security@...nel.org, sivanich@....com, lkp@...el.com
Subject: Re: [PATCH v6 RESEND] misc: sgi-gru: fix use-after-free error in
 gru_set_context_option, gru_fault and gru_handle_user_call_os

> > Yes, it helped with the test and found an unused variable. I added
> > this line as the mail suggested
> > ("If you fix the issue, kindly add following tag where applicable
> > | Reported-by: kernel test robot <lkp@...el.com>").
> >
> > Should I remove it?
>
> If you submit a patch that just fixes the issue that the test robot
> finds, yes, that needs to be there.  If you are fixing up a patch that
> you submit based on the report, no, you do not.
>

Thanks for your illustration. I get it now.
I sent another patch just now, which moved kernel test robot from
reported-by tag to tested-by tag to show my respect.

Best regards,

Zheng Wang

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ