public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Pankaj <pankaj.raghav@linux.dev>
To: Lukas Herbolt <lukas@herbolt.com>, Pankaj Raghav <p.raghav@samsung.com>
Cc: linux-xfs@vger.kernel.org, bfoster@redhat.com,
	"Darrick J . Wong" <djwong@kernel.org>,
	dgc@kernel.org, gost.dev@samsung.com, kundan.kumar@samsung.com,
	cem@kernel.org, hch@infradead.org
Subject: Re: [PATCH v2 0/2] add FALLOC_FL_WRITE_ZEROES support to xfs
Date: Tue, 14 Apr 2026 14:11:10 +0800	[thread overview]
Message-ID: <FC11AE42-0705-44FD-8F1C-C1A83BD41C37@linux.dev> (raw)
In-Reply-To: <3c2e979b144ecc02a5c6ea5eaa004bfd@herbolt.com>




>> base-commit: e0dc9e0f8da83cb70e2a7e9a
>> @Lukas: I didn't notice any activity from you regarding this series
>> since last month, so I decided to send it after spending some time on
>> Dave's feedback. I hope it is ok with you.
>
>No worries. I have actually very similar patch ready but run into some issue
>with fsx that i wanted to check first.

Maybe it is the same issue I ran into as well. generic/363 ( fsx that enables option to do mmap writes on EOF page) helped me debug the issue as it fails instead of crashing the system. For example, generic/127 and xfs/131 just crashed. 

--
Pankaj Raghav

      reply	other threads:[~2026-04-14  6:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 13:32 [PATCH v2 0/2] add FALLOC_FL_WRITE_ZEROES support to xfs Pankaj Raghav
2026-04-13 13:32 ` [PATCH v2 1/2] xfs: add xfs_bmap_alloc_or_convert_range function Pankaj Raghav
2026-04-13 13:32 ` [PATCH v2 2/2] xfs: add support for FALLOC_FL_WRITE_ZEROES Pankaj Raghav
2026-04-13 15:05   ` Lukas Herbolt
2026-04-14  6:08     ` Pankaj
2026-04-13 15:07 ` [PATCH v2 0/2] add FALLOC_FL_WRITE_ZEROES support to xfs Lukas Herbolt
2026-04-14  6:11   ` Pankaj [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=FC11AE42-0705-44FD-8F1C-C1A83BD41C37@linux.dev \
    --to=pankaj.raghav@linux.dev \
    --cc=bfoster@redhat.com \
    --cc=cem@kernel.org \
    --cc=dgc@kernel.org \
    --cc=djwong@kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=hch@infradead.org \
    --cc=kundan.kumar@samsung.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lukas@herbolt.com \
    --cc=p.raghav@samsung.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