lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 5 Jan 2012 15:40:05 +0100 From: Jan Kara <jack@...e.cz> To: linux-fsdevel@...r.kernel.org Cc: linux-ext4@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Christoph Hellwig <hch@...radead.org>, Al Viro <viro@...IV.linux.org.uk>, LKML <linux-kernel@...r.kernel.org>, Edward Shishkin <edward@...hat.com>, Jan Kara <jack@...e.cz> Subject: [PATCH 1/3] fs: Convert checks for write IO errors from !buffer_uptodate to buffer_write_io_error Convert a few remaining checks for write IO error in VFS using !buffer_uptodate test to using buffer_write_io_error. Signed-off-by: Jan Kara <jack@...e.cz> --- fs/buffer.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/buffer.c b/fs/buffer.c index 19d8eb7..3469d53 100644 --- a/fs/buffer.c +++ b/fs/buffer.c @@ -550,7 +550,7 @@ repeat: get_bh(bh); spin_unlock(lock); wait_on_buffer(bh); - if (!buffer_uptodate(bh)) + if (buffer_write_io_error(bh)) err = -EIO; brelse(bh); spin_lock(lock); @@ -810,7 +810,7 @@ static int fsync_buffers_list(spinlock_t *lock, struct list_head *list) } spin_unlock(lock); wait_on_buffer(bh); - if (!buffer_uptodate(bh)) + if (buffer_write_io_error(bh)) err = -EIO; brelse(bh); spin_lock(lock); @@ -3039,7 +3039,7 @@ int __sync_dirty_buffer(struct buffer_head *bh, int rw) bh->b_end_io = end_buffer_write_sync; ret = submit_bh(rw, bh); wait_on_buffer(bh); - if (!ret && !buffer_uptodate(bh)) + if (!ret && buffer_write_io_error(bh)) ret = -EIO; } else { unlock_buffer(bh); -- 1.7.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists