public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Marius Zachmann <mail@mariuszachmann.de>
Cc: Wilken Gottwalt <wilken.gottwalt@posteo.net>,
	Aleksandr Mezin <mezin.alexander@gmail.com>,
	linux-hwmon@vger.kernel.org, Jiri Kosina <jikos@kernel.org>
Subject: Re: corsair-cpro and hidraw
Date: Fri, 18 Jun 2021 12:41:24 -0700	[thread overview]
Message-ID: <20210618194124.GB1664689@roeck-us.net> (raw)
In-Reply-To: <36091016.oId77RFrrH@marius>

On Fri, Jun 18, 2021 at 02:22:57PM +0200, Marius Zachmann wrote:
> > 
> > Same there: Make userspace and kernel mutually exclusive if parallel access
> > is shown to be problematic. "Mutually exclusive" means disable userspace
> > access completely while the driver is loaded, not some cross-subsystem
> > mutex.
> > 
> > Guenter
> > 
> 
> For now I did not get a bug report nor did anyone seem to have a real problem.
> It is mostly a theoretical issue.
> I am not unhappy about how it is.
> Maybe until a real problem occurs, we should just do nothing?
> 

That would be my suggestion.

Guenter

  reply	other threads:[~2021-06-18 19:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  3:11 corsair-cpro and hidraw Aleksandr Mezin
2021-06-17  4:33 ` Aleksandr Mezin
2021-06-17  6:27 ` Marius Zachmann
2021-06-17  7:11   ` Aleksandr Mezin
2021-06-17 13:14     ` Guenter Roeck
2021-06-17 23:56       ` Aleksandr Mezin
2021-06-18  5:45         ` Wilken Gottwalt
2021-06-18  6:18           ` Marius Zachmann
2021-06-18  6:47             ` Wilken Gottwalt
2021-06-18  7:06               ` Marius Zachmann
2021-06-18 12:13                 ` Guenter Roeck
2021-06-18 12:22                   ` Marius Zachmann
2021-06-18 19:41                     ` Guenter Roeck [this message]
2021-06-18 12:10               ` Guenter Roeck

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=20210618194124.GB1664689@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jikos@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=mail@mariuszachmann.de \
    --cc=mezin.alexander@gmail.com \
    --cc=wilken.gottwalt@posteo.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox