From: Richard Weinberger <richard@nod.at>
To: linux-um@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, johannes.berg@intel.com,
anton.ivanov@cambridgegreys.com,
Richard Weinberger <richard@nod.at>
Subject: [PATCH 0/4] um: Assorted console related fixes
Date: Sat, 1 Jan 2022 22:58:06 +0100 [thread overview]
Message-ID: <20220101215810.13260-1-richard@nod.at> (raw)
When UML terminates (gracefully or panic) it does not always
cleanup on the host side.
Especially when fd:0,fd:1 is used as console it can leave a misconfigured
stdin/out on the host side.
Also stale processes such as port-helper can left behind.
This series fixes the console exit code to make sure UML
undoes everything it changed on the host side.
Richard Weinberger (4):
um: Run console exit code also upon kernel panic
um: os_set_fd_block: Return old blocking mode
um: chan: Restore blocking mode upon exit
um: irq: Restore O_ASYNC upon exit
arch/um/drivers/chan.h | 1 +
arch/um/drivers/chan_kern.c | 11 +++++++----
arch/um/drivers/chan_user.c | 2 +-
arch/um/drivers/mconsole_kern.c | 2 +-
arch/um/drivers/stdio_console.c | 4 ++--
arch/um/drivers/ubd_user.c | 2 +-
arch/um/drivers/xterm.c | 2 +-
arch/um/include/shared/uml_console.h | 11 +++++++++++
arch/um/kernel/irq.c | 5 ++++-
arch/um/kernel/um_arch.c | 8 +++++---
arch/um/os-Linux/file.c | 5 ++++-
11 files changed, 38 insertions(+), 15 deletions(-)
create mode 100644 arch/um/include/shared/uml_console.h
--
2.26.2
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next reply other threads:[~2022-01-01 21:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 21:58 Richard Weinberger [this message]
2022-01-01 21:58 ` [PATCH 1/4] um: Run console exit code also upon kernel panic Richard Weinberger
2022-01-04 8:56 ` Johannes Berg
2022-01-01 21:58 ` [PATCH 2/4] um: os_set_fd_block: Return old blocking mode Richard Weinberger
2022-01-04 9:00 ` Johannes Berg
2022-01-01 21:58 ` [PATCH 3/4] um: chan: Restore blocking mode upon exit Richard Weinberger
2022-01-01 21:58 ` [PATCH 4/4] um: irq: Restore O_ASYNC " Richard Weinberger
2022-01-04 9:02 ` Johannes Berg
2022-03-09 5:29 ` [PATCH 0/4] um: Assorted console related fixes Glenn Washburn
2022-03-09 8:35 ` Richard Weinberger
2022-03-09 16:13 ` Randy Dunlap
2022-03-09 16:21 ` Richard Weinberger
2022-03-09 16:48 ` Randy Dunlap
2022-03-10 18:21 ` Glenn Washburn
2022-04-04 21:41 ` Richard Weinberger
2022-06-06 23:16 ` Glenn Washburn
2022-06-07 8:22 ` Johannes Berg
2022-06-07 15:10 ` Glenn Washburn
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=20220101215810.13260-1-richard@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.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