From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: Takashi Iwai <tiwai@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: core: use WARN_ON_ONCE() to avoid superfluous dumps
Date: Sat, 7 Sep 2024 00:42:26 +0900 [thread overview]
Message-ID: <20240906154226.GA6012@workstation.local> (raw)
In-Reply-To: <20240905131029.6433-1-o-takashi@sakamocchi.jp>
On Thu, Sep 05, 2024 at 10:10:29PM +0900, Takashi Sakamoto wrote:
> It is enough to notify programming mistakes to programmers just once.
>
> Suggested-by: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> ---
> drivers/firewire/core-iso.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/firewire/core-iso.c b/drivers/firewire/core-iso.c
> index af76fa1823f1..a249974a0f87 100644
> --- a/drivers/firewire/core-iso.c
> +++ b/drivers/firewire/core-iso.c
> @@ -220,7 +220,7 @@ int fw_iso_context_flush_completions(struct fw_iso_context *ctx)
> might_sleep();
>
> // Avoid dead lock due to programming mistake.
> - if (WARN_ON(current_work() == &ctx->work))
> + if (WARN_ON_ONCE(current_work() == &ctx->work))
> return 0;
>
> disable_work_sync(&ctx->work);
> @@ -244,7 +244,7 @@ int fw_iso_context_stop(struct fw_iso_context *ctx)
> might_sleep();
>
> // Avoid dead lock due to programming mistake.
> - if (WARN_ON(current_work() == &ctx->work))
> + if (WARN_ON_ONCE(current_work() == &ctx->work))
> return 0;
>
> err = ctx->card->driver->stop_iso(ctx);
Applied to for-next branch.
Regards
Takashi Sakamoto
prev parent reply other threads:[~2024-09-06 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 13:10 [PATCH] firewire: core: use WARN_ON_ONCE() to avoid superfluous dumps Takashi Sakamoto
2024-09-06 15:42 ` Takashi Sakamoto [this message]
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=20240906154226.GA6012@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=tiwai@suse.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 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.