From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, tj@kernel.org
Subject: [PATCH 0/2 v2] percpu_counter: xfs requires custom compare batch size
Date: Wed, 13 May 2015 09:52:32 +1000 [thread overview]
Message-ID: <1431474754-15764-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
This is v2 of the regression fix for the new generic per-cpu
superblock counter code in XFS. The problems fixed arise from using
custom batch sizes for addition and decrement exceeding the
"accurate compare" bounds in percpu_counter_compare() and hence
resulting in incorrect comparisons being made.
This regression was introduced in 4.1-rc1 and it requires a small
tweak to the percpu counter infrastructure to fix, hence the two
patches.
Comments welcome!
-Dave.
next reply other threads:[~2015-05-12 23:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 23:52 Dave Chinner [this message]
2015-05-12 23:52 ` [PATCH 1/2] percpu_counter: batch size aware __percpu_counter_compare() Dave Chinner
2015-05-13 13:59 ` Tejun Heo
2015-05-14 0:55 ` Dave Chinner
2015-05-14 15:02 ` Tejun Heo
2015-05-12 23:52 ` [PATCH 2/2] xfs: inode and free block counters need to use __percpu_counter_compare Dave Chinner
2015-05-14 14:21 ` Brian Foster
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=1431474754-15764-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=xfs@oss.sgi.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