요약·해설과 원문, 전문 번역을 서로 분리했습니다. API 이름, symbol, source path는 원문 표기를 사용합니다.
1. 요약·해설
원문의 핵심 논리와 kernel programming 관점의 보충 설명입니다. 아래의 전문 번역과는 별도로 작성했습니다.
2. 영어 원문 전체
번역 기준이 된 Linux v6.18.37 원문입니다. 줄 번호는 이 버전의 파일 좌표입니다.
원문 전체 펼치기
1
Linux Magic System Request Key Hacks
2
====================================
4
Documentation for sysrq.c
6
What is the magic SysRq key?
7
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9
It is a 'magical' key combo you can hit which the kernel will respond to
10
regardless of whatever else it is doing, unless it is completely locked up.
12
How do I enable the magic SysRq key?
13
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15
You need to say "yes" to 'Magic SysRq key (CONFIG_MAGIC_SYSRQ)' when
16
configuring the kernel. When running a kernel with SysRq compiled in,
17
/proc/sys/kernel/sysrq controls the functions allowed to be invoked via
18
the SysRq key. The default value in this file is set by the
19
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE config symbol, which itself defaults
20
to 1. Here is the list of possible values in /proc/sys/kernel/sysrq:
22
- 0 - disable sysrq completely
23
- 1 - enable all functions of sysrq
24
- >1 - bitmask of allowed sysrq functions (see below for detailed function
25
description)::
27
2 = 0x2 - enable control of console logging level
28
4 = 0x4 - enable control of keyboard (SAK, unraw)
29
8 = 0x8 - enable debugging dumps of processes etc.
30
16 = 0x10 - enable sync command
31
32 = 0x20 - enable remount read-only
32
64 = 0x40 - enable signalling of processes (term, kill, oom-kill)
33
128 = 0x80 - allow reboot/poweroff
34
256 = 0x100 - allow nicing of all RT tasks
36
You can set the value in the file by the following command::
38
echo "number" >/proc/sys/kernel/sysrq
40
The number may be written here either as decimal or as hexadecimal
41
with the 0x prefix. CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE must always be
42
written in hexadecimal.
44
Note that the value of ``/proc/sys/kernel/sysrq`` influences only the invocation
45
via a keyboard. Invocation of any operation via ``/proc/sysrq-trigger`` is
46
always allowed (by a user with admin privileges).
48
How do I use the magic SysRq key?
49
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
51
On x86
52
You press the key combo `ALT-SysRq-<command key>`.
54
.. note::
55
Some
56
keyboards may not have a key labeled 'SysRq'. The 'SysRq' key is
57
also known as the 'Print Screen' key. Also some keyboards cannot
58
handle so many keys being pressed at the same time, so you might
59
have better luck with press `Alt`, press `SysRq`,
60
release `SysRq`, press `<command key>`, release everything.
62
On SPARC
63
You press `ALT-STOP-<command key>`, I believe.
65
On the serial console (PC style standard serial ports only)
66
You send a ``BREAK``, then within 5 seconds a command key. Sending
67
``BREAK`` twice is interpreted as a normal BREAK.
69
On PowerPC
70
Press `ALT - Print Screen` (or `F13`) - `<command key>`.
71
`Print Screen` (or `F13`) - `<command key>` may suffice.
73
On other
74
If you know of the key combos for other architectures, please
75
submit a patch to be included in this section.
77
On all
78
Write a single character to /proc/sysrq-trigger.
79
Only the first character is processed, the rest of the string is
80
ignored. However, it is not recommended to write any extra characters
81
as the behavior is undefined and might change in the future versions.
82
E.g.::
84
echo t > /proc/sysrq-trigger
86
Alternatively, write multiple characters prepended by underscore.
87
This way, all characters will be processed. E.g.::
89
echo _reisub > /proc/sysrq-trigger
91
The `<command key>` is case sensitive.
93
What are the 'command' keys?
94
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
96
=========== ===================================================================
97
Command Function
98
=========== ===================================================================
99
``b`` Will immediately reboot the system without syncing or unmounting
100
your disks.
102
``c`` Will perform a system crash and a crashdump will be taken
103
if configured.
105
``d`` Shows all locks that are held.
107
``e`` Send a SIGTERM to all processes, except for init.
109
``f`` Will call the oom killer to kill a memory hog process, but do not
110
panic if nothing can be killed.
112
``g`` Used by kgdb (kernel debugger)
114
``h`` Will display help (actually any other key than those listed
115
here will display help. but ``h`` is easy to remember :-)
117
``i`` Send a SIGKILL to all processes, except for init.
119
``j`` Forcibly "Just thaw it" - filesystems frozen by the FIFREEZE ioctl.
121
``k`` Secure Access Key (SAK) Kills all programs on the current virtual
122
console. NOTE: See important comments below in SAK section.
124
``l`` Shows a stack backtrace for all active CPUs.
126
``m`` Will dump current memory info to your console.
128
``n`` Used to make RT tasks nice-able
130
``o`` Will shut your system off (if configured and supported).
132
``p`` Will dump the current registers and flags to your console.
134
``q`` Will dump per CPU lists of all armed hrtimers (but NOT regular
135
timer_list timers) and detailed information about all
136
clockevent devices.
138
``r`` Turns off keyboard raw mode and sets it to XLATE.
140
``s`` Will attempt to sync all mounted filesystems.
142
``t`` Will dump a list of current tasks and their information to your
143
console.
145
``u`` Will attempt to remount all mounted filesystems read-only.
147
``v`` Forcefully restores framebuffer console
148
``v`` Causes ETM buffer dump [ARM-specific]
150
``w`` Dumps tasks that are in uninterruptible (blocked) state.
152
``x`` Used by xmon interface on ppc/powerpc platforms.
153
Show global PMU Registers on sparc64.
154
Dump all TLB entries on MIPS.
156
``y`` Show global CPU Registers [SPARC-64 specific]
158
``z`` Dump the ftrace buffer
160
``0``-``9`` Sets the console log level, controlling which kernel messages
161
will be printed to your console. (``0``, for example would make
162
it so that only emergency messages like PANICs or OOPSes would
163
make it to your console.)
165
``R`` Replay the kernel log messages on consoles.
166
=========== ===================================================================
168
Okay, so what can I use them for?
169
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
171
Well, unraw(r) is very handy when your X server or a svgalib program crashes.
173
sak(k) (Secure Access Key) is useful when you want to be sure there is no
174
trojan program running at console which could grab your password
175
when you would try to login. It will kill all programs on given console,
176
thus letting you make sure that the login prompt you see is actually
177
the one from init, not some trojan program.
179
.. important::
181
In its true form it is not a true SAK like the one in a
182
c2 compliant system, and it should not be mistaken as
183
such.
185
It seems others find it useful as (System Attention Key) which is
186
useful when you want to exit a program that will not let you switch consoles.
187
(For example, X or a svgalib program.)
189
``reboot(b)`` is good when you're unable to shut down, it is an equivalent
190
of pressing the "reset" button.
192
``crash(c)`` can be used to manually trigger a crashdump when the system is hung.
193
Note that this just triggers a crash if there is no dump mechanism available.
195
``sync(s)`` is handy before yanking removable medium or after using a rescue
196
shell that provides no graceful shutdown -- it will ensure your data is
197
safely written to the disk. Note that the sync hasn't taken place until you see
198
the "OK" and "Done" appear on the screen.
200
``umount(u)`` can be used to mark filesystems as properly unmounted. From the
201
running system's point of view, they will be remounted read-only. The remount
202
isn't complete until you see the "OK" and "Done" message appear on the screen.
204
The loglevels ``0``-``9`` are useful when your console is being flooded with
205
kernel messages you do not want to see. Selecting ``0`` will prevent all but
206
the most urgent kernel messages from reaching your console. (They will
207
still be logged if syslogd/klogd are alive, though.)
209
``term(e)`` and ``kill(i)`` are useful if you have some sort of runaway process
210
you are unable to kill any other way, especially if it's spawning other
211
processes.
213
"just thaw ``it(j)``" is useful if your system becomes unresponsive due to a
214
frozen (probably root) filesystem via the FIFREEZE ioctl.
216
``Replay logs(R)`` is useful to view the kernel log messages when system is hung
217
or you are not able to use dmesg command to view the messages in printk buffer.
218
User may have to press the key combination multiple times if console system is
219
busy. If it is completely locked up, then messages won't be printed. Output
220
messages depend on current console loglevel, which can be modified using
221
sysrq[0-9] (see above).
223
Sometimes SysRq seems to get 'stuck' after using it, what can I do?
224
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
226
When this happens, try tapping shift, alt and control on both sides of the
227
keyboard, and hitting an invalid sysrq sequence again. (i.e., something like
228
`alt-sysrq-z`).
230
Switching to another virtual console (`ALT+Fn`) and then back again
231
should also help.
233
I hit SysRq, but nothing seems to happen, what's wrong?
234
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
236
There are some keyboards that produce a different keycode for SysRq than the
237
pre-defined value of 99
238
(see ``KEY_SYSRQ`` in ``include/uapi/linux/input-event-codes.h``), or
239
which don't have a SysRq key at all. In these cases, run ``showkey -s`` to find
240
an appropriate scancode sequence, and use ``setkeycodes <sequence> 99`` to map
241
this sequence to the usual SysRq code (e.g., ``setkeycodes e05b 99``). It's
242
probably best to put this command in a boot script. Oh, and by the way, you
243
exit ``showkey`` by not typing anything for ten seconds.
245
I want to add SysRQ key events to a module, how does it work?
246
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
248
In order to register a basic function with the table, you must first include
249
the header ``include/linux/sysrq.h``, this will define everything else you need.
250
Next, you must create a ``sysrq_key_op`` struct, and populate it with A) the key
251
handler function you will use, B) a help_msg string, that will print when SysRQ
252
prints help, and C) an action_msg string, that will print right before your
253
handler is called. Your handler must conform to the prototype in 'sysrq.h'.
255
After the ``sysrq_key_op`` is created, you can call the kernel function
256
``register_sysrq_key(int key, const struct sysrq_key_op *op_p);`` this will
257
register the operation pointed to by ``op_p`` at table key 'key',
258
if that slot in the table is blank. At module unload time, you must call
259
the function ``unregister_sysrq_key(int key, const struct sysrq_key_op *op_p)``,
260
which will remove the key op pointed to by 'op_p' from the key 'key', if and
261
only if it is currently registered in that slot. This is in case the slot has
262
been overwritten since you registered it.
264
The Magic SysRQ system works by registering key operations against a key op
265
lookup table, which is defined in 'drivers/tty/sysrq.c'. This key table has
266
a number of operations registered into it at compile time, but is mutable,
267
and 2 functions are exported for interface to it::
269
register_sysrq_key and unregister_sysrq_key.
271
Of course, never ever leave an invalid pointer in the table. I.e., when
272
your module that called register_sysrq_key() exits, it must call
273
unregister_sysrq_key() to clean up the sysrq key table entry that it used.
274
Null pointers in the table are always safe. :)
276
If for some reason you feel the need to call the handle_sysrq function from
277
within a function called by handle_sysrq, you must be aware that you are in
278
a lock (you are also in an interrupt handler, which means don't sleep!), so
279
you must call ``__handle_sysrq_nolock`` instead.
281
When I hit a SysRq key combination only the header appears on the console?
282
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
284
Sysrq output is subject to the same console loglevel control as all
285
other console output. This means that if the kernel was booted 'quiet'
286
as is common on distro kernels the output may not appear on the actual
287
console, even though it will appear in the dmesg buffer, and be accessible
288
via the dmesg command and to the consumers of ``/proc/kmsg``. As a specific
289
exception the header line from the sysrq command is passed to all console
290
consumers as if the current loglevel was maximum. If only the header
291
is emitted it is almost certain that the kernel loglevel is too low.
292
Should you require the output on the console channel then you will need
293
to temporarily up the console loglevel using `alt-sysrq-8` or::
295
echo 8 > /proc/sysrq-trigger
297
Remember to return the loglevel to normal after triggering the sysrq
298
command you are interested in.
300
I have more questions, who can I ask?
301
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
303
Just ask them on the linux-kernel mailing list:
306
Credits
307
~~~~~~~
309
- Written by Mydraal <[email protected]>
310
- Updated by Adam Sulmicki <[email protected]>
311
- Updated by Jeremy M. Dolan <[email protected]> 2001/01/28 10:15:59
312
- Added to by Crutcher Dunnavant <[email protected]>
3. 한국어 전문 번역
영어 원문의 문단 순서와 의미를 유지한 전체 번역입니다. 코드, 함수명, symbol과 URL은 원문 표기를 유지합니다.
Linux Magic System Request Key Hacks
1-5`sysrq.c`에 대한 Magic SysRq 사용 설명서입니다.
What is the magic SysRq key?
6-11system이 완전히 lock up된 경우를 제외하면 kernel이 다른 어떤 작업 중이더라도 응답하는 특별한 key combination입니다.
How do I enable the magic SysRq key?
12-47kernel 구성에서 `Magic SysRq key (CONFIG_MAGIC_SYSRQ)`를 활성화해야 합니다. SysRq가 compile된 kernel에서는 `/proc/sys/kernel/sysrq`가 keyboard로 호출할 수 있는 기능을 제어합니다. 기본값은 기본적으로 `1`인 `CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE` symbol이 정합니다.
| 값 | 허용 기능 |
|---|---|
| `0` | SysRq 완전 비활성화 |
| `1` | 모든 SysRq 기능 활성화 |
| `>1` | 아래 bitmask로 기능을 선택 |
2 = 0x2 - enable control of console logging level
4 = 0x4 - enable control of keyboard (SAK, unraw)
8 = 0x8 - enable debugging dumps of processes etc.
16 = 0x10 - enable sync command
32 = 0x20 - enable remount read-only
64 = 0x40 - enable signalling of processes (term, kill, oom-kill)
128 = 0x80 - allow reboot/poweroff
256 = 0x100 - allow nicing of all RT tasks다음 명령으로 값을 설정합니다.
echo "number" >/proc/sys/kernel/sysrq값은 decimal 또는 `0x` prefix가 붙은 hexadecimal로 쓸 수 있습니다. `CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE`은 항상 hexadecimal로 작성해야 합니다.
`/proc/sys/kernel/sysrq` 값은 keyboard 호출에만 영향을 줍니다. admin privilege가 있는 사용자가 `/proc/sysrq-trigger`로 호출하는 operation은 항상 허용됩니다.
How do I use the magic SysRq key?
48-92| 환경 | 호출 방법 |
|---|---|
| x86 | `ALT-SysRq-<command key>`. SysRq는 Print Screen으로도 표시되며, 동시 key 입력이 안 되면 Alt 누름, SysRq 누름·놓음, command key 누름 순서 사용 |
| SPARC | `ALT-STOP-<command key>` |
| PC 표준 serial console | `BREAK`를 보낸 뒤 5초 안에 command key. `BREAK` 두 번은 normal BREAK |
| PowerPC | `ALT - Print Screen` 또는 `F13` 뒤 `<command key>`. 경우에 따라 Alt 없이도 가능 |
| 기타 architecture | 알려진 key combination을 이 절에 추가하는 patch 제출 |
모든 환경에서 `/proc/sysrq-trigger`에 문자 하나를 쓸 수 있습니다. 첫 문자만 처리되고 나머지는 무시되지만 추가 문자의 동작은 undefined이며 미래에 바뀔 수 있으므로 권장하지 않습니다.
echo t > /proc/sysrq-triggerunderscore를 앞에 붙이면 여러 문자를 모두 처리합니다.
echo _reisub > /proc/sysrq-trigger`<command key>`는 대소문자를 구분합니다.
What are the 'command' keys?
93-167| command | 기능 |
|---|---|
| `b` | disk sync나 unmount 없이 즉시 reboot |
| `c` | system crash 수행. 구성되어 있으면 crashdump 생성 |
| `d` | 현재 held lock 모두 표시 |
| `e` | init을 제외한 모든 process에 SIGTERM |
| `f` | OOM killer로 memory hog process 종료. 종료할 대상이 없어도 panic하지 않음 |
| `g` | kgdb(kernel debugger) |
| `h` | help 표시. 목록에 없는 다른 key도 help 표시 |
| `i` | init을 제외한 모든 process에 SIGKILL |
| `j` | FIFREEZE ioctl로 freeze된 filesystem을 강제로 thaw |
| `k` | Secure Access Key(SAK). 현재 virtual console의 모든 program 종료 |
| `l` | 모든 active CPU의 stack backtrace |
| `m` | 현재 memory 정보 dump |
| `n` | RT task를 nice 가능하게 변경 |
| `o` | 구성과 지원 여부에 따라 system power off |
| `p` | 현재 register와 flag dump |
| `q` | CPU별 armed hrtimer 목록과 clockevent device 상세 정보 dump. 일반 `timer_list` timer 제외 |
| `r` | keyboard raw mode를 끄고 XLATE로 설정 |
| `s` | mount된 모든 filesystem sync 시도 |
| `t` | 현재 task 목록과 정보 dump |
| `u` | mount된 모든 filesystem을 read-only로 remount 시도 |
| `v` | framebuffer console 강제 복원. ARM에서는 ETM buffer dump |
| `w` | uninterruptible(blocked) 상태 task dump |
| `x` | ppc/powerpc의 xmon, sparc64의 global PMU register, MIPS의 모든 TLB entry dump |
| `y` | SPARC-64 global CPU register 표시 |
| `z` | ftrace buffer dump |
| `0`-`9` | console log level 설정. `0`은 PANIC·OOPS 같은 emergency message만 console에 출력 |
| `R` | kernel log message를 console에 replay |
Okay, so what can I use them for?
168-222`unraw(r)`는 X server나 svgalib program crash 뒤 keyboard를 복구하는 데 유용합니다. `sak(k)`는 password를 가로챌 console trojan이 없는지 확인하려고 해당 console의 모든 program을 종료하지만, C2 compliant system의 진정한 SAK는 아닙니다. console 전환을 막는 X나 svgalib program에서 빠져나오는 System Attention Key로도 쓰입니다.
`reboot(b)`는 reset button과 같고 정상 shutdown이 불가능할 때 사용합니다. `crash(c)`는 hung system에서 crashdump를 수동 trigger하며 dump mechanism이 없으면 crash만 일으킵니다.
`sync(s)`는 removable medium 제거 전이나 graceful shutdown이 없는 rescue shell 사용 뒤 data를 disk에 기록합니다. 화면에 `OK`와 `Done`이 나타나기 전에는 완료된 것이 아닙니다. `umount(u)`는 filesystem을 read-only로 remount하며 역시 해당 message를 기다려야 합니다.
loglevel `0`-`9`는 console이 원치 않는 kernel message로 넘칠 때 사용합니다. `0`은 가장 긴급한 message 외에는 console 출력을 막지만 syslogd/klogd가 살아 있으면 log에는 남습니다.
`term(e)`과 `kill(i)`은 다른 방법으로 종료할 수 없고 child를 계속 만드는 runaway process에 유용합니다. `it(j)`는 FIFREEZE ioctl로 freeze된 root filesystem 때문에 system이 응답하지 않을 때 thaw합니다.
`Replay logs(R)`는 hung system이거나 dmesg로 printk buffer를 볼 수 없을 때 kernel log를 확인합니다. console이 바쁘면 여러 번 눌러야 할 수 있고 완전히 lock up되면 출력되지 않습니다. 출력은 `sysrq[0-9]`로 바꿀 수 있는 현재 console loglevel에 의존합니다.
Sometimes SysRq seems to get 'stuck' after using it, what can I do?
223-232keyboard 양쪽의 Shift, Alt, Control을 눌러 보고 `alt-sysrq-z` 같은 invalid SysRq sequence를 다시 입력합니다. 다른 virtual console로 `ALT+Fn` 전환했다가 돌아오는 방법도 도움이 됩니다.
I hit SysRq, but nothing seems to happen, what's wrong?
233-244일부 keyboard는 미리 정한 SysRq keycode `99`와 다른 값을 내거나 SysRq key가 없습니다. `include/uapi/linux/input-event-codes.h`의 `KEY_SYSRQ`를 참조하십시오.
`showkey -s`로 적절한 scancode sequence를 찾고 `setkeycodes <sequence> 99`, 예를 들어 `setkeycodes e05b 99`로 usual SysRq code에 map합니다. boot script에 넣는 것이 좋습니다. `showkey`는 10초 동안 아무것도 입력하지 않으면 종료됩니다.
I want to add SysRQ key events to a module, how does it work?
245-280key table에 기본 function을 등록하려면 `include/linux/sysrq.h`를 include합니다. `sysrq_key_op` struct를 만들고 key handler function, help 출력용 `help_msg`, handler 호출 직전 출력할 `action_msg`를 채웁니다. handler는 `sysrq.h`의 prototype을 따라야 합니다.
`register_sysrq_key(int key, const struct sysrq_key_op *op_p);`는 table slot이 비어 있을 때 `op_p` operation을 key에 등록합니다. module unload 시 `unregister_sysrq_key(int key, const struct sysrq_key_op *op_p)`를 호출하면 해당 slot에 여전히 같은 operation이 있을 때만 제거합니다.
Magic SysRq는 `drivers/tty/sysrq.c`의 mutable key operation lookup table을 사용합니다. compile time에 여러 operation이 등록되고 다음 두 function이 interface로 export됩니다.
register_sysrq_key and unregister_sysrq_key.`register_sysrq_key()`를 호출한 module은 종료할 때 반드시 `unregister_sysrq_key()`로 entry를 정리해야 하며 invalid pointer를 남기면 안 됩니다. null pointer는 안전합니다.
`handle_sysrq`가 호출한 function 안에서 다시 handle function이 필요하면 lock과 interrupt handler context에 있어 sleep할 수 없으므로 `__handle_sysrq_nolock`을 호출해야 합니다.
When I hit a SysRq key combination only the header appears on the console?
281-299SysRq output도 다른 console output과 같은 loglevel 제어를 받습니다. distro kernel처럼 `quiet`로 boot하면 실제 console에 보이지 않아도 dmesg buffer, dmesg command, `/proc/kmsg` consumer에는 나타납니다.
예외적으로 SysRq command header는 현재 loglevel이 최대인 것처럼 모든 console consumer에 전달됩니다. header만 나오면 kernel loglevel이 너무 낮을 가능성이 큽니다. console 출력이 필요하면 `alt-sysrq-8` 또는 다음 명령으로 임시로 높입니다.
echo 8 > /proc/sysrq-trigger원하는 SysRq command를 실행한 뒤 loglevel을 정상값으로 되돌리십시오.
I have more questions, who can I ask?
300-305질문은 `[email protected]` mailing list에 보냅니다.
Credits
306-312Mydraal이 작성했고 Adam Sulmicki, Jeremy M. Dolan, Crutcher Dunnavant가 갱신·추가했습니다.
요약과 해설
sysrq.rst:1-312Magic SysRq는 userspace가 응답하지 않아도 kernel이 살아 있으면 진단·sync·read-only remount·process 종료·reboot 같은 긴급 동작을 수행하는 경로입니다. `b`처럼 sync 없이 즉시 reboot하는 command도 있으므로 복구 순서와 data 손실 위험을 이해한 뒤 사용해야 합니다.