From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Peter Enderborg <pme@hyglo.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Procfs open hook bug.
Date: 01 Jul 2003 19:33:37 +0100 [thread overview]
Message-ID: <1057084415.18951.7.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3F016888.2080306@hyglo.com>
On Maw, 2003-07-01 at 11:55, Peter Enderborg wrote:
> And when loading this module. The procfs gets broken. I get EINVAL for
> open on
> /proc/meminfo and all other procfs info. Why? Should procfs inodes don't
> have full
> filesematics? And it don't help to unload the module.
If you look at other file systems you'll see they swap the file
operations pointer
prev parent reply other threads:[~2003-07-01 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 10:55 Peter Enderborg
2003-07-01 18:33 ` Alan Cox [this message]
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=1057084415.18951.7.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pme@hyglo.com \
--cc=torvalds@osdl.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®