From: Massimiliano Hofer <max@nucleus.it>
To: linux-kernel@vger.kernel.org
Subject: question about procfs
Date: Thu, 27 Apr 2006 14:28:24 +0200 [thread overview]
Message-ID: <200604271428.29764.max@nucleus.it> (raw)
Hi,
I'm trying various things with procfs, but there's one thing I can't find in
any existing code or documentation.
If I define a hook for proc_iops->unlink in a procfs directory and do a
remove_proc_entry() when called, I always get this message:
"de_put: deferred delete of ..."
Everything seems to work, but I get the warning.
I see 3 possibilities:
- I'm doing it the wrong way (likely);
- it's an overzealous warning that everyone should ignore;
- it's officially deemed as a Bad Thing (TM) (also likely).
Does anyone know why the warning is there?
I know procfs is not supposed to be meddled too much, but I'm just trying to
hack. :)
--
Saluti,
Massimiliano Hofer
Nucleus
reply other threads:[~2006-04-27 12:28 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=200604271428.29764.max@nucleus.it \
--to=max@nucleus.it \
--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
Powered by JetHome