Re: [PATCH] xfs: don't over-report free space or inodes in statvfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH] xfs: don't over-report free space or inodes in statvfs
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 17 Dec 2024 22:54:08 -0800
Cc: Carlos Maiolino <cem@xxxxxxxxxx>, Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>, xfs <linux-xfs@xxxxxxxxxxxxxxx>
In-reply-to: <20241217174446.GN6174@frogsfrogsfrogs>
References: <20241217174446.GN6174@frogsfrogsfrogs>

Looks good:

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

We should probably wire up the reproducer to xfstests as well.

References:
- [PATCH] xfs: don't over-report free space or inodes in statvfs
  - From: Darrick J. Wong

Prev by Date: Re: [PATCH 2/2] xfs: allow inode-based btrees to reserve space in the data device
Next by Date: Re: [PATCH 27/37] xfs: online repair of realtime file bmaps
Previous by thread: [PATCH] xfs: don't over-report free space or inodes in statvfs
Next by thread: [PATCH v1 2/3] xfs/libxfs: replace kmalloc() and memcpy() with kmemdup()
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux