From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme/pci: Print invalid SGL only once
Date: Fri, 15 Sep 2017 11:17:14 -0400 [thread overview]
Message-ID: <20170915151713.GD8878@localhost.localdomain> (raw)
In-Reply-To: <20170915145553.GA1147@lst.de>
On Fri, Sep 15, 2017@04:55:53PM +0200, Christoph Hellwig wrote:
> On Thu, Sep 14, 2017@03:06:14PM -0400, Keith Busch wrote:
> > The WARN_ONCE macro returns true if the condition is true, not if the
> > warn was raised, so we're printing the scatter list every time it's
> > invalid. This is excessive and makes debugging harder, so this patch
> > prints it just once.
>
> Please use the printk_ratelimited() helper instead.
Hmm, I don't want to rate limit the prints. That may log only partial
SGLs, or even worse, interleave parts from multiple errors. We want
to see an entire SGL for a single error, like what WARN_ONCE does.
A single occurrence is usually sufficient to work backwards to see how
the breakage occurred.
next prev parent reply other threads:[~2017-09-15 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 19:06 [PATCH] nvme/pci: Print invalid SGL only once Keith Busch
2017-09-15 7:36 ` Johannes Thumshirn
2017-09-15 14:55 ` Christoph Hellwig
2017-09-15 15:17 ` Keith Busch [this message]
2017-09-15 15:44 ` Keith Busch
2017-09-15 15:42 ` Christoph Hellwig
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=20170915151713.GD8878@localhost.localdomain \
--to=keith.busch@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox