From: Lachlan McIlroy <lachlan@sgi.com>
To: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] Don't do I/O beyond eof when unreserving space
Date: Tue, 02 Sep 2008 15:24:57 +1000 [thread overview]
Message-ID: <48BCCE29.3070707@sgi.com> (raw)
When unreserving space with boundaries that are not block aligned we round
up the start and round down the end boundaries and then use this function,
xfs_zero_remaining_bytes(), to zero the parts of the blocks that got dropped
during the rounding. The problem is we don't consider if these blocks are
beyond eof. Worse still is if we encounter delayed allocations beyond eof
we will try to use the magic delayed allocation block number as a real block
number. If the file size is ever extended to expose these blocks then we'll
go through xfs_zero_eof() to zero them anyway.
--- a/fs/xfs/xfs_vnodeops.c 2008-09-02 14:54:24.000000000 +1000
+++ b/fs/xfs/xfs_vnodeops.c 2008-09-02 14:51:03.000000000 +1000
@@ -3176,6 +3176,12 @@ xfs_zero_remaining_bytes(
int nimap;
int error = 0;
+ if (startoff >= ip->i_size)
+ return 0;
+
+ if (endoff > ip->i_size)
+ endoff = ip->i_size;
+
bp = xfs_buf_get_noaddr(mp->m_sb.sb_blocksize,
XFS_IS_REALTIME_INODE(ip) ?
mp->m_rtdev_targp : mp->m_ddev_targp);
next reply other threads:[~2008-09-02 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 5:24 Lachlan McIlroy [this message]
2008-09-02 21:51 ` [PATCH] Don't do I/O beyond eof when unreserving space Christoph Hellwig
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=48BCCE29.3070707@sgi.com \
--to=lachlan@sgi.com \
--cc=xfs-dev@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox