From: Steve French <smfrench@austin.rr.com>
To: linux-kernel@vger.kernel.org
Subject: upcall via DNOTIFY against /proc files
Date: Wed, 16 Feb 2005 17:08:35 -0600 [thread overview]
Message-ID: <4213D273.6010605@austin.rr.com> (raw)
Is there any argument against using the DNOTIFY/poll upcall approach
(against pseudo files e.g. in /proc or /sysfs) that e.g. nfs uses now to
get from kernel space to get data back from user space helper routines
(e.g. for idmapping and gssapi)? Since there could be security and
potential denial of service implications in getting it wrong, I wanted
to check if there are recent changes that I have missed that would be
better approaches to this.
I was hoping that the kernel event mechanism would standardize a way to
do this with less code someday.
reply other threads:[~2005-02-16 23:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4213D273.6010605@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-kernel@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