workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jiri Kosina <jikos@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	corbet@lwn.net, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	security@kernel.org, Kees Cook <keescook@chromium.org>,
	Sasha Levin <sashal@kernel.org>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
Date: Wed, 14 Feb 2024 15:10:20 +0000	[thread overview]
Message-ID: <fb5f7cf4-6541-4d91-afbb-5514cec3ca47@sirena.org.uk> (raw)
In-Reply-To: <nycvar.YFH.7.76.2402141539180.21798@cbobk.fhfr.pm>

[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-02-14 15:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  8:00 Greg Kroah-Hartman
2024-02-14  8:34 ` Lukas Bulwahn
2024-02-15 12:04   ` Greg Kroah-Hartman
2024-02-15 16:10     ` Oleksandr Natalenko
2024-02-15 17:49       ` Greg Kroah-Hartman
2024-02-14  8:37 ` Vegard Nossum
2024-02-15 11:50   ` Greg Kroah-Hartman
2024-02-15 12:24     ` Vegard Nossum
2024-02-16  8:28       ` Jani Nikula
2024-02-16 11:22         ` Greg Kroah-Hartman
2024-02-16 14:58           ` Jonathan Corbet
2024-02-17 11:56             ` Greg Kroah-Hartman
2024-02-14 13:10 ` Krzysztof Kozlowski
2024-02-15 12:00   ` Greg Kroah-Hartman
2024-02-14 13:41 ` Konstantin Ryabitsev
2024-02-15 11:59   ` Greg Kroah-Hartman
2024-02-14 13:43 ` Jiri Kosina
2024-02-14 13:55   ` Mark Brown
2024-02-14 14:32     ` Greg Kroah-Hartman
2024-02-14 14:46     ` Jiri Kosina
2024-02-14 15:10       ` Mark Brown [this message]
2024-02-14 13:58   ` Greg Kroah-Hartman
2024-02-14 14:38     ` Jiri Kosina
2024-02-14 15:09       ` Greg Kroah-Hartman
2024-02-15  8:17 ` Thorsten Leemhuis
2024-02-15  8:43   ` Greg Kroah-Hartman
2024-02-15 17:54 ` Michal Hocko
2024-02-15 18:20   ` Greg Kroah-Hartman
2024-02-15 18:36     ` Michal Hocko
2024-02-16 11:25       ` Greg Kroah-Hartman
2024-02-16 13:20         ` Michal Hocko
2024-02-16 15:34           ` Greg Kroah-Hartman
2024-02-16 16:51             ` Michal Hocko
2024-02-15 19:40     ` Kees Cook
2024-02-16  7:41       ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb5f7cf4-6541-4d91-afbb-5514cec3ca47@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jikos@kernel.org \
    --cc=keescook@chromium.org \
    --cc=lee@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=security@kernel.org \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox