2010-10-27 19:30:10 -06:00
|
|
|
/*
|
|
|
|
* linux/fs/ext4/page-io.c
|
|
|
|
*
|
|
|
|
* This contains the new page_io functions for ext4
|
|
|
|
*
|
|
|
|
* Written by Theodore Ts'o, 2010.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/fs.h>
|
|
|
|
#include <linux/time.h>
|
|
|
|
#include <linux/jbd2.h>
|
|
|
|
#include <linux/highuid.h>
|
|
|
|
#include <linux/pagemap.h>
|
|
|
|
#include <linux/quotaops.h>
|
|
|
|
#include <linux/string.h>
|
|
|
|
#include <linux/buffer_head.h>
|
|
|
|
#include <linux/writeback.h>
|
|
|
|
#include <linux/pagevec.h>
|
|
|
|
#include <linux/mpage.h>
|
|
|
|
#include <linux/namei.h>
|
|
|
|
#include <linux/uio.h>
|
|
|
|
#include <linux/bio.h>
|
|
|
|
#include <linux/workqueue.h>
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
|
|
|
|
#include "ext4_jbd2.h"
|
|
|
|
#include "xattr.h"
|
|
|
|
#include "acl.h"
|
|
|
|
#include "ext4_extents.h"
|
|
|
|
|
|
|
|
static struct kmem_cache *io_page_cachep, *io_end_cachep;
|
|
|
|
|
2010-10-27 19:30:14 -06:00
|
|
|
int __init ext4_init_pageio(void)
|
2010-10-27 19:30:10 -06:00
|
|
|
{
|
|
|
|
io_page_cachep = KMEM_CACHE(ext4_io_page, SLAB_RECLAIM_ACCOUNT);
|
|
|
|
if (io_page_cachep == NULL)
|
|
|
|
return -ENOMEM;
|
|
|
|
io_end_cachep = KMEM_CACHE(ext4_io_end, SLAB_RECLAIM_ACCOUNT);
|
2011-01-10 10:10:44 -07:00
|
|
|
if (io_end_cachep == NULL) {
|
2010-10-27 19:30:10 -06:00
|
|
|
kmem_cache_destroy(io_page_cachep);
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2010-10-27 19:30:14 -06:00
|
|
|
void ext4_exit_pageio(void)
|
2010-10-27 19:30:10 -06:00
|
|
|
{
|
|
|
|
kmem_cache_destroy(io_end_cachep);
|
|
|
|
kmem_cache_destroy(io_page_cachep);
|
|
|
|
}
|
|
|
|
|
2010-11-08 11:43:33 -07:00
|
|
|
void ext4_ioend_wait(struct inode *inode)
|
|
|
|
{
|
ext4: serialize unaligned asynchronous DIO
ext4 has a data corruption case when doing non-block-aligned
asynchronous direct IO into a sparse file, as demonstrated
by xfstest 240.
The root cause is that while ext4 preallocates space in the
hole, mappings of that space still look "new" and
dio_zero_block() will zero out the unwritten portions. When
more than one AIO thread is going, they both find this "new"
block and race to zero out their portion; this is uncoordinated
and causes data corruption.
Dave Chinner fixed this for xfs by simply serializing all
unaligned asynchronous direct IO. I've done the same here.
The difference is that we only wait on conversions, not all IO.
This is a very big hammer, and I'm not very pleased with
stuffing this into ext4_file_write(). But since ext4 is
DIO_LOCKING, we need to serialize it at this high level.
I tried to move this into ext4_ext_direct_IO, but by then
we have the i_mutex already, and we will wait on the
work queue to do conversions - which must also take the
i_mutex. So that won't work.
This was originally exposed by qemu-kvm installing to
a raw disk image with a normal sector-63 alignment. I've
tested a backport of this patch with qemu, and it does
avoid the corruption. It is also quite a lot slower
(14 min for package installs, vs. 8 min for well-aligned)
but I'll take slow correctness over fast corruption any day.
Mingming suggested that we can track outstanding
conversions, and wait on those so that non-sparse
files won't be affected, and I've implemented that here;
unaligned AIO to nonsparse files won't take a perf hit.
[tytso@mit.edu: Keep the mutex as a hashed array instead
of bloating the ext4 inode]
[tytso@mit.edu: Fix up namespace issues so that global
variables are protected with an "ext4_" prefix.]
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-02-12 06:17:34 -07:00
|
|
|
wait_queue_head_t *wq = ext4_ioend_wq(inode);
|
2010-11-08 11:43:33 -07:00
|
|
|
|
|
|
|
wait_event(*wq, (atomic_read(&EXT4_I(inode)->i_ioend_count) == 0));
|
|
|
|
}
|
|
|
|
|
2010-11-08 11:45:33 -07:00
|
|
|
static void put_io_page(struct ext4_io_page *io_page)
|
|
|
|
{
|
|
|
|
if (atomic_dec_and_test(&io_page->p_count)) {
|
|
|
|
end_page_writeback(io_page->p_page);
|
|
|
|
put_page(io_page->p_page);
|
|
|
|
kmem_cache_free(io_page_cachep, io_page);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2010-10-27 19:30:10 -06:00
|
|
|
void ext4_free_io_end(ext4_io_end_t *io)
|
|
|
|
{
|
|
|
|
int i;
|
2010-11-08 11:43:33 -07:00
|
|
|
wait_queue_head_t *wq;
|
2010-10-27 19:30:10 -06:00
|
|
|
|
|
|
|
BUG_ON(!io);
|
|
|
|
if (io->page)
|
|
|
|
put_page(io->page);
|
2010-11-08 11:45:33 -07:00
|
|
|
for (i = 0; i < io->num_io_pages; i++)
|
|
|
|
put_io_page(io->pages[i]);
|
2010-10-27 19:30:10 -06:00
|
|
|
io->num_io_pages = 0;
|
ext4: serialize unaligned asynchronous DIO
ext4 has a data corruption case when doing non-block-aligned
asynchronous direct IO into a sparse file, as demonstrated
by xfstest 240.
The root cause is that while ext4 preallocates space in the
hole, mappings of that space still look "new" and
dio_zero_block() will zero out the unwritten portions. When
more than one AIO thread is going, they both find this "new"
block and race to zero out their portion; this is uncoordinated
and causes data corruption.
Dave Chinner fixed this for xfs by simply serializing all
unaligned asynchronous direct IO. I've done the same here.
The difference is that we only wait on conversions, not all IO.
This is a very big hammer, and I'm not very pleased with
stuffing this into ext4_file_write(). But since ext4 is
DIO_LOCKING, we need to serialize it at this high level.
I tried to move this into ext4_ext_direct_IO, but by then
we have the i_mutex already, and we will wait on the
work queue to do conversions - which must also take the
i_mutex. So that won't work.
This was originally exposed by qemu-kvm installing to
a raw disk image with a normal sector-63 alignment. I've
tested a backport of this patch with qemu, and it does
avoid the corruption. It is also quite a lot slower
(14 min for package installs, vs. 8 min for well-aligned)
but I'll take slow correctness over fast corruption any day.
Mingming suggested that we can track outstanding
conversions, and wait on those so that non-sparse
files won't be affected, and I've implemented that here;
unaligned AIO to nonsparse files won't take a perf hit.
[tytso@mit.edu: Keep the mutex as a hashed array instead
of bloating the ext4 inode]
[tytso@mit.edu: Fix up namespace issues so that global
variables are protected with an "ext4_" prefix.]
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-02-12 06:17:34 -07:00
|
|
|
wq = ext4_ioend_wq(io->inode);
|
2010-11-08 11:43:33 -07:00
|
|
|
if (atomic_dec_and_test(&EXT4_I(io->inode)->i_ioend_count) &&
|
|
|
|
waitqueue_active(wq))
|
|
|
|
wake_up_all(wq);
|
2010-10-27 19:30:10 -06:00
|
|
|
kmem_cache_free(io_end_cachep, io);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* check a range of space and convert unwritten extents to written.
|
|
|
|
*/
|
|
|
|
int ext4_end_io_nolock(ext4_io_end_t *io)
|
|
|
|
{
|
|
|
|
struct inode *inode = io->inode;
|
|
|
|
loff_t offset = io->offset;
|
|
|
|
ssize_t size = io->size;
|
ext4: serialize unaligned asynchronous DIO
ext4 has a data corruption case when doing non-block-aligned
asynchronous direct IO into a sparse file, as demonstrated
by xfstest 240.
The root cause is that while ext4 preallocates space in the
hole, mappings of that space still look "new" and
dio_zero_block() will zero out the unwritten portions. When
more than one AIO thread is going, they both find this "new"
block and race to zero out their portion; this is uncoordinated
and causes data corruption.
Dave Chinner fixed this for xfs by simply serializing all
unaligned asynchronous direct IO. I've done the same here.
The difference is that we only wait on conversions, not all IO.
This is a very big hammer, and I'm not very pleased with
stuffing this into ext4_file_write(). But since ext4 is
DIO_LOCKING, we need to serialize it at this high level.
I tried to move this into ext4_ext_direct_IO, but by then
we have the i_mutex already, and we will wait on the
work queue to do conversions - which must also take the
i_mutex. So that won't work.
This was originally exposed by qemu-kvm installing to
a raw disk image with a normal sector-63 alignment. I've
tested a backport of this patch with qemu, and it does
avoid the corruption. It is also quite a lot slower
(14 min for package installs, vs. 8 min for well-aligned)
but I'll take slow correctness over fast corruption any day.
Mingming suggested that we can track outstanding
conversions, and wait on those so that non-sparse
files won't be affected, and I've implemented that here;
unaligned AIO to nonsparse files won't take a perf hit.
[tytso@mit.edu: Keep the mutex as a hashed array instead
of bloating the ext4 inode]
[tytso@mit.edu: Fix up namespace issues so that global
variables are protected with an "ext4_" prefix.]
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-02-12 06:17:34 -07:00
|
|
|
wait_queue_head_t *wq;
|
2010-10-27 19:30:10 -06:00
|
|
|
int ret = 0;
|
|
|
|
|
|
|
|
ext4_debug("ext4_end_io_nolock: io 0x%p from inode %lu,list->next 0x%p,"
|
|
|
|
"list->prev 0x%p\n",
|
|
|
|
io, inode->i_ino, io->list.next, io->list.prev);
|
|
|
|
|
|
|
|
if (list_empty(&io->list))
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
if (!(io->flag & EXT4_IO_END_UNWRITTEN))
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
ret = ext4_convert_unwritten_extents(inode, offset, size);
|
|
|
|
if (ret < 0) {
|
|
|
|
printk(KERN_EMERG "%s: failed to convert unwritten "
|
|
|
|
"extents to written extents, error is %d "
|
|
|
|
"io is still on inode %lu aio dio list\n",
|
|
|
|
__func__, ret, inode->i_ino);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (io->iocb)
|
|
|
|
aio_complete(io->iocb, io->result, 0);
|
|
|
|
/* clear the DIO AIO unwritten flag */
|
ext4: serialize unaligned asynchronous DIO
ext4 has a data corruption case when doing non-block-aligned
asynchronous direct IO into a sparse file, as demonstrated
by xfstest 240.
The root cause is that while ext4 preallocates space in the
hole, mappings of that space still look "new" and
dio_zero_block() will zero out the unwritten portions. When
more than one AIO thread is going, they both find this "new"
block and race to zero out their portion; this is uncoordinated
and causes data corruption.
Dave Chinner fixed this for xfs by simply serializing all
unaligned asynchronous direct IO. I've done the same here.
The difference is that we only wait on conversions, not all IO.
This is a very big hammer, and I'm not very pleased with
stuffing this into ext4_file_write(). But since ext4 is
DIO_LOCKING, we need to serialize it at this high level.
I tried to move this into ext4_ext_direct_IO, but by then
we have the i_mutex already, and we will wait on the
work queue to do conversions - which must also take the
i_mutex. So that won't work.
This was originally exposed by qemu-kvm installing to
a raw disk image with a normal sector-63 alignment. I've
tested a backport of this patch with qemu, and it does
avoid the corruption. It is also quite a lot slower
(14 min for package installs, vs. 8 min for well-aligned)
but I'll take slow correctness over fast corruption any day.
Mingming suggested that we can track outstanding
conversions, and wait on those so that non-sparse
files won't be affected, and I've implemented that here;
unaligned AIO to nonsparse files won't take a perf hit.
[tytso@mit.edu: Keep the mutex as a hashed array instead
of bloating the ext4 inode]
[tytso@mit.edu: Fix up namespace issues so that global
variables are protected with an "ext4_" prefix.]
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
2011-02-12 06:17:34 -07:00
|
|
|
if (io->flag & EXT4_IO_END_UNWRITTEN) {
|
|
|
|
io->flag &= ~EXT4_IO_END_UNWRITTEN;
|
|
|
|
/* Wake up anyone waiting on unwritten extent conversion */
|
|
|
|
wq = ext4_ioend_wq(io->inode);
|
|
|
|
if (atomic_dec_and_test(&EXT4_I(inode)->i_aiodio_unwritten) &&
|
|
|
|
waitqueue_active(wq)) {
|
|
|
|
wake_up_all(wq);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2010-10-27 19:30:10 -06:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* work on completed aio dio IO, to convert unwritten extents to extents
|
|
|
|
*/
|
|
|
|
static void ext4_end_io_work(struct work_struct *work)
|
|
|
|
{
|
|
|
|
ext4_io_end_t *io = container_of(work, ext4_io_end_t, work);
|
|
|
|
struct inode *inode = io->inode;
|
|
|
|
struct ext4_inode_info *ei = EXT4_I(inode);
|
|
|
|
unsigned long flags;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
mutex_lock(&inode->i_mutex);
|
|
|
|
ret = ext4_end_io_nolock(io);
|
|
|
|
if (ret < 0) {
|
|
|
|
mutex_unlock(&inode->i_mutex);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
spin_lock_irqsave(&ei->i_completed_io_lock, flags);
|
|
|
|
if (!list_empty(&io->list))
|
|
|
|
list_del_init(&io->list);
|
|
|
|
spin_unlock_irqrestore(&ei->i_completed_io_lock, flags);
|
|
|
|
mutex_unlock(&inode->i_mutex);
|
|
|
|
ext4_free_io_end(io);
|
|
|
|
}
|
|
|
|
|
|
|
|
ext4_io_end_t *ext4_init_io_end(struct inode *inode, gfp_t flags)
|
|
|
|
{
|
2010-12-19 19:41:55 -07:00
|
|
|
ext4_io_end_t *io = kmem_cache_zalloc(io_end_cachep, flags);
|
2010-10-27 19:30:10 -06:00
|
|
|
if (io) {
|
2010-11-08 11:43:33 -07:00
|
|
|
atomic_inc(&EXT4_I(inode)->i_ioend_count);
|
|
|
|
io->inode = inode;
|
2010-10-27 19:30:10 -06:00
|
|
|
INIT_WORK(&io->work, ext4_end_io_work);
|
|
|
|
INIT_LIST_HEAD(&io->list);
|
|
|
|
}
|
|
|
|
return io;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Print an buffer I/O error compatible with the fs/buffer.c. This
|
|
|
|
* provides compatibility with dmesg scrapers that look for a specific
|
|
|
|
* buffer I/O error message. We really need a unified error reporting
|
|
|
|
* structure to userspace ala Digital Unix's uerf system, but it's
|
|
|
|
* probably not going to happen in my lifetime, due to LKML politics...
|
|
|
|
*/
|
|
|
|
static void buffer_io_error(struct buffer_head *bh)
|
|
|
|
{
|
|
|
|
char b[BDEVNAME_SIZE];
|
|
|
|
printk(KERN_ERR "Buffer I/O error on device %s, logical block %llu\n",
|
|
|
|
bdevname(bh->b_bdev, b),
|
|
|
|
(unsigned long long)bh->b_blocknr);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ext4_end_bio(struct bio *bio, int error)
|
|
|
|
{
|
|
|
|
ext4_io_end_t *io_end = bio->bi_private;
|
|
|
|
struct workqueue_struct *wq;
|
|
|
|
struct inode *inode;
|
|
|
|
unsigned long flags;
|
|
|
|
int i;
|
ext4: Fix data corruption with multi-block writepages support
This fixes a corruption problem with the multi-block
writepages submittal change for ext4, from commit
bd2d0210cf22f2bd0cef72eb97cf94fc7d31d8cc ("ext4: use bio
layer instead of buffer layer in mpage_da_submit_io").
(Note that this corruption is not present in 2.6.37 on
ext4, because the corruption was detected after the
feature was merged in 2.6.37-rc1, and so it was turned
off by adding a non-default mount option,
mblk_io_submit. With this commit, which hopefully
fixes the last of the bugs with this feature, we'll be
able to turn on this performance feature by default in
2.6.38, and remove the mblk_io_submit option.)
The ext4 code path to bundle multiple pages for
writeback in ext4_bio_write_page() had a bug: we should
be clearing buffer head dirty flags *before* we submit
the bio, not in the completion routine.
The patch below was tested on 2.6.37 under KVM with the
postgresql script which was submitted by Jon Nelson as
documented in commit 1449032be1.
Without the patch, I'd hit the corruption problem about
50-70% of the time. With the patch, I executed the
script > 100 times with no corruption seen.
I also fixed a bug to make sure ext4_end_bio() doesn't
dereference the bio after the bio_put() call.
Reported-by: Jon Nelson <jnelson@jamponi.net>
Reported-by: Matthias Bayer <jackdachef@gmail.com>
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@kernel.org
2011-02-07 10:46:14 -07:00
|
|
|
sector_t bi_sector = bio->bi_sector;
|
2010-10-27 19:30:10 -06:00
|
|
|
|
|
|
|
BUG_ON(!io_end);
|
|
|
|
bio->bi_private = NULL;
|
|
|
|
bio->bi_end_io = NULL;
|
|
|
|
if (test_bit(BIO_UPTODATE, &bio->bi_flags))
|
|
|
|
error = 0;
|
|
|
|
bio_put(bio);
|
|
|
|
|
|
|
|
for (i = 0; i < io_end->num_io_pages; i++) {
|
|
|
|
struct page *page = io_end->pages[i]->p_page;
|
|
|
|
struct buffer_head *bh, *head;
|
|
|
|
int partial_write = 0;
|
|
|
|
|
|
|
|
head = page_buffers(page);
|
|
|
|
if (error)
|
|
|
|
SetPageError(page);
|
|
|
|
BUG_ON(!head);
|
ext4: Fix data corruption with multi-block writepages support
This fixes a corruption problem with the multi-block
writepages submittal change for ext4, from commit
bd2d0210cf22f2bd0cef72eb97cf94fc7d31d8cc ("ext4: use bio
layer instead of buffer layer in mpage_da_submit_io").
(Note that this corruption is not present in 2.6.37 on
ext4, because the corruption was detected after the
feature was merged in 2.6.37-rc1, and so it was turned
off by adding a non-default mount option,
mblk_io_submit. With this commit, which hopefully
fixes the last of the bugs with this feature, we'll be
able to turn on this performance feature by default in
2.6.38, and remove the mblk_io_submit option.)
The ext4 code path to bundle multiple pages for
writeback in ext4_bio_write_page() had a bug: we should
be clearing buffer head dirty flags *before* we submit
the bio, not in the completion routine.
The patch below was tested on 2.6.37 under KVM with the
postgresql script which was submitted by Jon Nelson as
documented in commit 1449032be1.
Without the patch, I'd hit the corruption problem about
50-70% of the time. With the patch, I executed the
script > 100 times with no corruption seen.
I also fixed a bug to make sure ext4_end_bio() doesn't
dereference the bio after the bio_put() call.
Reported-by: Jon Nelson <jnelson@jamponi.net>
Reported-by: Matthias Bayer <jackdachef@gmail.com>
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@kernel.org
2011-02-07 10:46:14 -07:00
|
|
|
if (head->b_size != PAGE_CACHE_SIZE) {
|
2010-10-27 19:30:10 -06:00
|
|
|
loff_t offset;
|
|
|
|
loff_t io_end_offset = io_end->offset + io_end->size;
|
|
|
|
|
|
|
|
offset = (sector_t) page->index << PAGE_CACHE_SHIFT;
|
|
|
|
bh = head;
|
|
|
|
do {
|
|
|
|
if ((offset >= io_end->offset) &&
|
|
|
|
(offset+bh->b_size <= io_end_offset)) {
|
|
|
|
if (error)
|
|
|
|
buffer_io_error(bh);
|
|
|
|
|
|
|
|
}
|
|
|
|
if (buffer_delay(bh))
|
|
|
|
partial_write = 1;
|
|
|
|
else if (!buffer_mapped(bh))
|
|
|
|
clear_buffer_dirty(bh);
|
|
|
|
else if (buffer_dirty(bh))
|
|
|
|
partial_write = 1;
|
|
|
|
offset += bh->b_size;
|
|
|
|
bh = bh->b_this_page;
|
|
|
|
} while (bh != head);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If this is a partial write which happened to make
|
|
|
|
* all buffers uptodate then we can optimize away a
|
|
|
|
* bogus readpage() for the next read(). Here we
|
|
|
|
* 'discover' whether the page went uptodate as a
|
|
|
|
* result of this (potentially partial) write.
|
|
|
|
*/
|
|
|
|
if (!partial_write)
|
|
|
|
SetPageUptodate(page);
|
2010-11-17 19:46:06 -07:00
|
|
|
|
|
|
|
put_io_page(io_end->pages[i]);
|
2010-10-27 19:30:10 -06:00
|
|
|
}
|
|
|
|
io_end->num_io_pages = 0;
|
2010-11-08 11:43:33 -07:00
|
|
|
inode = io_end->inode;
|
|
|
|
|
|
|
|
if (error) {
|
|
|
|
io_end->flag |= EXT4_IO_END_ERROR;
|
|
|
|
ext4_warning(inode->i_sb, "I/O error writing to inode %lu "
|
|
|
|
"(offset %llu size %ld starting block %llu)",
|
|
|
|
inode->i_ino,
|
|
|
|
(unsigned long long) io_end->offset,
|
|
|
|
(long) io_end->size,
|
|
|
|
(unsigned long long)
|
ext4: Fix data corruption with multi-block writepages support
This fixes a corruption problem with the multi-block
writepages submittal change for ext4, from commit
bd2d0210cf22f2bd0cef72eb97cf94fc7d31d8cc ("ext4: use bio
layer instead of buffer layer in mpage_da_submit_io").
(Note that this corruption is not present in 2.6.37 on
ext4, because the corruption was detected after the
feature was merged in 2.6.37-rc1, and so it was turned
off by adding a non-default mount option,
mblk_io_submit. With this commit, which hopefully
fixes the last of the bugs with this feature, we'll be
able to turn on this performance feature by default in
2.6.38, and remove the mblk_io_submit option.)
The ext4 code path to bundle multiple pages for
writeback in ext4_bio_write_page() had a bug: we should
be clearing buffer head dirty flags *before* we submit
the bio, not in the completion routine.
The patch below was tested on 2.6.37 under KVM with the
postgresql script which was submitted by Jon Nelson as
documented in commit 1449032be1.
Without the patch, I'd hit the corruption problem about
50-70% of the time. With the patch, I executed the
script > 100 times with no corruption seen.
I also fixed a bug to make sure ext4_end_bio() doesn't
dereference the bio after the bio_put() call.
Reported-by: Jon Nelson <jnelson@jamponi.net>
Reported-by: Matthias Bayer <jackdachef@gmail.com>
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@kernel.org
2011-02-07 10:46:14 -07:00
|
|
|
bi_sector >> (inode->i_blkbits - 9));
|
2010-11-08 11:43:33 -07:00
|
|
|
}
|
2010-10-27 19:30:10 -06:00
|
|
|
|
|
|
|
/* Add the io_end to per-inode completed io list*/
|
|
|
|
spin_lock_irqsave(&EXT4_I(inode)->i_completed_io_lock, flags);
|
|
|
|
list_add_tail(&io_end->list, &EXT4_I(inode)->i_completed_io_list);
|
|
|
|
spin_unlock_irqrestore(&EXT4_I(inode)->i_completed_io_lock, flags);
|
|
|
|
|
|
|
|
wq = EXT4_SB(inode->i_sb)->dio_unwritten_wq;
|
|
|
|
/* queue the work to convert unwritten extents to written */
|
|
|
|
queue_work(wq, &io_end->work);
|
|
|
|
}
|
|
|
|
|
|
|
|
void ext4_io_submit(struct ext4_io_submit *io)
|
|
|
|
{
|
|
|
|
struct bio *bio = io->io_bio;
|
|
|
|
|
|
|
|
if (bio) {
|
|
|
|
bio_get(io->io_bio);
|
|
|
|
submit_bio(io->io_op, io->io_bio);
|
|
|
|
BUG_ON(bio_flagged(io->io_bio, BIO_EOPNOTSUPP));
|
|
|
|
bio_put(io->io_bio);
|
|
|
|
}
|
|
|
|
io->io_bio = 0;
|
|
|
|
io->io_op = 0;
|
|
|
|
io->io_end = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int io_submit_init(struct ext4_io_submit *io,
|
|
|
|
struct inode *inode,
|
|
|
|
struct writeback_control *wbc,
|
|
|
|
struct buffer_head *bh)
|
|
|
|
{
|
|
|
|
ext4_io_end_t *io_end;
|
|
|
|
struct page *page = bh->b_page;
|
|
|
|
int nvecs = bio_get_nr_vecs(bh->b_bdev);
|
|
|
|
struct bio *bio;
|
|
|
|
|
|
|
|
io_end = ext4_init_io_end(inode, GFP_NOFS);
|
|
|
|
if (!io_end)
|
|
|
|
return -ENOMEM;
|
|
|
|
do {
|
|
|
|
bio = bio_alloc(GFP_NOIO, nvecs);
|
|
|
|
nvecs >>= 1;
|
|
|
|
} while (bio == NULL);
|
|
|
|
|
|
|
|
bio->bi_sector = bh->b_blocknr * (bh->b_size >> 9);
|
|
|
|
bio->bi_bdev = bh->b_bdev;
|
|
|
|
bio->bi_private = io->io_end = io_end;
|
|
|
|
bio->bi_end_io = ext4_end_bio;
|
|
|
|
|
|
|
|
io_end->offset = (page->index << PAGE_CACHE_SHIFT) + bh_offset(bh);
|
|
|
|
|
|
|
|
io->io_bio = bio;
|
|
|
|
io->io_op = (wbc->sync_mode == WB_SYNC_ALL ?
|
|
|
|
WRITE_SYNC_PLUG : WRITE);
|
|
|
|
io->io_next_block = bh->b_blocknr;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int io_submit_add_bh(struct ext4_io_submit *io,
|
|
|
|
struct ext4_io_page *io_page,
|
|
|
|
struct inode *inode,
|
|
|
|
struct writeback_control *wbc,
|
|
|
|
struct buffer_head *bh)
|
|
|
|
{
|
|
|
|
ext4_io_end_t *io_end;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
if (buffer_new(bh)) {
|
|
|
|
clear_buffer_new(bh);
|
|
|
|
unmap_underlying_metadata(bh->b_bdev, bh->b_blocknr);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!buffer_mapped(bh) || buffer_delay(bh)) {
|
|
|
|
if (!buffer_mapped(bh))
|
|
|
|
clear_buffer_dirty(bh);
|
|
|
|
if (io->io_bio)
|
|
|
|
ext4_io_submit(io);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (io->io_bio && bh->b_blocknr != io->io_next_block) {
|
|
|
|
submit_and_retry:
|
|
|
|
ext4_io_submit(io);
|
|
|
|
}
|
|
|
|
if (io->io_bio == NULL) {
|
|
|
|
ret = io_submit_init(io, inode, wbc, bh);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
io_end = io->io_end;
|
|
|
|
if ((io_end->num_io_pages >= MAX_IO_PAGES) &&
|
|
|
|
(io_end->pages[io_end->num_io_pages-1] != io_page))
|
|
|
|
goto submit_and_retry;
|
|
|
|
if (buffer_uninit(bh))
|
|
|
|
io->io_end->flag |= EXT4_IO_END_UNWRITTEN;
|
|
|
|
io->io_end->size += bh->b_size;
|
|
|
|
io->io_next_block++;
|
|
|
|
ret = bio_add_page(io->io_bio, bh->b_page, bh->b_size, bh_offset(bh));
|
|
|
|
if (ret != bh->b_size)
|
|
|
|
goto submit_and_retry;
|
|
|
|
if ((io_end->num_io_pages == 0) ||
|
|
|
|
(io_end->pages[io_end->num_io_pages-1] != io_page)) {
|
|
|
|
io_end->pages[io_end->num_io_pages++] = io_page;
|
2010-11-08 11:45:33 -07:00
|
|
|
atomic_inc(&io_page->p_count);
|
2010-10-27 19:30:10 -06:00
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int ext4_bio_write_page(struct ext4_io_submit *io,
|
|
|
|
struct page *page,
|
|
|
|
int len,
|
|
|
|
struct writeback_control *wbc)
|
|
|
|
{
|
|
|
|
struct inode *inode = page->mapping->host;
|
|
|
|
unsigned block_start, block_end, blocksize;
|
|
|
|
struct ext4_io_page *io_page;
|
|
|
|
struct buffer_head *bh, *head;
|
|
|
|
int ret = 0;
|
|
|
|
|
|
|
|
blocksize = 1 << inode->i_blkbits;
|
|
|
|
|
ext4: Fix data corruption with multi-block writepages support
This fixes a corruption problem with the multi-block
writepages submittal change for ext4, from commit
bd2d0210cf22f2bd0cef72eb97cf94fc7d31d8cc ("ext4: use bio
layer instead of buffer layer in mpage_da_submit_io").
(Note that this corruption is not present in 2.6.37 on
ext4, because the corruption was detected after the
feature was merged in 2.6.37-rc1, and so it was turned
off by adding a non-default mount option,
mblk_io_submit. With this commit, which hopefully
fixes the last of the bugs with this feature, we'll be
able to turn on this performance feature by default in
2.6.38, and remove the mblk_io_submit option.)
The ext4 code path to bundle multiple pages for
writeback in ext4_bio_write_page() had a bug: we should
be clearing buffer head dirty flags *before* we submit
the bio, not in the completion routine.
The patch below was tested on 2.6.37 under KVM with the
postgresql script which was submitted by Jon Nelson as
documented in commit 1449032be1.
Without the patch, I'd hit the corruption problem about
50-70% of the time. With the patch, I executed the
script > 100 times with no corruption seen.
I also fixed a bug to make sure ext4_end_bio() doesn't
dereference the bio after the bio_put() call.
Reported-by: Jon Nelson <jnelson@jamponi.net>
Reported-by: Matthias Bayer <jackdachef@gmail.com>
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@kernel.org
2011-02-07 10:46:14 -07:00
|
|
|
BUG_ON(!PageLocked(page));
|
2010-10-27 19:30:10 -06:00
|
|
|
BUG_ON(PageWriteback(page));
|
|
|
|
set_page_writeback(page);
|
|
|
|
ClearPageError(page);
|
|
|
|
|
|
|
|
io_page = kmem_cache_alloc(io_page_cachep, GFP_NOFS);
|
|
|
|
if (!io_page) {
|
|
|
|
set_page_dirty(page);
|
|
|
|
unlock_page(page);
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
io_page->p_page = page;
|
2010-11-08 11:45:33 -07:00
|
|
|
atomic_set(&io_page->p_count, 1);
|
2010-10-27 19:30:10 -06:00
|
|
|
get_page(page);
|
|
|
|
|
|
|
|
for (bh = head = page_buffers(page), block_start = 0;
|
|
|
|
bh != head || !block_start;
|
|
|
|
block_start = block_end, bh = bh->b_this_page) {
|
ext4: Fix data corruption with multi-block writepages support
This fixes a corruption problem with the multi-block
writepages submittal change for ext4, from commit
bd2d0210cf22f2bd0cef72eb97cf94fc7d31d8cc ("ext4: use bio
layer instead of buffer layer in mpage_da_submit_io").
(Note that this corruption is not present in 2.6.37 on
ext4, because the corruption was detected after the
feature was merged in 2.6.37-rc1, and so it was turned
off by adding a non-default mount option,
mblk_io_submit. With this commit, which hopefully
fixes the last of the bugs with this feature, we'll be
able to turn on this performance feature by default in
2.6.38, and remove the mblk_io_submit option.)
The ext4 code path to bundle multiple pages for
writeback in ext4_bio_write_page() had a bug: we should
be clearing buffer head dirty flags *before* we submit
the bio, not in the completion routine.
The patch below was tested on 2.6.37 under KVM with the
postgresql script which was submitted by Jon Nelson as
documented in commit 1449032be1.
Without the patch, I'd hit the corruption problem about
50-70% of the time. With the patch, I executed the
script > 100 times with no corruption seen.
I also fixed a bug to make sure ext4_end_bio() doesn't
dereference the bio after the bio_put() call.
Reported-by: Jon Nelson <jnelson@jamponi.net>
Reported-by: Matthias Bayer <jackdachef@gmail.com>
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@kernel.org
2011-02-07 10:46:14 -07:00
|
|
|
|
2010-10-27 19:30:10 -06:00
|
|
|
block_end = block_start + blocksize;
|
|
|
|
if (block_start >= len) {
|
|
|
|
clear_buffer_dirty(bh);
|
|
|
|
set_buffer_uptodate(bh);
|
|
|
|
continue;
|
|
|
|
}
|
ext4: Fix data corruption with multi-block writepages support
This fixes a corruption problem with the multi-block
writepages submittal change for ext4, from commit
bd2d0210cf22f2bd0cef72eb97cf94fc7d31d8cc ("ext4: use bio
layer instead of buffer layer in mpage_da_submit_io").
(Note that this corruption is not present in 2.6.37 on
ext4, because the corruption was detected after the
feature was merged in 2.6.37-rc1, and so it was turned
off by adding a non-default mount option,
mblk_io_submit. With this commit, which hopefully
fixes the last of the bugs with this feature, we'll be
able to turn on this performance feature by default in
2.6.38, and remove the mblk_io_submit option.)
The ext4 code path to bundle multiple pages for
writeback in ext4_bio_write_page() had a bug: we should
be clearing buffer head dirty flags *before* we submit
the bio, not in the completion routine.
The patch below was tested on 2.6.37 under KVM with the
postgresql script which was submitted by Jon Nelson as
documented in commit 1449032be1.
Without the patch, I'd hit the corruption problem about
50-70% of the time. With the patch, I executed the
script > 100 times with no corruption seen.
I also fixed a bug to make sure ext4_end_bio() doesn't
dereference the bio after the bio_put() call.
Reported-by: Jon Nelson <jnelson@jamponi.net>
Reported-by: Matthias Bayer <jackdachef@gmail.com>
Signed-off-by: Curt Wohlgemuth <curtw@google.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@kernel.org
2011-02-07 10:46:14 -07:00
|
|
|
clear_buffer_dirty(bh);
|
2010-10-27 19:30:10 -06:00
|
|
|
ret = io_submit_add_bh(io, io_page, inode, wbc, bh);
|
|
|
|
if (ret) {
|
|
|
|
/*
|
|
|
|
* We only get here on ENOMEM. Not much else
|
|
|
|
* we can do but mark the page as dirty, and
|
|
|
|
* better luck next time.
|
|
|
|
*/
|
|
|
|
set_page_dirty(page);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
unlock_page(page);
|
|
|
|
/*
|
|
|
|
* If the page was truncated before we could do the writeback,
|
|
|
|
* or we had a memory allocation error while trying to write
|
|
|
|
* the first buffer head, we won't have submitted any pages for
|
|
|
|
* I/O. In that case we need to make sure we've cleared the
|
|
|
|
* PageWriteback bit from the page to prevent the system from
|
|
|
|
* wedging later on.
|
|
|
|
*/
|
2010-11-08 11:45:33 -07:00
|
|
|
put_io_page(io_page);
|
2010-10-27 19:30:10 -06:00
|
|
|
return ret;
|
|
|
|
}
|