From: Michel Lespinasse <walken@google.com>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: mmotm 2010-12-16 - breaks mlockall() call
Date: Sun, 19 Dec 2010 17:48:05 -0800 [thread overview]
Message-ID: <AANLkTik4ffEzb_zzEN7Y+fksSkr+6HZs5Szd4VupH4+-@mail.gmail.com> (raw)
In-Reply-To: <131961.1292667059@localhost>
On Sat, Dec 18, 2010 at 2:10 AM, <Valdis.Kletnieks@vt.edu> wrote:
> 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?
I had a quick look, but didn't figure out much so far.
Could you send me your initramfs image and .config file so I can
reproduce the issue locally ?
Thanks,
--
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-12-20 1:48 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 ` mmotm 2010-12-16 - breaks mlockall() call Valdis.Kletnieks
2010-12-20 1:48 ` Michel Lespinasse [this message]
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=AANLkTik4ffEzb_zzEN7Y+fksSkr+6HZs5Szd4VupH4+-@mail.gmail.com \
--to=walken@google.com \
--cc=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 \
/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