From: Wolfram Sang <wsa@kernel.org>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] i2c: dev: don't allow user-space to deadlock the kernel
Date: Tue, 17 Jan 2023 11:26:38 +0100 [thread overview]
Message-ID: <Y8Z33ml5u0GLMSIG@ninjato> (raw)
In-Reply-To: <CACMJSev_hLAzaF2M15raxb49mkE7fFMN8T+BdT9-TYu2BJkasg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
> 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-17 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 16:00 [PATCH v2 0/2] i2c: fortify the subsystem against user-space induced deadlocks Bartosz Golaszewski
2022-12-29 16:00 ` [PATCH v2 1/2] i2c: dev: fix notifier return values Bartosz Golaszewski
2023-01-17 10:04 ` Wolfram Sang
2023-03-08 16:58 ` Geert Uytterhoeven
2023-03-08 19:33 ` Bartosz Golaszewski
2023-03-08 19:51 ` Geert Uytterhoeven
2023-03-09 7:47 ` Geert Uytterhoeven
2022-12-29 16:00 ` [PATCH v2 2/2] i2c: dev: don't allow user-space to deadlock the kernel Bartosz Golaszewski
2023-01-17 10:08 ` Wolfram Sang
2023-01-17 10:10 ` Bartosz Golaszewski
2023-01-17 10:26 ` Wolfram Sang [this message]
2023-01-17 18:57 ` Wolfram Sang
2023-01-18 12:51 ` Bartosz Golaszewski
[not found] ` <20230118145914.3012-1-hdanton@sina.com>
2023-01-18 15:07 ` Bartosz Golaszewski
2023-01-12 9:01 ` [PATCH v2 0/2] i2c: fortify the subsystem against user-space induced deadlocks Bartosz Golaszewski
2023-01-12 9:09 ` Wolfram Sang
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=Y8Z33ml5u0GLMSIG@ninjato \
--to=wsa@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.