All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Pisarcik <boris@acheron.sk>
To: linux-kernel@vger.kernel.org
Subject: Re: Non keyboard trigger of Alt-SysRQ-S-U-B
Date: Wed, 4 Apr 2001 15:54:45 +0200	[thread overview]
Message-ID: <20010404155445.A1800@Boris> (raw)
In-Reply-To: <3ABE1C70.92CBBF01@umr.edu>
In-Reply-To: <3ABE1C70.92CBBF01@umr.edu>; from nneul@umr.edu on Sun, Mar 25, 2001 at 10:27:28AM -0600

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

    Hi Nathan,

I've just made an experimental module which offers syscall to privileged
process, which internally translates itself into real sysrq handler
(handle_sysrq) defined in drivers/char/sysrq.c. It occupates itself 
one of unussed linux system calls (concretely stty - no. 31). 
Makefile and patch for that sysrq.c are included in attached archive. 
(I stronly believe i didn't made it reversed :). 
The patch itself only exports 1 variable and 1 function from sysrq.c, 
that normally aren't.

You can make a daemon, which listens on socket and triggers commands
send by clients. Dont call sysrq+boot until a while needed to sync and
unmount. This check, if sync and/or umount were finished before boot,
should be really done, but it would require more changes in kernel
source. And of course, the security is to be taken in client/server
into account.

Bye                                                                   B.

[-- Attachment #2: srq.tar.gz --]
[-- Type: application/octet-stream, Size: 1925 bytes --]

      parent reply	other threads:[~2001-04-04 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-25 16:27 Non keyboard trigger of Alt-SysRQ-S-U-B Nathan Neulinger
2001-03-25 22:16 ` Keith Owens
2001-04-04 11:21   ` Boris Pisarcik
2001-04-04 13:54 ` Boris Pisarcik [this message]

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=20010404155445.A1800@Boris \
    --to=boris@acheron.sk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.