mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: linux-os@analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reserving a syscall number
Date: Wed, 27 Oct 2004 15:55:37 -0400	[thread overview]
Message-ID: <417FFD39.70601@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0410271505110.4669@chaos.analogic.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



linux-os wrote:
| On Wed, 27 Oct 2004, John Richard Moser wrote:
|
|> -----BEGIN PGP SIGNED MESSAGE-----
|> Hash: SHA1
|>
|> How would one go about having a specific syscall number reserved in
|> entry.S?  I'm exploring doing a kill inside the kernel from a detection
|> done in userspace, which would allow the executable header of the binary
|> to indicate whether the task should be killed or not; if it works, the
|> changes will likely not go into mainline, but will still require a
|> non-changing syscall index (assuming I understood the syscall manpage
|> properly).
|>
|> On a side note, if a syscall doesn't exist, how would that be detected
|> in userspace?
|> - --
|
|
| Look at ld.so.preload for potential capabilities to control any
| executable.
|
| Also what's the problem with sending the task a signal when
| the detection has been done?
|
| If the usual capabilites are not sufficient, then make
| a driver (module).
|

I'm attempting to figure a way to control the IBM stack smash protector
via a flag in the ELF header, without opening the executable image on
disk and checking manually.  If there is a way to do this from
userspace, that would be acceptable.

|
| Cheers,
| Dick Johnson
| Penguin : Linux version 2.6.9 on an i686 machine (5537.79 BogoMips).
|  Notice : All mail here is now cached and reviewed by John Ashcroft.
|                  98.36% of all statistics are fiction.
|

- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBf/04hDd4aOud5P8RAm0AAJ9FWZ2d0hJpS5qDhogRPM6mWZJDOwCfe5YC
BynHiZzH94hn5XnSLZlNqyc=
=jMqN
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-10-27 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 18:48 John Richard Moser
2004-10-27 19:09 ` linux-os
2004-10-27 19:55   ` John Richard Moser [this message]
2004-10-27 19:20 ` Chris Wright

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=417FFD39.70601@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /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

Powered by JetHome