Linux-bcachefs Archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
	 Guo Xuenan <guoxuenan@huawei.com>,
	Rajat Asthana <thisisrast7@gmail.com>,
	 Gao Xiang <xiang@kernel.org>, Nick Terrell <terrelln@fb.com>
Cc: linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: lz4 hc buffer overflow
Date: Sun, 10 Mar 2024 20:00:24 -0400	[thread overview]
Message-ID: <js2vmwcgwyx5kxq3csunc3piwkpfsebg3u2zewok6iis5wgn2e@eyy4fzryskj7> (raw)

reference https://github.com/koverstreet/bcachefs/issues/658

It looks like something is off with the bounds checking in LZ4 HC; I
haven't dug too deep yet. Never saw this with regular LZ4.

Anyone know anything? Are we missing a fix from the userspace library?

                 reply	other threads:[~2024-03-11  0:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=js2vmwcgwyx5kxq3csunc3piwkpfsebg3u2zewok6iis5wgn2e@eyy4fzryskj7 \
    --to=kent.overstreet@linux.dev \
    --cc=guoxuenan@huawei.com \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terrelln@fb.com \
    --cc=thisisrast7@gmail.com \
    --cc=xiang@kernel.org \
    --cc=yangtiezhu@loongson.cn \
    /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).