linux-kernel - Re: [PATCH v2 2/2] i2c: dev: don't allow user-space to deadlock the kernel

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Y8Z33ml5u0GLMSIG@ninjato>
Date:   Tue, 17 Jan 2023 11:26:38 +0100
From:   Wolfram Sang <wsa@...nel.org>
To:     Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Cc:     Bartosz Golaszewski <brgl@...ev.pl>, linux-i2c@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] i2c: dev: don't allow user-space to deadlock the
 kernel


> No, not really. It can be logically split into two elements though:

Ok, no worries.

> removing the existing completion and then adding the locking bits
> which unfortunately go into many places. I tried to make the commit
> description as elaborate as possible but let me know if you have any
> specific questions.

Will do. The commit message _is_ nicely elaborate, still I need to dive
into the topic thoroughly. I'll let you know how it goes.


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)