linux-kernel - RE: [PATCH v2] tty: n_gsm: avoid call of sleeping functions from atomic context

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <DB9PR10MB58812CCC35455D34B57D0DE2E0229@DB9PR10MB5881.EURPRD10.PROD.OUTLOOK.COM>
Date:   Wed, 12 Oct 2022 06:04:03 +0000
From:   "Starke, Daniel" <daniel.starke@...mens.com>
To:     Fedor Pchelkin <pchelkin@...ras.ru>
CC:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jirislaby@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Alexey Khoroshilov <khoroshilov@...ras.ru>,
        Pavel Machek <pavel@....cz>,
        "lvc-project@...uxtesting.org" <lvc-project@...uxtesting.org>
Subject: RE: [PATCH v2] tty: n_gsm: avoid call of sleeping functions from
 atomic context

> 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.