From: Glenn Washburn <development@efficientek.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Richard Weinberger <richard@nod.at>,
linux-um <linux-um@lists.infradead.org>
Subject: Re: [PATCH 0/4] um: Assorted console related fixes
Date: Tue, 7 Jun 2022 10:10:18 -0500 [thread overview]
Message-ID: <20220607101018.7ebe76d4@crass-HP-ZBook-15-G2> (raw)
In-Reply-To: <6bfd0b100c71413d893c13440c8ea627078147e1.camel@sipsolutions.net>
On Tue, 07 Jun 2022 10:22:43 +0200
Johannes Berg <johannes@sipsolutions.net> wrote:
> On Mon, 2022-06-06 at 18:16 -0500, Glenn Washburn wrote:
> > GDB says that the process was terminated with
> > SIGKILL, which I'm guessing is why uml_console_exit() is not run.
> >
>
> https://patchwork.ozlabs.org/project/linux-um/patch/20220520194536.1acbb414a2d1.I1d71bab01d45f7f8e446df6e98547a7989338208@changeid/
Great! I've tested that this solves the SIGKILL issue and that stty
reports the same values before and after running a UML instance.
However, the flags re not the same (before 32770 and after 34818, in
decimal). It seems that the O_NONBLOCK flag is not being restored to
its original value (off).
So now the terminal is not messed up, but the flags are still an issue
for me because having stdin/stdout in non-blocking mode breaks some of
my scripts using uml.
Glenn
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
prev parent reply other threads:[~2022-06-07 15:10 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 ` [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 [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=20220607101018.7ebe76d4@crass-HP-ZBook-15-G2 \
--to=development@efficientek.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--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.