From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Fedor Pchelkin <pchelkin@ispras.ru>,
linux-kernel@vger.kernel.org,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
ldv-project@linuxtesting.org, Hillf Danton <hdanton@sina.com>
Subject: Re: [PATCH v4 1/2] tty: n_gsm: replace kicktimer with delayed_work
Date: Tue, 30 Aug 2022 14:38:04 +0200 [thread overview]
Message-ID: <Yw4ErPa8lfF49EFd@kroah.com> (raw)
In-Reply-To: <46019fb5-dcc1-f0df-4043-e25e6db3c226@kernel.org>
On Tue, Aug 30, 2022 at 09:30:27AM +0200, Jiri Slaby wrote:
> On 29. 08. 22, 15:16, Fedor Pchelkin wrote:
> > A kick_timer timer_list is replaced with kick_timeout delayed_work to be
> > able to synchronize with mutexes as a prerequisite for the introduction
> > of tx_mutex.
> >
> > Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
>
> Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
>
> But I think this conflicts with Tetsuo's cleanup [1]. So one of you will
> likely have to rebase and resubmit.
>
> [1] https://lore.kernel.org/all/2110618e-57f0-c1ce-b2ad-b6cacef3f60e@I-love.SAKURA.ne.jp/
I've fixed it up by hand now, no worries.
greg k-h
next prev parent reply other threads:[~2022-08-30 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220827130349.2738-1-hdanton@sina.com>
2022-08-27 19:55 ` [PATCH v3] tty: n_gsm: avoid call of sleeping functions from atomic context Fedor Pchelkin
2022-08-29 6:59 ` Jiri Slaby
2022-08-29 13:16 ` [PATCH v4 0/2] " Fedor Pchelkin
2022-08-29 13:16 ` [PATCH v4 1/2] tty: n_gsm: replace kicktimer with delayed_work Fedor Pchelkin
2022-08-30 7:30 ` Jiri Slaby
2022-08-30 12:38 ` Greg Kroah-Hartman [this message]
2022-08-29 13:16 ` [PATCH v4 2/2] tty: n_gsm: avoid call of sleeping functions from atomic context Fedor Pchelkin
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=Yw4ErPa8lfF49EFd@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=jirislaby@kernel.org \
--cc=khoroshilov@ispras.ru \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.