From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] to allow sys_pread64 and sys_pwrite64 to be used from modules
Date: Wed, 29 Sep 2004 15:35:55 +0100 [thread overview]
Message-ID: <20040929143555.GA25982@lkcl.net> (raw)
In-Reply-To: <1096462770.2786.35.camel@laptop.fenrus.com>
On Wed, Sep 29, 2004 at 02:59:30PM +0200, Arjan van de Ven wrote:
> On Wed, 2004-09-29 at 14:58, Luke Kenneth Casson Leighton wrote:
> > i do not know if this does any damage (and i'm going to find out!)
> >
> > i seek to use these two functions from an experimental kernel module: i
> > get warnings about "symbol not found" without this patch:
> >
>
> what on earth are you doing in your module??????
prefixing a new root onto the front of the file name and then
re-issuing (proxying) a request.
all file requests, all stats, all opendirs, everything.
i'm hacking fuse in an attempt to remove the userspace bits,
merging the functionality of the userspace "fusexmp" - fuse
example program - into the fuse kernel module.
l.
p.s. if someone fixes the ioctl bug BLKRRDPART on a usb scsi
storage device which has been umounted with a "-l"
option, then i don't have to do all this work.
bugs.debian.org no #273055.
--
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love. If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net"> lkcl.net </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
next prev parent reply other threads:[~2004-09-29 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 12:58 [PATCH] to allow sys_pread64 and sys_pwrite64 to be used from modules Luke Kenneth Casson Leighton
2004-09-29 12:59 ` Arjan van de Ven
2004-09-29 14:35 ` Luke Kenneth Casson Leighton [this message]
2004-09-29 14:37 ` Luke Kenneth Casson Leighton
2004-09-29 17:52 ` Luke Kenneth Casson Leighton
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=20040929143555.GA25982@lkcl.net \
--to=lkcl@lkcl.net \
--cc=arjanv@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.