From: Michael Halcrow <uml@halcrow.us>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Michael Halcrow <uml@halcrow.us>,
Blaisorblade <blaisorblade_spam@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] keyring syscalls
Date: Tue, 25 Jan 2005 16:46:51 -0600 [thread overview]
Message-ID: <20050125224650.GA6136@halcrow.us> (raw)
In-Reply-To: <200501252337.58219.blaisorblade@yahoo.it>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Tue, Jan 25, 2005 at 11:37:57PM +0100, Blaisorblade wrote:
> On Tuesday 25 January 2005 22:54, Michael Halcrow wrote:
> > On Thu, Nov 18, 2004 at 06:39:26PM +0100, Blaisorblade wrote:
> Well, it should be fixed in the -mm tree (and probably in 2.6.11-rc2-bk2, I
> guess, though it's not tested)... browse the patches at
> http://user-mode-linux.sourceforge.net/patches.html.
I did notice that and tried to build it, but I had build errors.
Specifically, the compiler complains that the PTRACE_SETOPTIONS symbol
is undeclared in arch/um/kernel/process.c. If I include
linux/ptrace.h and try again, then the new syscalls (vperfctr_*) are
undeclared in arch/um/kernel/sys_call_table.c. I just gave up at that
point; I'll wait for the official 2.6.11 release. In the meantime,
I'll see if I can't backport the changes in the 2.6.11-rc2 patch to
2.6.10.
Thanks,
Mike
.___________________________________________________________________.
Michael A. Halcrow
Security Software Engineer, IBM Linux Technology Center
GnuPG Fingerprint: 05B5 08A8 713A 64C1 D35D 2371 2D3C FDDA 3EB6 601D
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-25 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041118160909.GA7630@halcrow.us>
2004-11-18 17:39 ` [uml-devel] Re: [uml-user] keyring syscalls Blaisorblade
2004-11-18 17:43 ` Michael Halcrow
2005-01-25 21:54 ` Michael Halcrow
2005-01-25 22:21 ` Henrik Nordstrom
2005-01-25 22:37 ` Blaisorblade
2005-01-25 22:46 ` Michael Halcrow [this message]
2005-01-25 23:02 ` Blaisorblade
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=20050125224650.GA6136@halcrow.us \
--to=uml@halcrow.us \
--cc=blaisorblade@yahoo.it \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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