From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: loopback mount failing on 2.6.0-test7
Date: Fri, 17 Oct 2003 16:56:44 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106641048226864@msgid-missing> (raw)
Looks like some recent changes involving passing more errors up from
get_user_pages is making loopback mounting fail. I've traced this down
to mount trying to do an mlockall (it probably shouldn't be doing this
for what it's attempting to do). The test that's failing is:
!(flags & vma->vm_flags)
The values in question are:
flags: 0x1 VM_READ
vm_flags: 0x2070 VM_LOCKED, VM_MAY{READ,WRITE,EXEC}
I tested a 2.4 kernel, and the same test fails, but it's not propagated
out to the system call. It appears that the failing region is the
"---p" mapping of libc. x86 has no such mapping. Is this a broken use
of mlockall, or does the error propagation change make it so mlockall
cannot work on ia64? Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next reply other threads:[~2003-10-17 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 16:56 Alex Williamson [this message]
2003-10-17 17:21 ` loopback mount failing on 2.6.0-test7 David Mosberger
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-106641048226864@msgid-missing \
--to=alex.williamson@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