v9fs.lists.linux.dev archive mirror
 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 6.7-rc7
Date: Fri, 22 Dec 2023 10:07:30 +0900	[thread overview]
Message-ID: <ZYThUpCUMJUMP3Oy@codewreck.org> (raw)

The following changes since commit 2cc14f52aeb78ce3f29677c2de1f06c0e91471ab:

  Linux 6.7-rc3 (2023-11-26 19:59:33 -0800)

are available in the Git repository at:

  https://github.com/martinetd/linux tags/9p-for-6.7-rc7

for you to fetch changes up to ff49bf1867578f23a5ffdd38f927f6e1e16796c4:

  net: 9p: avoid freeing uninit memory in p9pdu_vreadf (2023-12-13 05:44:30 +0900)

----------------------------------------------------------------
Two small fixes scheduled for stable trees

A tracepoint fix that's been reading past the end of messages forever,
but semi-recently also went over the end of the buffer.
And a potential incorrectly freeing garbage in pdu parsing error path

----------------------------------------------------------------
Fedor Pchelkin (1):
      net: 9p: avoid freeing uninit memory in p9pdu_vreadf

JP Kobryn (1):
      9p: prevent read overrun in protocol dump tracepoint

 include/trace/events/9p.h | 11 +++++++----
 net/9p/protocol.c         | 17 +++++++++++++----
 2 files changed, 20 insertions(+), 8 deletions(-)

Cheers,
-- 
Dominique

             reply	other threads:[~2023-12-22  1:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22  1:07 Dominique Martinet [this message]
2023-12-22 16:02 ` [GIT PULL] 9p fixes for 6.7-rc7 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=ZYThUpCUMJUMP3Oy@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).