From: Jeff Johnson <jjohnson@codeaurora.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-wireless@vger.kernel.org, Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Kees Cook <keescook@chromium.org>, Jason Gunthorpe <jgg@ziepe.ca>,
Chao Yu <chao@kernel.org>, Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH v2] b43: don't save dentries for debugfs
Date: Thu, 20 May 2021 15:16:35 -0700 [thread overview]
Message-ID: <36d75173b785819a4792ccceb5bf26b8@codeaurora.org> (raw)
In-Reply-To: <YKU2vMoDO0Ch1Lyg@kroah.com>
On 2021-05-19 09:03, Greg Kroah-Hartman wrote:
> On Wed, May 19, 2021 at 08:57:00AM -0700, Jeff Johnson wrote:
>> Unless debugfs is disabled, like on Android, which is the real problem
>> I'm
>> trying to solve.
>
> Then use some other filesystem to place your relay file in. A relay
> file is not a file that userspace should rely on for normal operation,
> so why do you need it at all?
>
> What tools/operation requires access to this file that systems without
> debugfs support is causing problems on?
(trimmed some lists)
For the ath drivers (as well as the out-of-tree Android driver) it is
being used for RF spectral scan which produces a large amount of data
that is processed by a userspace analysis application.
I've been looking for an alternate filesystem to use, but am not finding
anything where it appears easy to get a parent dentry, so any clues for
the clueless (me) would be appreciated.
Jeff
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2021-05-20 22:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 16:33 [PATCH v2] b43: don't save dentries for debugfs Greg Kroah-Hartman
2021-05-18 17:47 ` Kalle Valo
2021-05-21 18:44 ` Greg Kroah-Hartman
2021-05-18 19:29 ` Jeff Johnson
2021-05-18 22:00 ` Jeff Johnson
2021-05-19 5:05 ` Greg Kroah-Hartman
2021-05-19 15:04 ` Jeff Johnson
2021-05-19 15:42 ` Greg Kroah-Hartman
2021-05-19 15:57 ` Jeff Johnson
2021-05-19 16:03 ` Greg Kroah-Hartman
2021-05-20 22:16 ` Jeff Johnson [this message]
2021-05-21 5:12 ` Greg Kroah-Hartman
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=36d75173b785819a4792ccceb5bf26b8@codeaurora.org \
--to=jjohnson@codeaurora.org \
--cc=chao@kernel.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=leon@kernel.org \
--cc=linux-wireless@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).