From: Rich Johnston <rjohnston@sgi.com>
To: Eryu Guan <eguan@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v3] xfstests generic 312: test fallocate(2) ENOSPC when file size is greater than 4G
Date: Wed, 15 May 2013 08:14:27 -0500 [thread overview]
Message-ID: <51938A33.50202@sgi.com> (raw)
In-Reply-To: <1367833355-14473-1-git-send-email-eguan@redhat.com>
On 05/06/2013 04:42 AM, Eryu Guan wrote:
> ENOSPC in fallocate(2) could corrupt ext4 when file size > 4G
>
> Regression test for commit
> 29ae07b ext4: Fix overflow caused by missing cast in ext4_fallocate()
>
> Signed-off-by: Eryu Guan <eguan@redhat.com>
Tested fine for xfs and ext4, Looks good.
Reviewed-by: Rich Johnston <rjohnston@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-15 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 9:42 [PATCH v3] xfstests generic 312: test fallocate(2) ENOSPC when file size is greater than 4G Eryu Guan
2013-05-10 7:07 ` Eryu Guan
2013-05-15 13:14 ` Rich Johnston [this message]
2013-05-15 13:16 ` Rich Johnston
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=51938A33.50202@sgi.com \
--to=rjohnston@sgi.com \
--cc=eguan@redhat.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