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
| ||
|
Message-ID: <20130207154521.GC25392@quack.suse.cz> Date: Thu, 7 Feb 2013 16:45:21 +0100 From: Jan Kara <jack@...e.cz> To: Wang shilong <wangshilong1991@...il.com> Cc: jack@...e.cz, linux-ext4@...r.kernel.org Subject: Re: [PATCH v1 2/3] Ext2: mark inode dirty after the function dquot_free_block_nodirty is called On Thu 07-02-13 22:57:53, Wang shilong wrote: > From: Wang Shilong <wangsl-fnst@...fujitsu.com> > > We should mark inode dirty after the function dquot_free_block_nodirty > is called.Besides,add a check whether it is necessary to call > dquot_free_block_nodirty functon. Thanks. I've added the patch to my tree. Honza > > Signed-off-by: Wang Shilong <wangsl-fnst@...fujitsu.com> > --- > fs/ext2/balloc.c | 15 ++++++++++----- > 1 file changed, 10 insertions(+), 5 deletions(-) > > diff --git a/fs/ext2/balloc.c b/fs/ext2/balloc.c > index 22993a0..9d372bf 100644 > --- a/fs/ext2/balloc.c > +++ b/fs/ext2/balloc.c > @@ -568,8 +568,11 @@ do_more: > } > error_return: > brelse(bitmap_bh); > - release_blocks(sb, freed); > - dquot_free_block_nodirty(inode, freed); > + if (freed) { > + release_blocks(sb, freed); > + dquot_free_block_nodirty(inode, freed); > + mark_inode_dirty(inode); > + } > } > > /** > @@ -1412,9 +1415,11 @@ allocated: > > *errp = 0; > brelse(bitmap_bh); > - dquot_free_block_nodirty(inode, *count-num); > - mark_inode_dirty(inode); > - *count = num; > + if (num < *count) { > + dquot_free_block_nodirty(inode, *count-num); > + mark_inode_dirty(inode); > + *count = num; > + } > return ret_block; > > io_error: > -- > 1.7.11.7 > -- Jan Kara <jack@...e.cz> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists