Linux 9p file system development
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Vasiliy Kovalev <kovalev@altlinux.org>
Cc: Eric Van Hensbergen <ericvh@kernel.org>,
	Latchesar Ionkov <lucho@ionkov.net>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
	lvc-project@linuxtesting.org
Subject: Re: [PATCH] net/9p: fix infinite loop in p9_client_rpc on fatal signal
Date: Tue, 19 May 2026 21:35:36 +0900	[thread overview]
Message-ID: <agxZGDFdOHnODKqO@codewreck.org> (raw)
In-Reply-To: <bd83eb25-3142-3d91-f605-4d6f01182d03@basealt.ru>

Vasiliy Kovalev wrote on Sun, Apr 19, 2026 at 11:22:11AM +0300:
> On 4/17/26 01:52, Dominique Martinet wrote>
> > So if I understand this right, with a sane server, the tag will be used
> > until umount or a reply (to either the flush or the original request)?
> 
> From what I tested — until a reply. Tested on latest master.

Thanks for all the tests and following up

I'm still a little scared of this but I can't fault what you've found,
I've picked this up for testing When I Find Time™ and will submit to
Linus hopefully for next cycle if you don't hear back from me

-- 
Dominique

      reply	other threads:[~2026-05-19 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 15:52 [PATCH] net/9p: fix infinite loop in p9_client_rpc on fatal signal Vasiliy Kovalev
2026-04-16  1:41 ` Dominique Martinet
2026-04-16 12:49   ` Vasiliy Kovalev
2026-04-16 22:52     ` Dominique Martinet
2026-04-19  8:22       ` Vasiliy Kovalev
2026-05-19 12:35         ` Dominique Martinet [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=agxZGDFdOHnODKqO@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=ericvh@kernel.org \
    --cc=kovalev@altlinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=lvc-project@linuxtesting.org \
    --cc=v9fs@lists.linux.dev \
    /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