* [PATCH v2] xfs: check the disk address for hardware atomic writes
@ 2026-11-12 0:41 Daejun Park via B4 Relay
2026-11-12 8:29 ` John Garry
` (3 more replies)
0 siblings, 4 replies; 9+ messages in thread
From: Daejun Park via B4 Relay @ 2026-11-12 0:41 UTC (permalink / raw)
To: Carlos Maiolino, linux-xfs
Cc: Pankaj Raghav, Pankaj Raghav, John Garry, Darrick J. Wong,
Christoph Hellwig, Dave Chinner, linux-kernel, Daejun Park
From: Daejun Park <daejun7.park@samsung.com>
xfs_bmap_hw_atomic_write_possible() checks the alignment of the encoded
br_startblock, not of the disk address. This was harmless while atomic
writes were capped at the greatest power-of-two factor of the group
size.
Commit ec8f62cc109a ("xfs: don't limit software atomic writes by the
group alignment") lifted that cap. The block layer can now fail a
misaligned write with -EINVAL, and XFS does not fall back to COW.
Unaligned AGs, such as those made by mkfs.xfs before 6.16, and rtgroups
made by any version can hit this.
Check the disk address instead.
Fixes: ec8f62cc109a ("xfs: don't limit software atomic writes by the group alignment")
Signed-off-by: Daejun Park <daejun7.park@samsung.com>
---
The bug needs a group size that is not a multiple of the device's
atomic write unit max. mkfs.xfs 6.16+ rounds agsize to a multiple
of it if the device reports one at mkfs time, but never rounds
rgsize. Before 6.16, a single device of 4 TB or more got an odd
agsize.
Tested on emulated NVMe with a 64 KiB atomic unit and boundary.
64 KiB atomic overwrites in AG 1-3 (mkfs.xfs 6.6.0 -d agsize=262142b)
and rtgroups 1-7 (xfsprogs 7ebfc20eb88e -r rgsize=65534b) failed with
EINVAL before and used COW after. fstests -g atomicwrites and xfs/838
(rt) give the same results before and after (generic/773 fails with
ENOSPC on both).
Changes in v2:
- Explain why the check was harmless before ec8f62cc109a and which
filesystems are affected (Pankaj).
- Reword the comment: an fsbno is not always a linear disk address
(Pankaj).
---
fs/xfs/xfs_iomap.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
index c3465204b8d..119ff8e4c95 100644
--- a/fs/xfs/xfs_iomap.c
+++ b/fs/xfs/xfs_iomap.c
@@ -848,8 +848,10 @@ xfs_bmap_hw_atomic_write_possible(
* atomic writes are required to be naturally aligned for disk blocks,
* which ensures that we adhere to block layer rules that we won't
* straddle any boundary or violate write alignment requirement.
+ * Check the disk address: an fsbno is not always a linear disk address.
*/
- if (!IS_ALIGNED(imap->br_startblock, imap->br_blockcount))
+ if (!IS_ALIGNED(xfs_fsb_to_db(ip, imap->br_startblock),
+ XFS_FSB_TO_BB(mp, imap->br_blockcount)))
return false;
/*
---
base-commit: 48326a2382d80715475d10ce98734ac65d2d2150
change-id: 20261110-xfs-hw-atomic-align-0eab6833447a
Best regards,
--
Daejun Park <daejun7.park@samsung.com>
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCH v2] xfs: check the disk address for hardware atomic writes
2026-11-12 0:41 [PATCH v2] xfs: check the disk address for hardware atomic writes Daejun Park via B4 Relay
@ 2026-11-12 8:29 ` John Garry
2026-11-12 13:49 ` Christoph Hellwig
` (2 subsequent siblings)
3 siblings, 0 replies; 9+ messages in thread
From: John Garry @ 2026-11-12 8:29 UTC (permalink / raw)
To: daejun7.park, Carlos Maiolino, linux-xfs
Cc: Pankaj Raghav, Pankaj Raghav, Darrick J. Wong, Christoph Hellwig,
Dave Chinner, linux-kernel
On 11/12/26 00:41, Daejun Park via B4 Relay wrote:
> From: Daejun Park <daejun7.park@samsung.com>
>
> xfs_bmap_hw_atomic_write_possible() checks the alignment of the encoded
> br_startblock, not of the disk address. This was harmless while atomic
> writes were capped at the greatest power-of-two factor of the group
> size.
>
> Commit ec8f62cc109a ("xfs: don't limit software atomic writes by the
> group alignment") lifted that cap. The block layer can now fail a
> misaligned write with -EINVAL,
It's a good thing that we have those block layer checks...
> and XFS does not fall back to COW.
> Unaligned AGs, such as those made by mkfs.xfs before 6.16, and rtgroups
> made by any version can hit this.
>
> Check the disk address instead.
>
> Fixes: ec8f62cc109a ("xfs: don't limit software atomic writes by the group alignment")
> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
> ---
> The bug needs a group size that is not a multiple of the device's
> atomic write unit max. mkfs.xfs 6.16+ rounds agsize to a multiple
> of it if the device reports one at mkfs time, but never rounds
> rgsize. Before 6.16, a single device of 4 TB or more got an odd
> agsize.
>
> Tested on emulated NVMe with a 64 KiB atomic unit and boundary.
> 64 KiB atomic overwrites in AG 1-3 (mkfs.xfs 6.6.0 -d agsize=262142b)
> and rtgroups 1-7 (xfsprogs 7ebfc20eb88e -r rgsize=65534b) failed with
> EINVAL before and used COW after. fstests -g atomicwrites and xfs/838
> (rt) give the same results before and after (generic/773 fails with
> ENOSPC on both).
>
> Changes in v2:
> - Explain why the check was harmless before ec8f62cc109a and which
> filesystems are affected (Pankaj).
> - Reword the comment: an fsbno is not always a linear disk address
> (Pankaj).
> ---
> fs/xfs/xfs_iomap.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
> index c3465204b8d..119ff8e4c95 100644
> --- a/fs/xfs/xfs_iomap.c
> +++ b/fs/xfs/xfs_iomap.c
> @@ -848,8 +848,10 @@ xfs_bmap_hw_atomic_write_possible(
> * atomic writes are required to be naturally aligned for disk blocks,
> * which ensures that we adhere to block layer rules that we won't
> * straddle any boundary or violate write alignment requirement.
> + * Check the disk address: an fsbno is not always a linear disk address.
> */
> - if (!IS_ALIGNED(imap->br_startblock, imap->br_blockcount))
Is there anywhere else in which we do an alignment check on
br_startblock that relies on the group size to be a multiple of the HW
awu max?
> + if (!IS_ALIGNED(xfs_fsb_to_db(ip, imap->br_startblock),
> + XFS_FSB_TO_BB(mp, imap->br_blockcount)))
> return false;
>
> /*
>
> ---
> base-commit: 48326a2382d80715475d10ce98734ac65d2d2150
> change-id: 20261110-xfs-hw-atomic-align-0eab6833447a
>
> Best regards,
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCH v2] xfs: check the disk address for hardware atomic writes
2026-11-12 0:41 [PATCH v2] xfs: check the disk address for hardware atomic writes Daejun Park via B4 Relay
2026-11-12 8:29 ` John Garry
@ 2026-11-12 13:49 ` Christoph Hellwig
2026-11-12 21:38 ` Pankaj Raghav (Samsung)
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p5>
3 siblings, 0 replies; 9+ messages in thread
From: Christoph Hellwig @ 2026-11-12 13:49 UTC (permalink / raw)
To: daejun7.park
Cc: Carlos Maiolino, linux-xfs, Pankaj Raghav, Pankaj Raghav,
John Garry, Darrick J. Wong, Christoph Hellwig, Dave Chinner,
linux-kernel
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCH v2] xfs: check the disk address for hardware atomic writes
2026-11-12 0:41 [PATCH v2] xfs: check the disk address for hardware atomic writes Daejun Park via B4 Relay
2026-11-12 8:29 ` John Garry
2026-11-12 13:49 ` Christoph Hellwig
@ 2026-11-12 21:38 ` Pankaj Raghav (Samsung)
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p5>
3 siblings, 0 replies; 9+ messages in thread
From: Pankaj Raghav (Samsung) @ 2026-11-12 21:38 UTC (permalink / raw)
To: Daejun Park
Cc: Carlos Maiolino, linux-xfs, Pankaj Raghav, John Garry,
Darrick J. Wong, Christoph Hellwig, Dave Chinner, linux-kernel
On Thu, Nov 12, 2026 at 09:41:56AM +0900, Daejun Park wrote:
> xfs_bmap_hw_atomic_write_possible() checks the alignment of the encoded
> br_startblock, not of the disk address. This was harmless while atomic
> writes were capped at the greatest power-of-two factor of the group
> size.
>
> Commit ec8f62cc109a ("xfs: don't limit software atomic writes by the
> group alignment") lifted that cap. The block layer can now fail a
> misaligned write with -EINVAL, and XFS does not fall back to COW.
> Unaligned AGs, such as those made by mkfs.xfs before 6.16, and rtgroups
> made by any version can hit this.
>
> Check the disk address instead.
>
> Fixes: ec8f62cc109a ("xfs: don't limit software atomic writes by the group alignment")
> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
Looks good,
Reviewed-by: Pankaj Raghav (Samsung) <pankaj.raghav@linux.dev>
--
Pankaj
^ permalink raw reply [flat|nested] 9+ messages in thread[parent not found: <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p5>]
* RE:(2) [PATCH v2] xfs: check the disk address for hardware atomic writes
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p5>
@ 2026-11-13 2:55 ` Daejun Park
2026-11-13 9:45 ` (2) " John Garry
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p1>
0 siblings, 2 replies; 9+ messages in thread
From: Daejun Park @ 2026-11-13 2:55 UTC (permalink / raw)
To: John Garry, Carlos Maiolino, linux-xfs
Cc: Pankaj Raghav Partha Sarathy, Pankaj Raghav, Darrick J. Wong,
Christoph Hellwig, Dave Chinner, linux-kernel, Daejun Park
On Thu, Nov 12, 2026 at 08:29:42AM +0000, John Garry wrote:
> On 11/12/26 00:41, Daejun Park via B4 Relay wrote:
[...]
> > - if (!IS_ALIGNED(imap->br_startblock, imap->br_blockcount))
>
> Is there anywhere else in which we do an alignment check on
> br_startblock that relies on the group size to be a multiple of the HW
> awu max?
No, I did not find another one. This is the only check of the start
block for the REQ_ATOMIC path. Two other places depend on the group
alignment, but neither checks br_startblock:
- xfs_get_atomic_write_max_opt() already caps max_opt at
xfs_calc_group_awu_align_max(), the largest power-of-two factor of
the group size (from ec8f62cc109a).
- The allocator aligns the AG block number, not the disk address,
for example for XFS_BMAPI_EXTSZALIGN in
xfs_atomic_write_cow_iomap_begin(). In an unaligned AG, that extent
can still be misaligned on disk. With this patch, the next atomic
write to it goes through COW instead of failing.
Best regards,
Daejun
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: (2) [PATCH v2] xfs: check the disk address for hardware atomic writes
2026-11-13 2:55 ` Daejun Park
@ 2026-11-13 9:45 ` John Garry
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p1>
1 sibling, 0 replies; 9+ messages in thread
From: John Garry @ 2026-11-13 9:45 UTC (permalink / raw)
To: daejun7.park, Carlos Maiolino, linux-xfs
Cc: Pankaj Raghav Partha Sarathy, Pankaj Raghav, Darrick J. Wong,
Christoph Hellwig, Dave Chinner, linux-kernel
On 11/13/26 02:55, Daejun Park wrote:
> On Thu, Nov 12, 2026 at 08:29:42AM +0000, John Garry wrote:
>> On 11/12/26 00:41, Daejun Park via B4 Relay wrote:
> [...]
>>> - if (!IS_ALIGNED(imap->br_startblock, imap->br_blockcount))
>> Is there anywhere else in which we do an alignment check on
>> br_startblock that relies on the group size to be a multiple of the HW
>> awu max?
> No, I did not find another one. This is the only check of the start
> block for the REQ_ATOMIC path. Two other places depend on the group
> alignment, but neither checks br_startblock:
>
> - xfs_get_atomic_write_max_opt() already caps max_opt at
> xfs_calc_group_awu_align_max(), the largest power-of-two factor of
> the group size (from ec8f62cc109a).
> - The allocator aligns the AG block number, not the disk address,
> for example for XFS_BMAPI_EXTSZALIGN in
> xfs_atomic_write_cow_iomap_begin(). In an unaligned AG, that extent
> can still be misaligned on disk. With this patch, the next atomic
> write to it goes through COW instead of failing.
hmm.. I am still not confident that this the best fix. And if it is,
then I think that we should still change the size pre-check in
xfs_file_dio_write_atomic(). Here's a combined change which I am
thinking of:
--- a/fs/xfs/xfs_file.c
+++ b/fs/xfs/xfs_file.c
@@ -776,7 +776,7 @@ xfs_file_dio_write_atomic(
* HW offload should be faster, so try that first if it is already
* known that the write length is not too large.
*/
- if (ocount > xfs_inode_buftarg(ip)->bt_awu_max)
+ if (ocount > xfs_get_atomic_write_max_opt())
dops = &xfs_atomic_write_cow_iomap_ops;
else
dops = &xfs_direct_write_iomap_ops;
diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
index c3465204b8d5..c54aaa4b8816 100644
--- a/fs/xfs/xfs_iomap.c
+++ b/fs/xfs/xfs_iomap.c
@@ -863,7 +863,7 @@ xfs_bmap_hw_atomic_write_possible(
/*
* The ->iomap_begin caller should ensure this, but check anyway.
*/
- return len <= xfs_inode_buftarg(ip)->bt_awu_max;
+ return len <= xfs_get_atomic_write_max_opt();
}
bt_awu_max is the HW max, and you are saying that it is not aligned with
the AG size (and so need a disk alignment check). However, opt max
should be (aligned to AG size), so we could check that vs size instead.
Note that I am just using xfs_get_atomic_write_max_opt() for
illustrative purposes and we could save this value in xfs_inode_buftarg().
BTW, with your proposed change, since HW size is not aligned to AG size
and we only check the size vs HW size for HW offload, it is in theory
possible to have an atomic write which straddles the AG and is rejected,
right?
Thanks,
John
^ permalink raw reply [flat|nested] 9+ messages in thread[parent not found: <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p1>]
* RE:(2) (2) [PATCH v2] xfs: check the disk address for hardware atomic writes
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p1>
@ 2026-11-16 7:39 ` Daejun Park
2026-11-16 8:11 ` (2) " John Garry
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p7>
0 siblings, 2 replies; 9+ messages in thread
From: Daejun Park @ 2026-11-16 7:39 UTC (permalink / raw)
To: John Garry, Carlos Maiolino, linux-xfs
Cc: Pankaj Raghav Partha Sarathy, Pankaj Raghav, Darrick J. Wong,
Christoph Hellwig, Dave Chinner, linux-kernel, Daejun Park
On Fri, Nov 13, 2026 at 09:45:22AM +0000, John Garry wrote:
> hmm.. I am still not confident that this the best fix. And if it is,
> then I think that we should still change the size pre-check in
> xfs_file_dio_write_atomic(). Here's a combined change which I am
> thinking of:
[...]
> bt_awu_max is the HW max, and you are saying that it is not aligned with
> the AG size (and so need a disk alignment check). However, opt max
> should be (aligned to AG size), so we could check that vs size instead.
Thanks, agreed. v3 will check the size instead of the disk address,
in both xfs_file_dio_write_atomic() and
xfs_bmap_hw_atomic_write_possible(). The limit is the one max_opt
applies: the smaller of bt_awu_max and the largest power-of-two factor
of the group size. Below that limit the existing br_startblock check is
enough, so v3 drops the disk address check.
v3 puts this limit in a helper that xfs_get_atomic_write_max_opt() also
uses, so max_opt and the checks use the same hardware limit. The checks
call the helper rather than max_opt, since max_opt is 0 on a filesystem
without reflink. When I tried max_opt there, the one-block atomic
writes went to COW and failed with -EINVAL. The helper returns
bt_awu_max when there are no groups, which is the rt device without
rtgroups.
> BTW, with your proposed change, since HW size is not aligned to AG size
> and we only check the size vs HW size for HW offload, it is in theory
> possible to have an atomic write which straddles the AG and is rejected,
> right?
Userspace does not see a rejection. Such a write maps to two extents,
so xfs_bmap_hw_atomic_write_possible() returns false and the write goes
through COW. This is the same in v2 and v3. In v3, a write sent to the
hardware is also aligned and no larger than the group alignment, so it
cannot cross a group boundary.
Best regards,
Daejun
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: (2) (2) [PATCH v2] xfs: check the disk address for hardware atomic writes
2026-11-16 7:39 ` Daejun Park
@ 2026-11-16 8:11 ` John Garry
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p7>
1 sibling, 0 replies; 9+ messages in thread
From: John Garry @ 2026-11-16 8:11 UTC (permalink / raw)
To: daejun7.park, Carlos Maiolino, linux-xfs
Cc: Pankaj Raghav Partha Sarathy, Pankaj Raghav, Darrick J. Wong,
Christoph Hellwig, Dave Chinner, linux-kernel
On 11/16/26 07:39, Daejun Park wrote:
> On Fri, Nov 13, 2026 at 09:45:22AM +0000, John Garry wrote:
>> hmm.. I am still not confident that this the best fix. And if it is,
>> then I think that we should still change the size pre-check in
>> xfs_file_dio_write_atomic(). Here's a combined change which I am
>> thinking of:
> [...]
>> bt_awu_max is the HW max, and you are saying that it is not aligned with
>> the AG size (and so need a disk alignment check). However, opt max
>> should be (aligned to AG size), so we could check that vs size instead.
>
uhhh... I thought about this a bit more, and I am really not sure on the
best solution. On one hand, atomic writes whose length is above opt max
should not use HW atomics. Or, more specifically, the user can't expect
HW atomics to be used. However, if HW atomic is possible, then it would
be silly not to use it.
> Thanks, agreed. v3 will check the size instead of the disk address,
> in both xfs_file_dio_write_atomic() and
> xfs_bmap_hw_atomic_write_possible(). The limit is the one max_opt
> applies: the smaller of bt_awu_max and the largest power-of-two factor
> of the group size. Below that limit the existing br_startblock check is
> enough, so v3 drops the disk address check.
>
> v3 puts this limit in a helper that xfs_get_atomic_write_max_opt() also
> uses, so max_opt and the checks use the same hardware limit. The checks
> call the helper rather than max_opt, since max_opt is 0 on a filesystem
> without reflink. When I tried max_opt there, the one-block atomic
> writes went to COW and failed with -EINVAL. The helper returns
> bt_awu_max when there are no groups, which is the rt device without
> rtgroups.
>
>> BTW, with your proposed change, since HW size is not aligned to AG size
>> and we only check the size vs HW size for HW offload, it is in theory
>> possible to have an atomic write which straddles the AG and is rejected,
>> right?
>
> Userspace does not see a rejection. Such a write maps to two extents,
> so xfs_bmap_hw_atomic_write_possible() returns false and the write goes
> through COW.
Yeah, I was really asking if HW atomic could span 2x extents before we
catch it.
> This is the same in v2 and v3. In v3, a write sent to the
> hardware is also aligned and no larger than the group alignment, so it
> cannot cross a group boundary.
>
Maybe what you have in this patch is ok. I'll wait for v3 and consider
it more. Sorry for the hesitancy.
Thanks,
John
^ permalink raw reply [flat|nested] 9+ messages in thread[parent not found: <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p7>]
* RE:(2) (2) (2) [PATCH v2] xfs: check the disk address for hardware atomic writes
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p7>
@ 2026-11-16 9:54 ` Daejun Park
0 siblings, 0 replies; 9+ messages in thread
From: Daejun Park @ 2026-11-16 9:54 UTC (permalink / raw)
To: John Garry, Carlos Maiolino, linux-xfs
Cc: Pankaj Raghav Partha Sarathy, Pankaj Raghav, Darrick J. Wong,
Christoph Hellwig, Dave Chinner, linux-kernel, Daejun Park
On Mon, Nov 16, 2026 at 08:11:51AM +0000, John Garry wrote:
> Yeah, I was really asking if HW atomic could span 2x extents before we
> catch it.
It is caught before any bio is built. xfs_direct_write_iomap_begin()
checks with xfs_bmap_hw_atomic_write_possible() that one mapping covers
the whole write. For a write over two extents it returns -ENOPROTOOPT,
and xfs_file_dio_write_atomic() redoes the write through COW, which is
still atomic. If a shorter mapping ever got past that check, iomap
fails the write with -EINVAL instead of issuing a partial REQ_ATOMIC
bio.
> Maybe what you have in this patch is ok. I'll wait for v3 and consider
> it more. Sorry for the hesitancy.
I wrote the v3 I described and tested it against v2 before posting it.
v3 sends every write above the group alignment to COW, also when the
extent is aligned on disk, as in AG 0. v2 sends those writes to the
hardware and falls back to COW when the hardware path is not possible,
for example when the extent is misaligned on disk. So I'll keep v2 as
posted and not send v3.
For reference only, on emulated NVMe (QEMU) with a 64 KiB atomic unit
and boundary, non-debug kernels, three runs of 10000 overwrites: a
64 KiB atomic overwrite in AG 0 took 35.2-38.6 us with v2 and
69.4-78.1 us with v3. In a misaligned AG 1 it took 70.5-88.8 us with
v2 and 68.8-88.7 us with v3.
Best regards,
Daejun
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2026-11-16 9:54 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-11-12 0:41 [PATCH v2] xfs: check the disk address for hardware atomic writes Daejun Park via B4 Relay
2026-11-12 8:29 ` John Garry
2026-11-12 13:49 ` Christoph Hellwig
2026-11-12 21:38 ` Pankaj Raghav (Samsung)
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p5>
2026-11-13 2:55 ` Daejun Park
2026-11-13 9:45 ` (2) " John Garry
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p1>
2026-11-16 7:39 ` Daejun Park
2026-11-16 8:11 ` (2) " John Garry
[not found] ` <CGME20261112082952epcas2p1f902c4243d451635ff27fe1a1c5035fe@epcms2p7>
2026-11-16 9:54 ` Daejun Park
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®