From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lee Jones <lee@kernel.org>
Cc: "Starke, Daniel" <daniel.starke@siemens.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Fedor Pchelkin <pchelkin@ispras.ru>,
Jiri Slaby <jirislaby@kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"syzbot+5f47a8cea6a12b77a876@syzkaller.appspotmail.com"
<syzbot+5f47a8cea6a12b77a876@syzkaller.appspotmail.com>
Subject: Re: [PATCH 1/1] tty: n_gsm: Avoid sleeping during .write() whilst atomic
Date: Thu, 5 Oct 2023 13:55:46 +0200 [thread overview]
Message-ID: <2023100507-worst-quarrel-2b97@gregkh> (raw)
In-Reply-To: <20231005114632.GA681678@google.com>
On Thu, Oct 05, 2023 at 12:46:32PM +0100, Lee Jones wrote:
> On Thu, 05 Oct 2023, Starke, Daniel wrote:
>
> > > > Would something like this tick that box?
> > > >
> > > > diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index
> > > > 1f3aba607cd51..5c1d2fcd5d9e2 100644
> > > > --- a/drivers/tty/n_gsm.c
> > > > +++ b/drivers/tty/n_gsm.c
> > > > @@ -3716,6 +3716,10 @@ static ssize_t gsmld_write(struct tty_struct *tty, struct file *file,
> > > > if (!gsm)
> > > > return -ENODEV;
> > > >
> > > > + /* The GSM line discipline does not support binding to console */
> > > > + if (strncmp(tty->name, "tty", 3))
> > > > + return -EINVAL;
> > >
> > > No, that's not going to work, some consoles do not start with "tty" :(
>
> Ah, you mean there are others that we need to consider?
>
> I was just covering off con_write() from drivers/tty/vt/vt.c.
>
> Does anyone have a counter proposal?
consoles are dynamically assigned, the device knows if it is a console
or not, so there is a way to determine this at runtime. It's not a
device naming thing at all.
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-05 14:47 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
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 [this message]
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=2023100507-worst-quarrel-2b97@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=daniel.starke@siemens.com \
--cc=jirislaby@kernel.org \
--cc=lee@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).