From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: loopback mount failing on 2.6.0-test7
Date: Fri, 17 Oct 2003 17:21:06 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106641129027803@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106641048226864@msgid-missing>
>>>>> On Fri, 17 Oct 2003 10:56:44 -0600, Alex Williamson <alex.williamson@hp.com> said:
Alex> Looks like some recent changes involving passing more errors up from
Alex> get_user_pages is making loopback mounting fail. I've traced this down
Alex> to mount trying to do an mlockall (it probably shouldn't be doing this
Alex> for what it's attempting to do). The test that's failing is:
Alex> !(flags & vma->vm_flags)
Alex> The values in question are:
Alex> flags: 0x1 VM_READ
Alex> vm_flags: 0x2070 VM_LOCKED, VM_MAY{READ,WRITE,EXEC}
Alex> I tested a 2.4 kernel, and the same test fails, but it's not propagated
Alex> out to the system call. It appears that the failing region is the
Alex> "---p" mapping of libc. x86 has no such mapping. Is this a broken use
Alex> of mlockall, or does the error propagation change make it so mlockall
Alex> cannot work on ia64? Thanks,
Andi Kleen hacked some stuff in this area recently. I didn't follow
the discussion too closely, but he complained that mlockall() failed
for "no-access" mappings. I thought the fix went into test7 already,
but I may be misremembering and perhaps it's only in the current bk
tree. Could you check Linus' bk tree and see if it fixes the problem?
--david
next prev parent reply other threads:[~2003-10-17 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 16:56 loopback mount failing on 2.6.0-test7 Alex Williamson
2003-10-17 17:21 ` David Mosberger [this message]
2003-10-17 19:10 ` Alex Williamson
2003-10-17 20:15 ` David Mosberger
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=marc-linux-ia64-106641129027803@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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