From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/2] xfs stats fixes
Date: Wed, 3 Oct 2018 14:35:35 +0200 [thread overview]
Message-ID: <20181003123537.30965-1-cmaiolino@redhat.com> (raw)
Hi,
this week I found a bug in the code for xqmstat file in procfs, caused by wrong
offsets while reading the __xfsstats structure fields in xqmstat_proc_show.
This patchset aims to fix the bug (patch 1) and add a way to reduce the
likelyhood of creating the same error again.
xqmstat_proc_show() uses a loop to walk through the quota-specific fields in
__xfsstats when printing the information. The problem is, since the start/end
offsets are hardcoded, any update to __xfsstats may also require an update on
the start offset in xqmstat_proc_show().
I decided to split it into two patches, because I think it is easier to let the
bugfix itself in a separated patch, and the approach on how to avoid it in the
future can be discussed in a separated patch.
My first idea was to try to add a method to check it at compile time, and I spent
some time discussing with Eric what would be the best way to avoid this problem
in the future.
We end up with an possible solution using offsetof() and a new constant in
xfs_stats.h to properly check the offsets at compile time.
Although, after giving it some extra thought, I found it better to only use a
new constant to mark the start of xqmstat in xfs_stats.h and not add any fancy
calculation in xqmstat_proc_show itself.
History told me that all updates to __xfsstats and its respective content/uses,
were properly done when needed, only the xqmstat was left behind because it's
unusual direct usage of the offset markers. So, I believe that the addition of a
new marker to specify the start offset of the quota stat fields is enough to
avoid future problems here, once no more changes will be needed in xqmstat code
whenever __xfsstats requires to be updated.
My idea though is still to move this file to sysfs together with the rest of
statistic code, but by now, I believe we should fix this bug.
Comments?
Cheers.
Carlos Maiolino (2):
xfs: Fix xqmstats offsets in /proc/fs/xfs/xqmstat
xfs: Add new constant to mark start of xqmstat
fs/xfs/xfs_stats.c | 2 +-
fs/xfs/xfs_stats.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2018-10-03 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 12:35 Carlos Maiolino [this message]
2018-10-03 12:35 ` [PATCH 1/2] xfs: Fix xqmstats offsets in /proc/fs/xfs/xqmstat Carlos Maiolino
2018-10-03 12:47 ` Eric Sandeen
2018-10-03 13:39 ` Carlos Maiolino
2018-10-03 13:59 ` Eric Sandeen
2018-10-04 8:01 ` Carlos Maiolino
2018-10-03 15:18 ` Darrick J. Wong
2018-10-03 15:20 ` Darrick J. Wong
2018-10-03 12:35 ` [PATCH 2/2] xfs: Add new constant to mark start of xqmstat Carlos Maiolino
2018-10-03 12:51 ` Eric Sandeen
2018-10-03 14:00 ` Carlos Maiolino
2018-10-03 14:04 ` Eric Sandeen
2018-10-03 23:09 ` Dave Chinner
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=20181003123537.30965-1-cmaiolino@redhat.com \
--to=cmaiolino@redhat.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).