mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Dave Jones <davej@redhat.com>, Andi Kleen <ak@suse.de>,
	Ulrich Drepper <drepper@gmail.com>,
	dragoran <dragoran@feuerpokemon.de>,
	linux-kernel@vger.kernel.org
Subject: Re: IA32 syscall 311 not implemented on x86_64
Date: Sun, 21 May 2006 16:51:50 -0700	[thread overview]
Message-ID: <20060521235150.GA7581@taniwha.stupidest.org> (raw)
In-Reply-To: <20060521234821.GQ8250@redhat.com>

On Sun, May 21, 2006 at 07:48:21PM -0400, Dave Jones wrote:

> If a regular user can trip up debugging printks, yes, lets remove it.
> Examples ?

segfaults are printk reported on iamd64 machines, you can fork a lot
of those if you wanted


  reply	other threads:[~2006-05-21 23:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-21  8:35 dragoran
2006-05-21  8:50 ` Chris Wedgwood
2006-05-21  9:06   ` dragoran
2006-05-21  9:11     ` Chris Wedgwood
2006-05-21  9:26       ` dragoran
2006-05-21  9:54       ` dragoran
2006-05-21 16:03   ` Dave Jones
2006-05-21 18:35     ` Ulrich Drepper
2006-05-21 18:50       ` Dave Jones
2006-05-21 18:56         ` Dave Jones
2006-05-21 19:38           ` Adrian Bunk
2006-05-21 19:47             ` Dave Jones
2006-05-22  0:17               ` [2.6 patch] x86_64: don't printk for unimplemented 32bit syscalls Adrian Bunk
2006-05-21 22:19           ` IA32 syscall 311 not implemented on x86_64 Andi Kleen
2006-05-21 22:28             ` Dave Jones
2006-05-21 22:37               ` Andi Kleen
2006-05-21 23:48                 ` Dave Jones
2006-05-21 23:51                   ` Chris Wedgwood [this message]
2006-05-22  5:59                   ` dragoran
2006-05-22 12:41                     ` Dave Jones
2006-05-23 14:30                 ` Denis Vlasenko
2006-05-21 23:09             ` Andrew Morton
2006-05-21 19:35       ` Chris Wedgwood
2006-05-21 19:38         ` Dave Jones

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=20060521235150.GA7581@taniwha.stupidest.org \
    --to=cw@f00f.org \
    --cc=ak@suse.de \
    --cc=davej@redhat.com \
    --cc=dragoran@feuerpokemon.de \
    --cc=drepper@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®