public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Schoenebeck <linux_oss@crudebyte.com>,
	Eric Van Hensbergen <ericvh@kernel.org>,
	v9fs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] 9p fixes for 7.1-rc1
Date: Fri, 24 Apr 2026 19:28:48 +0900	[thread overview]
Message-ID: <aetF4EENt3meh6lt@codewreck.org> (raw)


Hi Linus,

I'm a bit swamped with real life priorities; there are a couple of other
known 9p bugs that I'd have liked to see fixed for 7.1 but fixes aren't
obvious and there's doesn't seem to be any consensus so here's what's
safe to take for now.

Thanks,

--------
The following changes since commit 028ef9c96e96197026887c0f092424679298aae8:

  Linux 7.0 (2026-04-12 13:48:06 -0700)

are available in the Git repository at:

  https://github.com/martinetd/linux tags/9p-for-7.1-rc1

for you to fetch changes up to 8fc518e489c1386fd0cf7f4256d055960ed6a2e4:

  9p/trans_xen: replace simple_strto* with kstrtouint (2026-04-16 02:57:01 +0000)

----------------------------------------------------------------
- 9p access flag fix (cannot change access flag since new mount API implem)
- some minor cleanup

----------------------------------------------------------------
Kit Dallege (1):
      9p: document missing enum values in kernel-doc comments

Pierre Barre (1):
      9p: fix access mode flags being ORed instead of replaced

Sasha Levin (1):
      9p: fix memory leak in v9fs_init_fs_context error path

Yufan Chen (2):
      9p/trans_xen: make cleanup idempotent after dataring alloc errors
      9p/trans_xen: replace simple_strto* with kstrtouint

 fs/9p/v9fs.c        |  4 ++++
 fs/9p/vfs_super.c   |  6 +++---
 include/net/9p/9p.h | 38 +++++++++++++++++++++++++++++++++++---
 net/9p/trans_xen.c  | 77 +++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------
 4 files changed, 95 insertions(+), 30 deletions(-)

-- 
Dominique Martinet | Asmadeus


             reply	other threads:[~2026-04-24 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24 10:28 Dominique Martinet [this message]
2026-04-24 20:51 ` [GIT PULL] 9p fixes for 7.1-rc1 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=aetF4EENt3meh6lt@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=ericvh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox