public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 113041] mbcache NULL pointer dereference
Date: Wed, 27 Apr 2016 21:35:28 +0000	[thread overview]
Message-ID: <bug-113041-13602-nOQwBNKUR9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-113041-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=113041

Theodore Tso <tytso@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@mit.edu

--- Comment #7 from Theodore Tso <tytso@mit.edu> ---
The comm field doesn't really matter all that much.  The crash is in the
mbcache slab shrinker, which gets called from the VM when the system us under
memory pressure.

It looks like the crash is in the extended attribute cache which is in turn
triggered by SELinux.   (As far as I know Cassandra doesn't use extended
attributes.)

Note that the 4.3.x kernel is not a long-term supported kernel, and it's no
longer automatically getting bug fixes ported to it, at least not in the
upstream.  If CoreOS is providing their own security updates, then you should
really ask them for support because this would be a distro-kernel that has
changes not seen or supported by usptream developers.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2016-04-27 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 10:05 [Bug 113041] New: mbcache NULL pointer dereference bugzilla-daemon
2016-03-15  2:11 ` [Bug 113041] " bugzilla-daemon
2016-03-15 13:07 ` bugzilla-daemon
2016-03-15 15:47 ` bugzilla-daemon
2016-04-11 13:21 ` bugzilla-daemon
2016-04-27  7:26 ` bugzilla-daemon
2016-04-27  7:36 ` bugzilla-daemon
2016-04-27 21:35 ` bugzilla-daemon [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=bug-113041-13602-nOQwBNKUR9@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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