[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb5f7cf4-6541-4d91-afbb-5514cec3ca47@sirena.org.uk>
Date: Wed, 14 Feb 2024 15:10:20 +0000
From: Mark Brown <broonie@...nel.org>
To: Jiri Kosina <jikos@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, corbet@....net,
workflows@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, security@...nel.org,
Kees Cook <keescook@...omium.org>, Sasha Levin <sashal@...nel.org>,
Lee Jones <lee@...nel.org>
Subject: Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
On Wed, Feb 14, 2024 at 03:46:12PM +0100, Jiri Kosina wrote:
> On Wed, 14 Feb 2024, Mark Brown wrote:
> > There's an argument for many headphone volume related fixes too since
> > excessively large volumes can cause substantial distress and potential
> > injury to users (I can't remember if that fix would be relevant to that
> > issue).
> Something being too loud, causing distress ... that's really a grey zone
> (to put it mildly) for me. How about e.g. a bug in GPU driver, leading to
> a flickering screen? Many people are very sensitive to that (both
> physically and mentally) for various reasons.
> Bug worth fixing? Absolutely, as soon as possible. Security-relevant? Not
> in my book.
To be clear, most headphone drivers can easily generate output levels
which will cause temporary or permanent hearing loss after very brief
exposure. The distress is the urgent and instinctive need to remove the
headphones as fast as possible that tends to result, much as it would
for any other ongoing source of injury.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists