mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nitin Gupta <nitingupta910@gmail.com>,
	Richard Purdie <rpurdie@openedhand.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Markus F.X.J. Oberhumer" <markus@oberhumer.com>,
	Dave Rodgman <dave.rodgman@arm.com>
Subject: Re: [PATCH] lib/lzo: Avoid output overruns when compressing
Date: Thu, 27 Feb 2025 09:47:38 +0800	[thread overview]
Message-ID: <Z7_EOjyoC64HbiKP@gondor.apana.org.au> (raw)
In-Reply-To: <hymyvszwshcvqngjlomeyltmpghx6gges76muaz23a6cit5oe2@eas2xjgfynnu>

On Sun, Feb 23, 2025 at 05:40:31PM +0900, Sergey Senozhatsky wrote:
>
> A bit of a pity that NEED_OP() with "goto output_overrun" is only
> for decompression.  It looks equally relevant to the compression
> path.  I'm not insisting on doing something similar in compression
> tho.

I thought HAVE_OP looked nicer but I'll switch to NEED_OP for
the sake of consistency.

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2025-02-27  1:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-23  6:55 Herbert Xu
2025-02-23  8:40 ` Sergey Senozhatsky
2025-02-27  1:47   ` Herbert Xu [this message]
2025-02-24 16:20 ` Markus F.X.J. Oberhumer
2025-02-26 13:00 ` David Sterba
2025-02-27  1:46   ` Herbert Xu
2025-02-27  2:08     ` [v2 PATCH] crypto: lzo - Fix compression buffer overrun Herbert Xu
2025-02-27  9:04       ` [v3 " Herbert Xu
2025-02-28 13:21         ` David Sterba
2025-02-27  3:16     ` [PATCH] lib/lzo: Avoid output overruns when compressing David Sterba
2025-02-28  5:24   ` Sergey Senozhatsky
2025-02-28 12:43     ` Ard Biesheuvel
2025-02-28 13:55       ` Sergey Senozhatsky
2025-02-28 14:02         ` David Sterba

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=Z7_EOjyoC64HbiKP@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=dave.rodgman@arm.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@oberhumer.com \
    --cc=nitingupta910@gmail.com \
    --cc=rpurdie@openedhand.com \
    --cc=senozhatsky@chromium.org \
    --cc=torvalds@linux-foundation.org \
    /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®