From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: 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 18:52:04 +0100 [thread overview]
Message-ID: <20040929175204.GA6488@lkcl.net> (raw)
In-Reply-To: <20040929125835.GA6764@lkcl.net>
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:lkcl@lkcl.net"> lkcl@lkcl.net </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:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
prev parent reply other threads:[~2004-09-29 17:41 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
2004-09-29 14:37 ` Luke Kenneth Casson Leighton
2004-09-29 17:52 ` Luke Kenneth Casson Leighton [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=20040929175204.GA6488@lkcl.net \
--to=lkcl@lkcl.net \
--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