From: Emmanuel Varagnat <varagnat@crm.mot.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Sysctl problem
Date: Thu, 31 May 2001 18:14:09 +0200 [thread overview]
Message-ID: <3B166DD1.94BF4B44@crm.mot.com> (raw)
I registered a new directory and its tree in the proc filesystem with
some register_sysctl_table. And naturally I use unregister_sysctl_table
when the module is unloaded.
And everything seems to work fine.
Execpt that I can't read the corresponding data with the 'cat' command.
A 'strace'
shows me that 'cat' is in a loop :
...
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
write(1, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
write(1, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
1024) = 1024
...
I'm using my own function to change the data value, but helped by
proc_dointvec.
My function doesn't seem to be called.
Does anybody ever met something like this ?
Thanks
-Manu
reply other threads:[~2001-05-31 16:15 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=3B166DD1.94BF4B44@crm.mot.com \
--to=varagnat@crm.mot.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