From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Paolo Giarrusso <blaisorblade_personal@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Security patches 1- 3
Date: Tue, 19 Oct 2004 18:10:48 +0200 [thread overview]
Message-ID: <41753C88.1080808@fujitsu-siemens.com> (raw)
In-Reply-To: <200410182347.17797.blaisorblade_personal@yahoo.it>
Paolo Giarrusso wrote:
>
> Ok, I guess I have understood you. I could insert it, but first I would like
> to have it tested. However, for now -v6 is released with the other change you
> posted.
>
Today I installed a 2.6.7-skas3.v6 host. And I adapted and applied also the patch
from bitkeeper. For me, this combination works fine. So here is the slightly
modified patch.
Bodo
----
# Modified to apply to Linux-2.6.7 + host-skas3-2.6.7-v6.patch
#
#
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/09/08 07:49:36-07:00 roland@redhat.com
# [PATCH] i386 syscall tracing of bogus system calls
#
# In 2.4, strace will show you all bogus system calls a process tries. In
# 2.6, it only shows you stubs < __NR_syscalls, and there is no tracing stop
# for large bogus system call numbers. I can't see why this was changed, so
# I am assuming it was accidental.
#
# This patch restores the expected behavior that syscall tracing shows every
# bogus syscall attempt.
#
# Signed-off-by: Roland McGrath <roland@redhat.com>
# Signed-off-by: Andrew Morton <akpm@osdl.org>
# Signed-off-by: Linus Torvalds <torvalds@osdl.org>
#
# arch/i386/kernel/entry.S
# 2004/09/08 07:49:29-07:00 roland@redhat.com +4 -4
# i386 syscall tracing of bogus system calls
#
diff -Nru a/arch/i386/kernel/entry.S b/arch/i386/kernel/entry.S
--- a/arch/i386/kernel/entry.S 2004-10-19 02:40:35 -07:00
+++ b/arch/i386/kernel/entry.S 2004-10-19 02:40:35 -07:00
@@ -255,11 +255,11 @@
pushl %eax
SAVE_ALL
GET_THREAD_INFO(%ebp)
- cmpl $(nr_syscalls), %eax
- jae syscall_badsys
testb $(_TIF_SYSCALL_EMU|_TIF_SYSCALL_TRACE|_TIF_SYSCALL_AUDIT),TI_flags(%ebp)
jnz syscall_trace_entry
+ cmpl $(nr_syscalls), %eax
+ jae syscall_badsys
call *sys_call_table(,%eax,4)
movl %eax,EAX(%esp)
cli
@@ -278,11 +278,11 @@
pushl %eax # save orig_eax
SAVE_ALL
GET_THREAD_INFO(%ebp)
- cmpl $(nr_syscalls), %eax
- jae syscall_badsys
# system call tracing in operation / emulation
testb $(_TIF_SYSCALL_EMU|_TIF_SYSCALL_TRACE|_TIF_SYSCALL_AUDIT),TI_flags(%ebp)
jnz syscall_trace_entry
+ cmpl $(nr_syscalls), %eax
+ jae syscall_badsys
syscall_call:
call *sys_call_table(,%eax,4)
movl %eax,EAX(%esp) # store the return value
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
parent reply other threads:[~2004-10-19 16:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200410182347.17797.blaisorblade_personal@yahoo.it>]
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=41753C88.1080808@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade_personal@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@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;
as well as URLs for NNTP newsgroup(s).