From: Michal Simek <michal.simek@petalogix.com>
To: monstr@monstr.eu
Cc: linux-aio@kvack.org,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: generic_file_aio_write on nfs
Date: Mon, 13 Jul 2009 17:37:02 +0200 [thread overview]
Message-ID: <4A5B549E.4040003@petalogix.com> (raw)
In-Reply-To: <4A4C6EA4.9030108@monstr.eu>
Hi All,
can someone met with problem writev01, writev03, writev04?
Kernel patch below solve my issue but I have no idea why I couldn't use
generic aio write function.
Thanks,
Michal
> Hi Benjamin,
>
> I am doing LTP tests on Microblaze cpu and I am getting some faults.
> I found that the problem is caused by generic_file_aio_write function.
> I did quick patch with disable usage of generic_file_aio_write function and
> use only write function which works. I haven't debug
> generic_file_aio_write function.
>
> I am running Linux with initramfs and LTP programs are run from nfs.
>
> Have you ever met with this problem?
>
> Thanks,
> Michal
>
> [monstr@monstr linux-monstr.eu-commit]$ git diff fs/read_write.c
> diff --git a/fs/read_write.c b/fs/read_write.c
> index 400fe81..e639098 100644
> --- a/fs/read_write.c
> +++ b/fs/read_write.c
> @@ -642,7 +642,8 @@ static ssize_t do_readv_writev(int type, struct file
> *file,
> fnv = file->f_op->aio_read;
> } else {
> fn = (io_fn_t)file->f_op->write;
> - fnv = file->f_op->aio_write;
> + //fnv = file->f_op->aio_write;
> + fnv = 0;
> }
>
> if (fnv)
>
>
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
prev parent reply other threads:[~2009-07-13 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 8:24 generic_file_aio_write on nfs Michal Simek
2009-07-13 15:37 ` Michal Simek [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=4A5B549E.4040003@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=arnd@arndb.de \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
/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