From: "Lukáš Czerner" <lczerner@redhat.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-ext4@vger.kernel.org
Subject: re: ext4: refactor ext4_fallocate code
Date: Mon, 31 Mar 2014 10:43:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1403311042100.4996@localhost.localdomain> (raw)
In-Reply-To: <20140328080432.GC25192@mwanda>
On Fri, 28 Mar 2014, Dan Carpenter wrote:
> Date: Fri, 28 Mar 2014 11:04:32 +0300
> From: Dan Carpenter <dan.carpenter@oracle.com>
> To: lczerner@redhat.com
> Cc: linux-ext4@vger.kernel.org
> Subject: re: ext4: refactor ext4_fallocate code
>
> Hello Lukas Czerner,
>
> The patch f6a7718e9581: "ext4: refactor ext4_fallocate code" from Mar
> 18, 2014, leads to the following static checker warning:
>
> fs/ext4/extents.c:4926 ext4_fallocate()
> warn: we tested 'ret' before and it was 'false'
>
> fs/ext4/extents.c
> 4916 ret = ext4_alloc_file_blocks(file, lblk, max_blocks, flags, mode);
> 4917 if (ret)
> ^^^
> Checked.
>
> 4918 goto out;
> 4919
> 4920 handle = ext4_journal_start(inode, EXT4_HT_INODE, 2);
> 4921 if (IS_ERR(handle))
> 4922 goto out;
> 4923
> 4924 tv = inode->i_ctime = ext4_current_time(inode);
> 4925
> 4926 if (!ret && new_size) {
> ^^^^
> Known.
>
> 4927 if (new_size > i_size_read(inode)) {
> 4928 i_size_write(inode, new_size);
> 4929 inode->i_mtime = tv;
> 4930 }
> 4931 if (new_size > EXT4_I(inode)->i_disksize)
> 4932 ext4_update_i_disksize(inode, new_size);
> 4933 } else if (!ret && !new_size) {
> ^^^^
> Known.
Right,
and this is true for the other function we;re using
ext4_alloc_file_blocks().
Thanks!
-Lukas
>
> 4934 /*
> 4935 * Mark that we allocate beyond EOF so the subsequent truncate
> 4936 * can proceed even if the new size is the same as i_size.
> 4937 */
> 4938 if ((offset + len) > i_size_read(inode))
> 4939 ext4_set_inode_flag(inode, EXT4_INODE_EOFBLOCKS);
> 4940 }
>
> regards,
> dan carpenter
>
prev parent reply other threads:[~2014-03-31 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 8:04 ext4: refactor ext4_fallocate code Dan Carpenter
2014-03-31 8:43 ` Lukáš Czerner [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=alpine.LFD.2.00.1403311042100.4996@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).