From: Chandan Babu R <chandan.babu@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Creating written extents beyond EOF
Date: Tue, 06 Sep 2022 12:25:00 +0530 [thread overview]
Message-ID: <87a67dxa7u.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20220902215516.GX3600936@dread.disaster.area>
On Sat, Sep 03, 2022 at 07:55:16 AM +1000, Dave Chinner wrote:
> On Thu, Sep 01, 2022 at 06:55:31PM +0530, Chandan Babu R wrote:
>> Hi Dave,
>>
>> 7684e2c4384d5d1f884b01ab8bff2369e4db0bff
>> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7684e2c4384d5d1f884b01ab8bff2369e4db0bff)
>> is one of the commits that needs to be backported to 5.4.y stable kernel.
>>
>> The commit message mentions that we could have written extents beyond EOF. I
>> am unable to come up with a sequence of commands that could create such
>> extents.
>>
>> Can you please explain how a user could create a file having written extents
>> beyond EOF?
>
> That bug fix was committed in v5.5. We didn't convert delalloc to
> use unwritten extents until v5.8 via commit a5949d3faedf.
>
Ok. Thanks for clarifying my doubt. I can now recreate the bug on my test
machine when running v5.4 LTS kernel.
--
chandan
prev parent reply other threads:[~2022-09-06 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 13:25 Creating written extents beyond EOF Chandan Babu R
2022-09-02 21:55 ` Dave Chinner
2022-09-06 6:55 ` Chandan Babu R [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=87a67dxa7u.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@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).