From: "Starke, Daniel" <daniel.starke@siemens.com>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
Pavel Machek <pavel@ucw.cz>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>
Subject: RE: [PATCH v2] tty: n_gsm: avoid call of sleeping functions from atomic context
Date: Wed, 12 Oct 2022 06:04:03 +0000 [thread overview]
Message-ID: <DB9PR10MB58812CCC35455D34B57D0DE2E0229@DB9PR10MB5881.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <3572970f-f40f-5410-651a-a5e019d328d8@ispras.ru>
> We have found the only potential concurrency place:
> gsm->tty->ops->write() in gsmld_output() and tty->ops->write() in
> gsmld_write().
>
> Is that right? Or there are some other cases?
Correct. These are the only two places.
prev parent reply other threads:[~2022-10-12 6:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 19:35 [PATCH] tty: n_gsm: avoid call of sleeping functions from atomic context Fedor Pchelkin
2022-08-27 9:13 ` [PATCH v2] " Fedor Pchelkin
2022-09-19 11:32 ` Pavel Machek
2022-09-20 7:18 ` Fedor Pchelkin
2022-10-05 10:47 ` Starke, Daniel
2022-10-08 10:54 ` Fedor Pchelkin
2022-10-08 11:02 ` [PATCH 0/2] tty: n_gsm: revert tx_mutex usage Fedor Pchelkin
2022-10-08 11:02 ` [PATCH 1/2] Revert "tty: n_gsm: avoid call of sleeping functions from atomic context" Fedor Pchelkin
2022-10-25 6:06 ` D. Starke
2022-10-08 11:02 ` [PATCH 2/2] Revert "tty: n_gsm: replace kicktimer with delayed_work" Fedor Pchelkin
2022-10-25 6:10 ` D. Starke
2022-10-25 7:31 ` [PATCH 0/2] tty: n_gsm: revert tx_mutex usage Pavel Machek
2022-10-12 6:04 ` Starke, Daniel [this message]
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=DB9PR10MB58812CCC35455D34B57D0DE2E0229@DB9PR10MB5881.EURPRD10.PROD.OUTLOOK.COM \
--to=daniel.starke@siemens.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=khoroshilov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pavel@ucw.cz \
--cc=pchelkin@ispras.ru \
/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).