Subject: [PATCH] to allow sys_pread64 and sys_pwrite64 to be used from modules

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:


Index: fs/read_write.c
===================================================================
RCS file: /cvsroot/selinux/nsa/linux-2.6/fs/read_write.c,v
retrieving revision 1.1.1.6
diff -u -3 -p -u -r1.1.1.6 read_write.c
--- fs/read_write.c 18 Jun 2004 19:30:06 -0000 1.1.1.6
+++ fs/read_write.c 29 Sep 2004 12:45:31 -0000
@@ -318,6 +318,7 @@ asmlinkage ssize_t sys_pread64(unsigned

return ret;
}
+EXPORT_SYMBOL_GPL(sys_pread64);

asmlinkage ssize_t sys_pwrite64(unsigned int fd, const char __user *buf,
size_t count, loff_t pos)
@@ -337,6 +338,7 @@ asmlinkage ssize_t sys_pwrite64(unsigned

return ret;
}
+EXPORT_SYMBOL_GPL(sys_pwrite64);

/*
* Reduce an iovec's length in-place. Return the resulting number of segments


--
--
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:[email protected]"> [email protected] </a> <br />


2004-09-29 13:02:50

by Arjan van de Ven

[permalink] [raw]
Subject: Re: [PATCH] to allow sys_pread64 and sys_pwrite64 to be used from modules

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??????


Attachments:
signature.asc (189.00 B)
This is a digitally signed message part
Subject: Re: [PATCH] to allow sys_pread64 and sys_pwrite64 to be used from modules

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??????

... if i feel like giving up i will of course try something like
install the selinux-enabled nfs server plus nfs client selinux patches,
and mount the filesystem via 127.0.0.1.

as a last resort.

--
--
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:[email protected]"> [email protected] </a> <br />

Subject: Re: [PATCH] to allow sys_pread64 and sys_pwrite64 to be used from modules

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:[email protected]"> [email protected] </a> <br />

Subject: Re: [PATCH] to allow sys_pread64 and sys_pwrite64 to be used from modules

scratch that: i found that vfs_read along with filp_open and filp_close
would do the job.

having a ball :)

On Wed, Sep 29, 2004 at 01:58:35PM +0100, 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:
>
>
> Index: fs/read_write.c
> ===================================================================
> RCS file: /cvsroot/selinux/nsa/linux-2.6/fs/read_write.c,v
> retrieving revision 1.1.1.6
> diff -u -3 -p -u -r1.1.1.6 read_write.c
> --- fs/read_write.c 18 Jun 2004 19:30:06 -0000 1.1.1.6
> +++ fs/read_write.c 29 Sep 2004 12:45:31 -0000
> @@ -318,6 +318,7 @@ asmlinkage ssize_t sys_pread64(unsigned
>
> return ret;
> }
> +EXPORT_SYMBOL_GPL(sys_pread64);
>
> asmlinkage ssize_t sys_pwrite64(unsigned int fd, const char __user *buf,
> size_t count, loff_t pos)
> @@ -337,6 +338,7 @@ asmlinkage ssize_t sys_pwrite64(unsigned
>
> return ret;
> }
> +EXPORT_SYMBOL_GPL(sys_pwrite64);
>
> /*
> * Reduce an iovec's length in-place. Return the resulting number of segments
>
>
> --
> --
> 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:[email protected]"> [email protected] </a> <br />
>

--
--
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:[email protected]"> [email protected] </a> <br />