From: David Gibson <david@gibson.dropbear.id.au>
To: akpm@linux-foundation.org, abarry@cray.com
Cc: hughd@google.com, mgorman@suse.de, minchan.kim@gmail.com,
paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Hugepage cleanup and bugfix
Date: Thu, 16 Feb 2012 15:23:58 +1100 [thread overview]
Message-ID: <1329366240-11663-1-git-send-email-david@gibson.dropbear.id.au> (raw)
Hi, this is a revised version of Andrew Barry's fix for the hugepage
race between unmount and quota update. In fact it's not just that
race which is a problem, it's a more general use-after-free problem on
fs inodes from the hugepage code.
Despite all the abstract talk in the patch comments about layering
violations, this fixes a real, exploitable, crash bug which has been
in the kernel for a very long time now.
Andrew, please apply.
next reply other threads:[~2012-02-16 4:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 4:23 David Gibson [this message]
2012-02-16 4:23 ` [PATCH 1/2] Cleanup to hugetlb.h David Gibson
2012-02-16 4:24 ` [PATCH 2/2] hugepages: Fix use after free bug in "quota" handling David Gibson
2012-02-16 12:33 ` Hillf Danton
2012-03-06 2:37 ` David Gibson
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=1329366240-11663-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=abarry@cray.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=paulus@samba.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).