From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>,
Michel Lespinasse <walken@google.com>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
linux-mm@kvack.org
Subject: mmotm 2010-12-16 - breaks mlockall() call
Date: Sat, 18 Dec 2010 05:10:59 -0500 [thread overview]
Message-ID: <131961.1292667059@localhost> (raw)
In-Reply-To: Your message of "Thu, 16 Dec 2010 14:56:39 PST." <201012162329.oBGNTdPY006808@imap1.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
On Thu, 16 Dec 2010 14:56:39 PST, akpm@linux-foundation.org said:
> The mm-of-the-moment snapshot 2010-12-16-14-56 has been uploaded to
>
> http://userweb.kernel.org/~akpm/mmotm/
The patch mlock-only-hold-mmap_sem-in-shared-mode-when-faulting-in-pages.patch
causes this chunk of code from cryptsetup-luks to fail during the initramfs:
if (mlockall(MCL_CURRENT | MCL_FUTURE)) {
log_err(ctx, _("WARNING!!! Possibly insecure memory. Are you root?\n"));
_memlock_count--;
return 0;
}
Bisection fingered this patch, which was added after -rc4-mmotm1202, which
boots without tripping this log_err() call. I haven't tried building a
-rc6-mmotm1216 with this patch reverted, because reverting it causes apply
errors for subsequent patches.
Ideas?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-12-18 10:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 22:56 mmotm 2010-12-16-14-56 uploaded akpm
2010-12-17 22:33 ` mmotm 2010-12-16-14-56 uploaded (hugetlb) Randy Dunlap
2010-12-17 22:53 ` Andrew Morton
2010-12-17 23:37 ` Andrea Arcangeli
2010-12-18 0:28 ` Randy Dunlap
2010-12-18 0:58 ` Andrew Morton
2010-12-18 8:17 ` Andrea Arcangeli
2010-12-18 7:44 ` Andrea Arcangeli
2010-12-18 10:10 ` Valdis.Kletnieks [this message]
2010-12-20 1:48 ` mmotm 2010-12-16 - breaks mlockall() call Michel Lespinasse
2010-12-21 6:26 ` Michel Lespinasse
2010-12-22 1:07 ` Valdis.Kletnieks
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=131961.1292667059@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=walken@google.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;
as well as URLs for NNTP newsgroup(s).