Linux 9p file system development
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Breno Leitao <leitao@debian.org>
Cc: Eric Van Hensbergen <ericvh@kernel.org>,
	Latchesar Ionkov <lucho@ionkov.net>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Eryu Guan <eguan@linux.alibaba.com>,
	Yiwen Jiang <jiangyiwen@huawei.com>,
	v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] 9p: fix WARN_ON when dropping nlink on files with nlink=0
Date: Mon, 15 Jun 2026 22:19:40 +0900	[thread overview]
Message-ID: <ai_77Gr0h_n5SkET@codewreck.org> (raw)
In-Reply-To: <ai-842Shp-LJIOBD@gmail.com>

Breno Leitao wrote on Mon, Jun 15, 2026 at 01:51:09AM -0700:
> > Please send as a proper PATCH mail and I'll tentatively apply for 7.2
> > (a bit too late for 7.1)
> 
> Please, don't forget this one for 7.2. This is one is hurting me from
> time to time.

Thanks for the reminder, that did fall through the cracks, with the
dozen of LLM-generated patches that came in lately and my attention
being more than limited..

I've picked 20260421-9p-v2-1-48762d294fad@debian.org up, and will send
it to Linus at the end of the week unless something bad happens

-- 
Dominique

  reply	other threads:[~2026-06-15 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 10:23 [PATCH] 9p: fix WARN_ON when dropping nlink on files with nlink=0 Breno Leitao
2026-02-15  9:27 ` Dominique Martinet
2026-04-20 14:31   ` Breno Leitao
2026-04-20 15:59     ` Dominique Martinet
2026-04-20 16:26       ` Breno Leitao
2026-06-15  8:51       ` Breno Leitao
2026-06-15 13:19         ` Dominique Martinet [this message]
2026-06-15 13:58           ` Breno Leitao

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=ai_77Gr0h_n5SkET@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=akpm@linux-foundation.org \
    --cc=eguan@linux.alibaba.com \
    --cc=ericvh@kernel.org \
    --cc=jiangyiwen@huawei.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=stable@vger.kernel.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