From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Mike Marshall <hubcap@omnibond.com>,
Sasha Levin <sashal@kernel.org>,
devel@lists.orangefs.org
Subject: [PATCH AUTOSEL 4.9 09/16] orangefs: fix orangefs df output.
Date: Sat, 10 Jul 2021 19:52:33 -0400 [thread overview]
Message-ID: <20210710235240.3222618-9-sashal@kernel.org> (raw)
In-Reply-To: <20210710235240.3222618-1-sashal@kernel.org>
From: Mike Marshall <hubcap@omnibond.com>
[ Upstream commit 0fdec1b3c9fbb5e856a40db5993c9eaf91c74a83 ]
Orangefs df output is whacky. Walt Ligon suggested this might fix it.
It seems way more in line with reality now...
Signed-off-by: Mike Marshall <hubcap@omnibond.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
fs/orangefs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/orangefs/super.c b/fs/orangefs/super.c
index 6e35ef6521b4..8972ebc87016 100644
--- a/fs/orangefs/super.c
+++ b/fs/orangefs/super.c
@@ -185,7 +185,7 @@ static int orangefs_statfs(struct dentry *dentry, struct kstatfs *buf)
buf->f_bavail = (sector_t) new_op->downcall.resp.statfs.blocks_avail;
buf->f_files = (sector_t) new_op->downcall.resp.statfs.files_total;
buf->f_ffree = (sector_t) new_op->downcall.resp.statfs.files_avail;
- buf->f_frsize = sb->s_blocksize;
+ buf->f_frsize = 0;
out_op_release:
op_release(new_op);
--
2.30.2
next prev parent reply other threads:[~2021-07-10 23:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 23:52 [PATCH AUTOSEL 4.9 01/16] pwm: spear: Don't modify HW state in .remove callback Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 02/16] power: supply: ab8500: Avoid NULL pointers Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 03/16] power: reset: gpio-poweroff: add missing MODULE_DEVICE_TABLE Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 04/16] ARM: 9087/1: kprobes: test-thumb: fix for LLVM_IAS=1 Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 05/16] watchdog: Fix possible use-after-free in wdt_startup() Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 06/16] watchdog: sc520_wdt: Fix possible use-after-free in wdt_turnoff() Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 07/16] watchdog: Fix possible use-after-free by calling del_timer_sync() Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 08/16] x86/fpu: Return proper error codes from user access functions Sasha Levin
2021-07-10 23:52 ` Sasha Levin [this message]
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 10/16] ceph: remove bogus checks and WARN_ONs from ceph_set_page_dirty Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 11/16] power: supply: charger-manager: add missing MODULE_DEVICE_TABLE Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 12/16] power: supply: ab8500: " Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 13/16] pwm: tegra: Don't modify HW state in .remove callback Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 14/16] ACPI: AMBA: Fix resource name in /proc/iomem Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 15/16] virtio-blk: Fix memory leak among suspend/resume procedure Sasha Levin
2021-07-10 23:52 ` [PATCH AUTOSEL 4.9 16/16] virtio_console: Assure used length from device is limited Sasha Levin
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=20210710235240.3222618-9-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=devel@lists.orangefs.org \
--cc=hubcap@omnibond.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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