[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgQAgHh_rjiFaAO+Y_mRQvp4SJ7SQ7niVKj89hDmh8Q_A@mail.gmail.com>
Date: Thu, 1 Jun 2023 08:26:29 -0400
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Christian Brauner <brauner@...nel.org>
Cc: Thorsten Leemhuis <linux@...mhuis.info>,
Mike Christie <michael.christie@...cle.com>, oleg@...hat.com,
nicolas.dichtel@...nd.com, axboe@...nel.dk, ebiederm@...ssion.com,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, mst@...hat.com,
sgarzare@...hat.com, jasowang@...hat.com, stefanha@...hat.com,
Linux kernel regressions list <regressions@...ts.linux.dev>,
hch@...radead.org, konrad.wilk@...cle.com
Subject: Re: [RFC PATCH 0/8] vhost_tasks: Use CLONE_THREAD/SIGHAND
On Thu, Jun 1, 2023 at 6:47 AM Christian Brauner <brauner@...nel.org> wrote:
>
> @Mike, do you want to prepare an updated version of the temporary fix.
> If @Linus prefers to just apply it directly he can just grab it from the
> list rather than delaying it. Make sure to grab a Co-developed-by line
> on this, @Mike.
Yeah, let's apply the known "fix the immediate regression" patch wrt
vhost ps output and the freezer. That gets rid of the regression.
I think that we can - and should - then treat the questions about core
dumping and execve as separate issues.
vhost wouldn't have done execve since it's nonsensical and has never
worked anyway since it always left the old mm ref behind, and
similarly core dumping has never been an issue.
So on those things we don't have any "semantic" issues, we just need
to make sure we don't do crazy things like hang uninterruptibly.
Linus
Powered by blists - more mailing lists