From: Roland Schwarz <roland.schwarz@blackspace.at>
To: linux-hams@vger.kernel.org
Subject: Kernel freeze on killall kissattach
Date: Sun, 6 Mar 2022 15:18:14 +0100 [thread overview]
Message-ID: <e037cff4-87fa-ce95-438d-66be0754c6b2@blackspace.at> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1414 bytes --]
Dear All,
please correct me if I am wrong, but as I understand it should not be
possible to trigger a kernel freeze by just killing user space processes.
While trying to understand a certain behavior of the ax25 driver I came
up with a small test case which I ran in a virtual machine (KVM):
First I tried with a kernel from Linus tree:
uname -r
5.17.0-rc6+
cat /etc/ax25/axports
ax0 OE1RSA-0 115200 255 7 Test A
ax1 OE1RSA-1 115200 255 7 Test B
sudo kissattach /dev/ptmx ax0
AX.25 port ax0 bound to device ax0
Awaiting client connects on
/dev/pts/1
sudo kissattach /dev/pts/1 ax1
AX.25 port ax1 bound to device ax1
axcall ax1 OE1RSA-0
Now in a second terminal:
sudo killall kissattach
First terminal:
GW4PTS AX.25 Connect v1.11
Trying...
*** Connected to OE1RSA-0
*** Cleared
==> But: Kernel freezes
I can see this behaviour also in the debian kernel:
uname -r
5.10.0-11-amd64
This kernel also freezes. I suspect this to be a bug because if I try to
reboot the machine instead of the killall command the machine does not
shut off and reboot which is a problem with a remotely installed system.
Any ideas?
73 de Roland oe1rsa
--
__________________________________________
_ _ | Roland Schwarz
|_)(_ |
| \__) | mailto:roland.schwarz@blackspace.at
________| http://www.blackspace.at
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2022-03-06 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 14:18 Roland Schwarz [this message]
2022-03-06 17:14 ` Kernel freeze on killall kissattach David Ranch
2022-03-06 18:01 ` Roland Schwarz
2022-03-06 18:05 ` David Ranch
2022-03-06 18:21 ` Roland Schwarz
2022-03-06 19:01 ` Thomas Osterried
2022-03-06 19:20 ` David Ranch
2022-03-07 10:52 ` Dan Carpenter
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=e037cff4-87fa-ce95-438d-66be0754c6b2@blackspace.at \
--to=roland.schwarz@blackspace.at \
--cc=linux-hams@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