From: Pim van den Berg <pim.vandenberg-IXGSG4U2CCrz+pZb47iToQ@public.gmane.org>
To: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mkfs crash
Date: Sat, 29 Dec 2012 21:28:47 +0100 [thread overview]
Message-ID: <50DF527F.9080003@nethuis.nl> (raw)
In-Reply-To: <50DED9A0.40002-IXGSG4U2CCrz+pZb47iToQ@public.gmane.org>
On 12/29/2012 12:53 PM, Pim van den Berg wrote:
> So it starts with PAX, detecting a refcount overflow, and makes
> mkfs.ext4 crash. The question now is, is it a grsecurity/pax bug, a
> bcache bug, or is it a combination of things?
I got an accidental reply from the PaX Team:
On 12/29/2012 07:33 PM, PaX Team wrote:
> hi,
>
> i just accidentally ran across your report on linux-bcache, and
> wanted to tell you that this is probably a false positive refcount
> overflow detection because the atomic variables in question seem to
> be only statistics that only ever get incremented so an eventual
> overflow is normal (or at least not a security problem, you may still
> want to let Kent know since an overflowing counter means 'false'
> stats for the end user). the 'fix' for this problem could be any of
> the following (with different benefits/drawbacks):
>
> 1. disable REFCOUNT in your .config
> 2. patch these bcache counters to be of the atomic_unchecked_t type
> and also their accessors to use the _unchecked variants
> 3. make these counters atomic64_t that will probably not overflow
> (but if they still can, there's atomic64_unchecked_t ;)
>
> cheers and happy new year,
> PaX Team
prev parent reply other threads:[~2012-12-29 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 12:05 mkfs crash Pim van den Berg
[not found] ` <50DC3977.2080209-IXGSG4U2CCrz+pZb47iToQ@public.gmane.org>
2012-12-28 4:31 ` Kent Overstreet
[not found] ` <20121228043144.GC10411-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2012-12-29 11:53 ` Pim van den Berg
[not found] ` <50DED9A0.40002-IXGSG4U2CCrz+pZb47iToQ@public.gmane.org>
2012-12-29 20:28 ` Pim van den Berg [this message]
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=50DF527F.9080003@nethuis.nl \
--to=pim.vandenberg-ixgsg4u2ccrz+pzb47itoq@public.gmane.org \
--cc=koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.