From: Lee Jones <lee@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org,
Daniel Starke <daniel.starke@siemens.com>,
Fedor Pchelkin <pchelkin@ispras.ru>,
linux-serial@vger.kernel.org,
syzbot+5f47a8cea6a12b77a876@syzkaller.appspotmail.com
Subject: Re: [PATCH 1/1] tty: n_gsm: Avoid sleeping during .write() whilst atomic
Date: Thu, 5 Oct 2023 08:26:04 +0100 [thread overview]
Message-ID: <20231005072604.GC83257@google.com> (raw)
In-Reply-To: <2023100511-unpeeled-dinginess-fefd@gregkh>
On Thu, 05 Oct 2023, Greg Kroah-Hartman wrote:
> On Thu, Oct 05, 2023 at 06:59:50AM +0200, Jiri Slaby wrote:
> > On 04. 10. 23, 14:57, Lee Jones wrote:
> > > > > n_gsm is available on all the systems I have available. The mention of
> > > > > 'EXPERIMENTAL' in the module description appears to have zero effect on
> > > > > whether distros choose to make it available or not. If you're saying
> > > > > that we know this module is BROKEN however, then perhaps we should mark
> > > > > it as such.
> > > >
> > > > Also, I think this requires root to set this line discipline to the
> > > > console, right? A normal user can't do that, or am I missing a code
> > > > path here?
> > >
> > > I haven't been testing long, but yes, early indications show that root
> > > is required.
> >
> > FWIW I concluded to the same yesterday, so I disputed the connected
> > CVE-2023-31082. Waiting for mitre's ack/nack.
>
> Trying to dispute obviously-wrong CVEs is a never-ending task.
>
> Personally, it's fun to see who keeps popping up to attempt to resolve
> this issue showing what companies have their security policies dictated
> by a random government authority that can be modified by anyone :)
It's a struggle! :)
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-10-05 15:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 17:00 [PATCH 1/1] tty: n_gsm: Avoid sleeping during .write() whilst atomic Lee Jones
2023-10-03 18:14 ` Greg Kroah-Hartman
2023-10-03 18:55 ` Lee Jones
2023-10-04 6:04 ` Greg Kroah-Hartman
2023-10-04 9:09 ` Lee Jones
2023-10-04 9:55 ` Greg Kroah-Hartman
2023-10-04 12:19 ` Greg Kroah-Hartman
2023-10-04 12:57 ` Lee Jones
2023-10-04 13:13 ` Greg Kroah-Hartman
2023-10-05 4:59 ` Jiri Slaby
2023-10-05 6:05 ` Greg Kroah-Hartman
2023-10-05 7:26 ` Lee Jones [this message]
2023-10-04 5:59 ` Starke, Daniel
2023-10-04 6:05 ` Greg Kroah-Hartman
2023-10-04 8:40 ` Jiri Slaby
2023-10-04 8:58 ` Starke, Daniel
2023-10-04 8:57 ` Lee Jones
2023-10-04 12:21 ` Greg Kroah-Hartman
2023-10-04 12:57 ` Lee Jones
2023-10-04 13:14 ` Greg Kroah-Hartman
2023-10-05 9:03 ` Lee Jones
2023-10-05 9:18 ` Greg Kroah-Hartman
2023-10-05 10:43 ` Lee Jones
2023-10-05 11:33 ` Greg Kroah-Hartman
2023-10-05 11:38 ` Starke, Daniel
2023-10-05 11:46 ` Lee Jones
2023-10-05 11:55 ` Greg Kroah-Hartman
2023-10-05 12:17 ` Lee Jones
2023-10-05 12:37 ` 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=20231005072604.GC83257@google.com \
--to=lee@kernel.org \
--cc=daniel.starke@siemens.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pchelkin@ispras.ru \
--cc=syzbot+5f47a8cea6a12b77a876@syzkaller.appspotmail.com \
/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;
as well as URLs for NNTP newsgroup(s).