From: u-vpoa@aetey.se
To: Jody Bruchon <jody@jodybruchon.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: another fix for huge data (Re: a compression tool useful with constrained memory)
Date: Wed, 29 Apr 2015 17:10:48 +0200 [thread overview]
Message-ID: <20150429151048.GK8197@example.net> (raw)
In-Reply-To: <20150427210409.GB8197@example.net>
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
Noticed a situation where we would divide by zero:
+ * version 0.2015-04-29
+ * avoid division by zero when the input length
+ * differs from N*4GB less than 100 bytes
Attaching a patch which should apply cleanly (build tested with
a different patch version, for the original source format).
Regards,
Rl
[-- Attachment #2: patch.20150429.bz2 --]
[-- Type: application/octet-stream, Size: 1261 bytes --]
prev parent reply other threads:[~2015-04-29 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 12:29 a compression tool useful with constrained memory u-vpoa
2015-04-26 12:36 ` Jody Bruchon
2015-04-26 13:11 ` u-vpoa
2015-04-26 16:49 ` Status updates: compression tool, kernel fixes, BCC features, etc Jody Bruchon
2015-04-27 21:04 ` a compression tool useful with constrained memory u-vpoa
2015-04-29 15:10 ` u-vpoa [this message]
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=20150429151048.GK8197@example.net \
--to=u-vpoa@aetey.se \
--cc=jody@jodybruchon.com \
--cc=linux-8086@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).