All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Mulqueen <mike@method-b.uk>,
	ericvh@kernel.org, lucho@ionkov.net, dhowells@redhat.com,
	pc@manguebit.org, linux_oss@crudebyte.com, v9fs@lists.linux.dev,
	linux-fsdevel@vger.kernel.org, regressions@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] 9p regression fix for 7.3-rc4
Date: Mon, 14 Sep 2026 18:34:40 +0900	[thread overview]
Message-ID: <aqe_sF0kM6mGn_KY@codewreck.org> (raw)

The following changes since commit df2908090cda368b01ff43709f51890076c56157:

  Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)

are available in the Git repository at:

  https://github.com/martinetd/linux tags/9p-for-7.3-rc4

for you to fetch changes up to c60ae98c5aa64021751b38ab1313b19d620bf640:

  9p: Fix v9fs_issue_write() to update i_size and remote_i_size (2026-09-12 07:49:22 +0000)

----------------------------------------------------------------
This is a single fix for a 9p/netfs regression that got in 7.1
(and was backported to 7.0)

We need to rework how cached attributes, and in particular i_size, are
handled in 9p more thoroughly but that will take more time and this
appears to be enough for the most obvious problems

----------------------------------------------------------------
David Howells (1):
      9p: Fix v9fs_issue_write() to update i_size and remote_i_size

 fs/9p/vfs_addr.c | 28 +++++++++++++++++++++++++++-
 1 file changed, 27 insertions(+), 1 deletion(-)
-- 
Dominique Martinet | Asmadeus

             reply	other threads:[~2026-09-14  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  9:34 Dominique Martinet [this message]
2026-09-14 18:07 ` [GIT PULL] 9p regression fix for 7.3-rc4 pr-tracker-bot

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=aqe_sF0kM6mGn_KY@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=dhowells@redhat.com \
    --cc=ericvh@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=mike@method-b.uk \
    --cc=pc@manguebit.org \
    --cc=regressions@lists.linux.dev \
    --cc=torvalds@linux-foundation.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 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.