From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
Eric Joyner <eric.joyner@amd.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
Brett Creeley <brett.creeley@amd.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Abhijit Gangurde <abhijit.gangurde@amd.com>,
Allen Hubbe <allen.hubbe@amd.com>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH net-next 3/4] RDMA/ionic: Add debugfs support
Date: Thu, 14 May 2026 09:04:08 +0200 [thread overview]
Message-ID: <2026051440-devourer-appendix-4326@gregkh> (raw)
In-Reply-To: <20260514060048.GK15586@unreal>
On Thu, May 14, 2026 at 09:00:48AM +0300, Leon Romanovsky wrote:
> On Wed, May 13, 2026 at 05:23:14PM -0700, Jakub Kicinski wrote:
> > On Wed, 13 May 2026 10:21:13 +0300 Leon Romanovsky wrote:
> > > 3. The patch is too large and exposes too many details that should be
> > > gathered through the FW (fwctl).
> >
> > Why? What's wrong with debugfs? Much easier for people to access.
>
> There is nothing inherently wrong with debugfs. You can see recently
> accepted debugfs patches from hns [1].
>
> The issue here is what data is being dumped through debugfs, and in what
> quantity. From a quick look, ionic_dev_info_show() appears to print
> raw data coming straight from the FW.
>
> In my view, debugfs should expose in‑kernel structures that are shaped
> and controlled by the kernel itself. IMHO it is not the right place to
> debug FW state. There can always be exceptions, of course, but in this
> case the driver is effectively dumping everything from pds_core/FW in
> the RDMA layer.
debugfs is for anything you want, there is nothing wrong with doing
this in debugfs, in fact, it's preferred. Don't spread debug info out
into other areas, that makes it harder for admins and users to properly
secure things from stuff they don't want users to have access to.
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-14 7:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 4:19 [PATCH net-next 0/4] RDMA/net/ionic: Misc updates Eric Joyner
2026-05-06 4:19 ` [PATCH net-next 1/4] RDMA/ionic: Update copyright year to 2026 Eric Joyner
2026-05-06 4:19 ` [PATCH net-next 2/4] net/ionic: Add devlink parameter for RDMA Eric Joyner
2026-05-06 4:19 ` [PATCH net-next 3/4] RDMA/ionic: Add debugfs support Eric Joyner
2026-05-13 7:21 ` Leon Romanovsky
2026-05-14 0:23 ` Jakub Kicinski
2026-05-14 6:00 ` Leon Romanovsky
2026-05-14 7:04 ` Greg Kroah-Hartman [this message]
2026-05-14 16:35 ` Leon Romanovsky
2026-05-06 4:19 ` [PATCH net-next 4/4] RDMA/ionic: Add DCQCN parameter configuration via debugfs Eric Joyner
2026-05-06 22:59 ` [PATCH net-next 0/4] RDMA/net/ionic: Misc updates Jakub Kicinski
2026-05-14 14:33 ` Abhijit Gangurde
2026-05-14 16:40 ` Leon Romanovsky
2026-05-14 17:19 ` Creeley, Brett
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=2026051440-devourer-appendix-4326@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=abhijit.gangurde@amd.com \
--cc=allen.hubbe@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.joyner@amd.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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