linux-kernel - Re: Re: Re：[PATCH V11] kdb: Fix the deadlock issue in KDB debugging.

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: <2024041915-flinch-cinema-9c22@gregkh>
Date: Fri, 19 Apr 2024 08:06:42 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Liuye <liu.yeC@....com>
Cc: "daniel.thompson@...aro.org" <daniel.thompson@...aro.org>,
	"dianders@...omium.org" <dianders@...omium.org>,
	"jason.wessel@...driver.com" <jason.wessel@...driver.com>,
	"jirislaby@...nel.org" <jirislaby@...nel.org>,
	"kgdb-bugreport@...ts.sourceforge.net" <kgdb-bugreport@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
	"andy.shevchenko@...il.com" <andy.shevchenko@...il.com>
Subject: Re: Re: Re：[PATCH V11] kdb: Fix the
 deadlock issue in KDB debugging.

On Fri, Apr 19, 2024 at 05:54:58AM +0000, Liuye wrote:
> @Greg KH
> 
> This issue still needs to be resolved, but I don't know how to do it. 
> Please tell me an effective strategy. How should feedback be given to make it effective for you? 
> There is already an approval process for external emails in the current company. 
> And a review mechanism has been added within the team. And internal training is provided.
> The previous mentioned has been completed. What else needs to be done?

What would you want to see if you were in my position here?

Some sort of "proof" that this really is the case?  A discussion with
your company legal group about this?  A discussion with your legal group
and the open source legal community about how they have structured all
of this so that it will not happen again and a discussion about how this
did happen (i.e. a blameless post-mortum)?  A signed-off-by on your next
patch from a lawyer in that group?

In other words, what does your legal group think would be sufficient
here?

thanks,

greg k-h