From: Christoph Hellwig <hch@infradead.org>
To: alan.adamson@oracle.com
Cc: Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, kbusch@kernel.org, hch@lst.de
Subject: Re: [RFC v3 1/1] nvme: add passthrough error logging opt-in
Date: Wed, 5 Apr 2023 08:07:55 -0700 [thread overview]
Message-ID: <ZC2OyyPMeu8d06th@infradead.org> (raw)
In-Reply-To: <c1aa9b1b-5a10-8dcb-9a9a-fce1ff8a5097@oracle.com>
On Tue, Apr 04, 2023 at 09:20:40AM -0700, alan.adamson@oracle.com wrote:
> For namespace errors (read, write, etc), passthrough initiated or not,
> shouldn't they always be logged?
We could start with that. If we see complaints we can add the
per-namespace attribute.
prev parent reply other threads:[~2023-04-05 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 22:18 [RFC v3 0/1] nvme: add passthrough error logging opt-in Alan Adamson
2023-03-31 22:18 ` [RFC v3 1/1] " Alan Adamson
2023-04-03 8:26 ` Pankaj Raghav
2023-04-05 22:35 ` alan.adamson
2023-04-06 4:13 ` Minwoo Im
2023-04-06 4:24 ` Chaitanya Kulkarni
2023-04-06 4:27 ` Minwoo Im
2023-04-03 10:17 ` Sagi Grimberg
2023-04-03 22:20 ` alan.adamson
2023-04-03 22:38 ` Sagi Grimberg
2023-04-03 22:54 ` alan.adamson
2023-04-03 23:29 ` Sagi Grimberg
2023-04-04 16:20 ` alan.adamson
2023-04-05 15:07 ` Christoph Hellwig [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=ZC2OyyPMeu8d06th@infradead.org \
--to=hch@infradead.org \
--cc=alan.adamson@oracle.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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