From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Kasper Sandberg <lkml@metanurb.dk>,
LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64
Date: Tue, 05 Dec 2006 14:17:38 +0000 [thread overview]
Message-ID: <4659.1165328258@redhat.com> (raw)
In-Reply-To: <20061204192018.2a61814f.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
> Possibly one could work out what's going on by reverse-engineering x86_64
> ioctl command 0x82187201, but unfortunately I don't have time to do that.
strace can do that.
David
next prev parent reply other threads:[~2006-12-05 14:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 14:29 BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64 Kasper Sandberg
2006-11-22 23:25 ` Andrew Morton
2006-11-26 13:47 ` Kasper Sandberg
2006-11-26 18:07 ` BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64| perhaps duplicate bug report? Kasper Sandberg
2006-11-26 19:52 ` Alistair John Strachan
2006-11-26 22:56 ` Kasper Sandberg
2006-12-05 2:36 ` BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64 Kasper Sandberg
2006-12-05 2:59 ` Kasper Sandberg
2006-12-05 3:20 ` Andrew Morton
2006-12-05 14:17 ` David Howells [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-05 9:33 Chuck Ebbert
2006-12-05 14:19 ` David Howells
2006-12-06 0:11 ` Kasper Sandberg
2006-12-05 20:32 Chuck Ebbert
2006-12-05 22:11 ` David Howells
2006-12-06 2:31 Chuck Ebbert
2006-12-06 12:58 ` Kasper Sandberg
2006-12-06 13:08 ` David Howells
2006-12-06 16:06 ` Kasper Sandberg
2006-12-06 16:48 ` David Howells
2006-12-06 20:05 ` Kasper Sandberg
2006-12-06 21:29 ` Andi Kleen
2006-12-06 22:19 ` Kasper Sandberg
2006-12-11 8:27 Chuck Ebbert
2006-12-13 4:39 ` Kasper Sandberg
2006-12-13 7:50 Chuck Ebbert
2006-12-13 8:05 ` Kasper Sandberg
2006-12-13 11:08 ` Alan
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=4659.1165328258@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
/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