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: Windows password security audit tool. GUI, reports in PDF.

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

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

On Tue, 17 Jan 2023 at 11:08, Wolfram Sang <wsa@...nel.org> wrote:
>
>
> > In order to fix that, we introduce a couple changes. They need to be
> > part of a single commit in order to preserve bisectability. First, drop
>
> Do you have maybe a branch at hand with more finegrained commits just
> for reviewing?
>

No, not really. It can be logically split into two elements though:
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.

Bart