From: Pavel Machek <pavel@denx.de>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Daniel Starke <daniel.starke@siemens.com>,
Jiri Slaby <jirislaby@kernel.org>,
lvc-project@linuxtesting.org,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] tty: n_gsm: revert tx_mutex usage
Date: Tue, 25 Oct 2022 09:31:12 +0200 [thread overview]
Message-ID: <20221025073112.GA1587@duo.ucw.cz> (raw)
In-Reply-To: <20221008110221.13645-1-pchelkin@ispras.ru>
[-- Attachment #1: Type: text/plain, Size: 582 bytes --]
Hi!
> As far as switching to tx_mutex turns out to have its own problems,
> we suggest to revert it and to find another solution for the original
> issue described in 902e02ea9385 ("tty: n_gsm: avoid call of sleeping
> functions from atomic context").
We have lived with locking problems for a long time, and we really
don't want data corruption.
Reviewed-by: Pavel Machek <pavel@denx.de>
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-10-25 7:31 UTC|newest]
Thread overview: 14+ 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 ` Pavel Machek [this message]
2022-10-12 6:04 ` [PATCH v2] tty: n_gsm: avoid call of sleeping functions from atomic context Starke, Daniel
[not found] <DB9PR10MB58817A08B92BA7F943CDD9B2E02E9@DB9PR10MB5881.EURPRD10.PROD.OUTLOOK.COM>
2022-10-24 14:37 ` [PATCH 0/2] tty: n_gsm: revert tx_mutex usage Greg KH
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=20221025073112.GA1587@duo.ucw.cz \
--to=pavel@denx.de \
--cc=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=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
all inboxes | Powered by JetHome®