mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Yichong Chen <chenyichong@uniontech.com>
Cc: dhowells@redhat.com, netfs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cachefiles: fix out-of-bounds read in coherency trace
Date: Thu, 27 Aug 2026 08:31:18 +0100	[thread overview]
Message-ID: <1924988.1787815878@warthog.procyon.org.uk> (raw)
In-Reply-To: <20260827061444.2404961-1-chenyichong@uniontech.com>

Thanks, but I have a patch for this.  See patch 9 here:

https://lore.kernel.org/linux-fsdevel/20260825132045.1000787-1-dhowells@redhat.com/

I don't want to call memcpy() like this just for the purposes of a tracepoint
that is almost certainly not actually be active.

You're also moving buf->content into a variable rather than using it directly
- is there a reason for that?

David


  reply	other threads:[~2026-08-27  7:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  6:14 Yichong Chen
2026-08-27  7:31 ` David Howells [this message]
2026-08-27  8:05   ` Yichong Chen

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=1924988.1787815878@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=chenyichong@uniontech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfs@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
all inboxes | Powered by JetHome®