All of lore.kernel.org
 help / color / mirror / Atom feed
From: "rik.theys via Bugspray Bot" <bugbot@kernel.org>
To: trondmy@kernel.org, anna@kernel.org, linux-nfs@vger.kernel.org,
	 cel@kernel.org, jlayton@kernel.org
Subject: Re: warning in nfsd4_cb_done
Date: Thu, 30 Jan 2025 14:20:07 +0000	[thread overview]
Message-ID: <20250130-b219737c2-b4f8114c4919@bugzilla.kernel.org> (raw)
In-Reply-To: <20250130-b219737c0-091f27de8b7a@bugzilla.kernel.org>

rik.theys writes via Kernel.org Bugzilla:

Hi,

It seems I've cloned the wrong bug. It should have been https://bugzilla.kernel.org/show_bug.cgi?id=219710 instead.

As mentioned by Chuck in https://bugzilla.kernel.org/show_bug.cgi?id=219710#c25 there are multiple events in the trace, but there is only a single WARNING logged? So is there still something different between the various events, or is the warning only logged once?

Regards,
Rik

View: https://bugzilla.kernel.org/show_bug.cgi?id=219737#c2
You can reply to this message to join the discussion.
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)


  parent reply	other threads:[~2025-01-30 14:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30 14:05 warning in nfsd4_cb_done rik.theys via Bugspray Bot
2025-01-30 14:10 ` Chuck Lever via Bugspray Bot
2025-01-30 15:08   ` Olga Kornievskaia
2025-01-30 15:20     ` Chuck Lever via Bugspray Bot
2025-01-30 15:20       ` Chuck Lever via Bugspray Bot
2025-01-30 15:55       ` Chuck Lever via Bugspray Bot
2025-01-30 14:20 ` rik.theys via Bugspray Bot [this message]
2025-02-04 13:30 ` rik.theys via Bugspray Bot
2025-02-04 13:30   ` Chuck Lever via Bugspray Bot
2025-02-10 15:03     ` Olga Kornievskaia
2025-02-10 16:35     ` Jeff Layton via Bugspray Bot
2025-02-10 15:45 ` Jeff Layton via Bugspray Bot
2025-02-10 16:45 ` Chuck Lever via Bugspray Bot
2025-02-24 11:55 ` rik.theys via Bugspray Bot
2025-02-24 12:20 ` Jeff Layton via Bugspray Bot

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=20250130-b219737c2-b4f8114c4919@bugzilla.kernel.org \
    --to=bugbot@kernel.org \
    --cc=anna@kernel.org \
    --cc=cel@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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.