From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] Questionable RCU/BH usage in cgw_create_job().
Date: Thu, 30 Nov 2023 17:43:30 +0100 [thread overview]
Message-ID: <20231130164330.bYbMzPz7@linutronix.de> (raw)
In-Reply-To: <20231031165245.-pTSiGsg@linutronix.de>
On 2023-10-31 17:52:47 [+0100], To Oliver Hartkopp wrote:
> On 2023-10-31 17:14:01 [+0100], Oliver Hartkopp wrote:
> > Hi Sebastian,
Hi Oliver,
> The point is to replace/ update cf_mod at runtime while following RCU
> rules so always either new or the old object is observed. Never an
> intermediate step.
Do you want me to take care of it?
> > Best regards,
> > Oliver
>
Sebastian
next prev parent reply other threads:[~2023-11-30 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 11:23 [RFC] Questionable RCU/BH usage in cgw_create_job() Sebastian Andrzej Siewior
2023-10-31 16:14 ` Oliver Hartkopp
2023-10-31 16:52 ` Sebastian Andrzej Siewior
2023-11-30 16:43 ` Sebastian Andrzej Siewior [this message]
2023-11-30 19:56 ` Oliver Hartkopp
2023-12-21 12:43 ` Oliver Hartkopp
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=20231130164330.bYbMzPz7@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).