All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Luis Goncalves <lgoncalv@redhat.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	stable-rt@vger.kernel.org, Chunyu Hu <chuhu@redhat.com>
Subject: Re: [RFC RT v5.10] [rt] repair usage of raw_v6_hashinfo.lock in raw_seq_start()
Date: Wed, 27 Oct 2021 11:06:50 +0200	[thread overview]
Message-ID: <20211027090650.fqpqtze6wfetihej@linutronix.de> (raw)
In-Reply-To: <CAD8J---eDMZb7Z39vYLY+vZZYhvTokv3NgsCCa=oJhH_hTYH6w@mail.gmail.com>

On 2021-10-18 12:51:32 [-0300], Luis Goncalves wrote:
> Again, the use of tuned in the tests is mostly to reproduce the
> configuration in use at
> the moment. I can isolate the specific configuration that makes it
> possible to trigger the
> lockdep splat.

I can't reproduce any of those two issues. I tried both and iterated the
tuned profiles
	tuned-adm profile realtime
	tuned-adm profile throughput-performance

while running the test you mentioned.
Could you please try if this reproduces with latest v5.15-RT and post
complete lockdep backtrace?

Sebastian

  reply	other threads:[~2021-10-27  9:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05  1:53 [RFC RT v5.10] [rt] repair usage of raw_v6_hashinfo.lock in raw_seq_start() Luis Claudio R. Goncalves
2021-10-11 16:33 ` Sebastian Andrzej Siewior
2021-10-18 15:51   ` Luis Goncalves
2021-10-27  9:06     ` Sebastian Andrzej Siewior [this message]
2021-11-04 18:48       ` Luis Goncalves
2021-11-05 17:18         ` Sebastian Andrzej Siewior
2021-11-05 17:31           ` Sebastian Andrzej Siewior
2021-11-04 18:55       ` Luis Goncalves

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=20211027090650.fqpqtze6wfetihej@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=chuhu@redhat.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stable-rt@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.