All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glenn Washburn <development@efficientek.com>
To: Richard Weinberger <richard@nod.at>,
	linux-um <linux-um@lists.infradead.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Glenn Washburn <development@efficientek.com>
Subject: [PATCH 0/4] um: Assorted console related fixes
Date: Tue,  8 Mar 2022 23:29:21 -0600	[thread overview]
Message-ID: <1f5276f9b2950d34eec89004d2a2322a06145d2b.1646802841.development@efficientek.com> (raw)
In-Reply-To: <20220101215810.13260-1-richard@nod.at>

On Sat, 2022-01-01 at 22:58 +0100, Richard Weinberger wrote:
> 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.

I gave this a run hoping it would fix the issues I'm seeing with the console
getting messed up when UML exits via halt in the guest. Echo is turned off
and looks like carriage return doesn't work either. I'm using "reset" to get
the terminal back to its previous state. Unfortunately this patch series did
not fix this issue.

I'm not saying that these aren't valid fixes. But it does appear that these
changes don't make sure that "everything" changed on the host side is undone.

Glenn


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  parent reply	other threads:[~2022-03-09  5:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 21:58 [PATCH 0/4] um: Assorted console related fixes Richard Weinberger
2022-01-01 21:58 ` Richard Weinberger
2022-01-01 21:58 ` [PATCH 1/4] um: Run console exit code also upon kernel panic Richard Weinberger
2022-01-01 21:58   ` Richard Weinberger
2022-01-04  5:58   ` kernel test robot
2022-01-04  8:56   ` Johannes Berg
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-01 21:58   ` Richard Weinberger
2022-01-04  9:00   ` Johannes Berg
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   ` Richard Weinberger
2022-01-01 21:58 ` [PATCH 4/4] um: irq: Restore O_ASYNC " Richard Weinberger
2022-01-01 21:58   ` Richard Weinberger
2022-01-04  9:02   ` Johannes Berg
2022-01-04  9:02     ` Johannes Berg
2022-03-09  5:29 ` Glenn Washburn [this message]
2022-03-09  8:35   ` [PATCH 0/4] um: Assorted console related fixes 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=1f5276f9b2950d34eec89004d2a2322a06145d2b.1646802841.development@efficientek.com \
    --to=development@efficientek.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    /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.