From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: loopback mount failing on 2.6.0-test7
Date: Fri, 17 Oct 2003 19:10:43 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106642262105622@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106641048226864@msgid-missing>
On Fri, 2003-10-17 at 11:21, David Mosberger wrote:
> 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?
>
Sure enough, seems to be fixed in Linus' bk. It was still broken in
linux-ia64-2.5 as of yesterday though. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2003-10-17 19:10 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
2003-10-17 19:10 ` Alex Williamson [this message]
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-106642262105622@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