All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, lvc-project@linuxtesting.org,
	Dmitry Antipov <dmantipov@yandex.ru>
Subject: Re: [PATCH net-next v5] net: sched: consistently use rcu_replace_pointer() in taprio_change()
Date: Thu, 05 Sep 2024 09:42:18 -0300	[thread overview]
Message-ID: <87wmjqnufp.fsf@intel.com> (raw)
In-Reply-To: <20240904115401.3425674-1-dmantipov@yandex.ru>

Dmitry Antipov <dmantipov@yandex.ru> writes:

> According to Vinicius (and carefully looking through the whole
> https://syzkaller.appspot.com/bug?extid=b65e0af58423fc8a73aa
> once again), txtime branch of 'taprio_change()' is not going to
> race against 'advance_sched()'. But using 'rcu_replace_pointer()'
> in the former may be a good idea as well.
>
> Suggested-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
> Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
> ---
> v5: cut from the series, add syzbot link an re-target to net-next
> v4: adjust subject to target net tree
> v3: unchanged since v2
> v2: added to the series
> ---

Acked-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>


Cheers,
-- 
Vinicius

  reply	other threads:[~2024-09-05 12:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 11:54 [PATCH net-next v5] net: sched: consistently use rcu_replace_pointer() in taprio_change() Dmitry Antipov
2024-09-05 12:42 ` Vinicius Costa Gomes [this message]
2024-09-08 10:30 ` patchwork-bot+netdevbpf

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=87wmjqnufp.fsf@intel.com \
    --to=vinicius.gomes@intel.com \
    --cc=dmantipov@yandex.ru \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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.