From: Dmitriy Monakhov <dmonakhov@sw.ru>
To: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, npiggin@suse.de,
mark.fasheh@oracle.com, linux-ext4@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: iov_iter_fault_in_readable fix
Date: Sat, 16 Jun 2007 22:17:51 +0400 [thread overview]
Message-ID: <20070616181751.GE14349@localhost.sw.ru> (raw)
In-Reply-To: <20070614173153.GA14771@infradead.org>
On 18:31 Чтв 14 Июн , Christoph Hellwig wrote:
> On Wed, Jun 13, 2007 at 05:57:59PM +0400, Dmitriy Monakhov wrote:
> > Function prerform check for signgle region, with out respect to
> > segment nature of iovec, For example writev no longer works :)
>
> Btw, could someone please start to collect all sniplets like this in
> a nice simple regression test suite? If no one wants to start a new
> one we should probably just put it into xfsqa (which should be useable
> for other filesystems aswell despite the name)
I've prepared testcase (testcases/kernel/syscalls/writev/writev06.c)
and sent it to ltp mailing list.
prev parent reply other threads:[~2007-06-16 18:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 21:19 + fs-introduce-write_begin-write_end-and-perform_write-aops.patch added to -mm tree akpm
2007-05-30 3:13 ` Nick Piggin
2007-05-30 3:24 ` Andrew Morton
2007-05-30 22:44 ` Mark Fasheh
2007-05-30 22:49 ` Andrew Morton
2007-05-30 10:39 ` Steven Whitehouse
2007-05-31 5:50 ` Nick Piggin
2007-06-13 13:40 ` Dmitriy Monakhov
2007-06-13 11:43 ` Nick Piggin
2007-06-13 18:51 ` Dmitriy Monakhov
2007-06-13 23:07 ` Badari Pulavarty
2007-06-13 23:28 ` Nick Piggin
2007-06-14 9:52 ` Jan Kara
2007-06-14 10:39 ` Nick Piggin
2007-06-13 13:50 ` [patch] new aop block_write_begin fix Dmitriy Monakhov
2007-06-13 13:57 ` iov_iter_fault_in_readable fix Dmitriy Monakhov
2007-06-14 17:31 ` Christoph Hellwig
2007-06-14 22:21 ` David Chinner
2007-06-14 22:34 ` Christoph Hellwig
2007-06-16 18:17 ` Dmitriy Monakhov [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=20070616181751.GE14349@localhost.sw.ru \
--to=dmonakhov@sw.ru \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=npiggin@suse.de \
--cc=xfs@oss.sgi.com \
/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.