linux-kernel - Re: [PATCH] platform/chrome: cros_ec

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: <D0HF9FPTDYNC.18XQW4MJQPCGD@noahloomans.com>
Date: Thu, 11 Apr 2024 18:08:45 +0200
From: "Noah Loomans" <noah@...hloomans.com>
To: "Guenter Roeck" <groeck@...gle.com>, "Tzung-Bi Shih"
 <tzungbi@...nel.org>
Cc: "Bhanu Prakash Maiya" <bhanumaiya@...omium.org>, "Benson Leung"
 <bleung@...omium.org>, "Guenter Roeck" <groeck@...omium.org>, "Robert
 Zieba" <robertzieba@...gle.com>, <chrome-platform@...ts.linux.dev>,
 <linux-kernel@...r.kernel.org>, <stable@...r.kernel.org>
Subject: Re: [PATCH] platform/chrome: cros_ec_uart: properly fix race
 condition

On 2024-04-11 at 04:26 UTC+02, Guenter Roeck wrote:
> We might also consider applying the patch to all ChromeOS branches
> directly (not waiting for upstream); we do see a number of crashes
> because of it.

Heh, I did wonder how Chromebooks running Chrome OS avoided this issue.
I guess the answer is simple: they didn't :)