From: Theodore Ts'o <tytso@mit.edu>
To: "zhangyi (F)" <yi.zhang@huawei.com>
Cc: linux-ext4@vger.kernel.org, adilger.kernel@dilger.ca, miaoxie@huawei.com
Subject: Re: [e2fsprogs PATCH] libsupport: fix error handling in quota_write_inode
Date: Mon, 24 Jul 2017 15:17:22 -0400 [thread overview]
Message-ID: <20170724191722.lhlikwpuzt3te6mf@thunk.org> (raw)
In-Reply-To: <1500879686-741-1-git-send-email-yi.zhang@huawei.com>
On Mon, Jul 24, 2017 at 03:01:26PM +0800, zhangyi (F) wrote:
> The error return value of quota_file_create() is no longer < 0,
> and the error handling in quota_write_inode() is incorrect,
> fix these. This also fix a tune2fs segfault that currently
> occurs when we add project and quota features to an inode
> exhaustion ext4 filesystem.
>
> Fixes: a701823a3150("libsupport: fix gcc -Wall nits")
>
> Signed-off-by: zhangyi (F) <yi.zhang@huawei.com>
Applied, thanks!
- Ted
prev parent reply other threads:[~2017-07-24 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 7:01 [e2fsprogs PATCH] libsupport: fix error handling in quota_write_inode zhangyi (F)
2017-07-24 19:17 ` Theodore Ts'o [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=20170724191722.lhlikwpuzt3te6mf@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=yi.zhang@huawei.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;
as well as URLs for NNTP newsgroup(s).