similar to: [PATCH] libxc: Fix memory leak in zlib usage

Hi, libxc contains the following function which is used when uncompressing zipped kernel images: /* ------------------------------------------------------------------------ */ /* read files, copy memory blocks, with transparent gunzip */ size_t xc_dom_check_gzip(void *blob, size_t ziplen) { unsigned char *gzlen; size_t unziplen; if ( strncmp(blob,

This patch (apologies for the size) updates zlib/* to the files that ship with zlib 1.1.3. Index: zlib/ChangeLog =================================================================== RCS file: /cvsroot/rsync/zlib/ChangeLog,v retrieving revision 1.1 diff -u -r1.1 ChangeLog --- zlib/ChangeLog 7 May 1998 06:19:41 -0000 1.1 +++ zlib/ChangeLog 30 Jan 2002 01:12:41 -0000 @@ -1,6 +1,54 @@ ChangeLog

I am just now getting around to upgrading from 3.1.2 to 3.2.0 and am getting hammered by a problem which is beyond my limited capabilities of handling. I executed ./configure --with-tcltk --with cairo which seemed to go just fine, and then did: make In fairly short order I started getting error messages like unto: > connections.o: In function `gzcon_write': >

I am just now getting around to upgrading from 3.1.2 to 3.2.0 and am getting hammered by a problem which is beyond my limited capabilities of handling. I executed ./configure --with-tcltk --with cairo which seemed to go just fine, and then did: make In fairly short order I started getting error messages like unto: > connections.o: In function `gzcon_write': >

When CONFIG_KLIBC_ZLIB is not set, related functions shall not be called otherwise build failure is encountered: KLIBCLD usr/kinit/static/kinit usr/kinit/ramdisk_load.o: In function `load_ramdisk_compressed': /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:68: undefined reference to `inflateInit2_' /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:116: undefined

I am cross-posting this to r-sig-fedora (I hope that's not an egregious sin) in the hope that doing so might provide some source of insight. I tried sudo yum install zlib and was told > Package zlib-1.2.5-7.fc17.x86_64 already installed and latest version Likewise for "zlib-devel". I also tried sudo yum install bzlib and was told > No package bzlib

On Thu, 2014-11-20 at 22:13 -0500, Gedalya wrote: > On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: > >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which > >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other > >> than the gzip one)

1. R 3.2.0 is packaged for Fedora now; it's in Rawhide and Fedora 22. I'm running Fedora 22 (late beta) and haven't had any problems with R. RStudio Desktop Preview (0.99.435) from the RStudio Fedora RPM is also running fine. You might save yourself some hassles by upgrading to Fedora 22. 2. I have a bash script to build R from source that works on Fedora 22. It probably also works on

On 11/05/15 12:06, M. Edward (Ed) Borasky wrote: > 1. R 3.2.0 is packaged for Fedora now; it's in Rawhide and Fedora 22. > I'm running Fedora 22 (late beta) and haven't had any problems with R. > RStudio Desktop Preview (0.99.435) from the RStudio Fedora RPM is also > running fine. You might save yourself some hassles by upgrading to > Fedora 22. I'm sure I would,

https://bugzilla.samba.org/show_bug.cgi?id=11215 Bug ID: 11215 Summary: compression/zlib errors discard the zlib error message Product: rsync Version: 3.1.0 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org

On 11/05/15 16:19, Tom Callaway wrote: > I just landed in Paris, and haven't read backwards in this thread, > but I've done 3.2.0 builds for all current Fedora releases, they're > all in updates-testing (I think the Fedora 22 builds are in updates > stable now). > > The thing that changed is that R doesn't bundle a number of libraries > like it used to. This

When CONFIG_KLIBC_ZLIB is not set, related functions shall not be called otherwise build failure is encountered: KLIBCLD usr/kinit/static/kinit usr/kinit/ramdisk_load.o: In function `load_ramdisk_compressed': /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:68: undefined reference to `inflateInit2_' /root/ldb_base/ofl/packages/klibc/usr/kinit/ramdisk_load.c:116: undefined

Commit-ID: 534a04d85defc627b031906d27cd9d09a913adc4 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=534a04d85defc627b031906d27cd9d09a913adc4 Author: Christophe Leroy <christophe.leroy at c-s.fr> AuthorDate: Wed, 23 Jan 2019 06:16:01 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 24 Jan 2019 23:11:11 +0000 [klibc] fix build failure

I just landed in Paris, and haven't read backwards in this thread, but I've done 3.2.0 builds for all current Fedora releases, they're all in updates-testing (I think the Fedora 22 builds are in updates stable now). The thing that changed is that R doesn't bundle a number of libraries like it used to. This doesn't affect the official Fedora R package, since we never used the

On Fri, 2014-11-21 at 11:03 +0000, Ian Campbell wrote: > http://man7.org/linux/man-pages/man3/mallopt.3.html also talks about > various dynamic thresholds for growing and shrinking the heap. My guess > is that we are bouncing up and down over some threshold with every other > reboot. IOW I'm not overly concerned with this apparent bi-modality, so long as the amount isn't

When using the -z and -B65536 options together, sometimes there is file corruption. Client and server are both compiled against zlib 1.1.4, so the gzip corruption shouldn't be there, right? With -z and -B32768 there is an error, but it is detected in a different way. With -B65536 and without -z all seems to be going OK. With -B16384 and with -z all seems to be going OK. I'm guessing

On 11/20/2014 03:21 PM, Konrad Rzeszutek Wilk wrote: > On Thu, Nov 20, 2014 at 03:48:47PM +0000, Ian Campbell wrote: >> The libxc xc_dom_* infrastructure uses a very simple malloc memory pool which >> is freed by xc_dom_release. However the various xc_try_*_decode routines (other >> than the gzip one) just use plain malloc/realloc and therefore the buffer ends >> up

On Fri, 2014-11-21 at 15:25 -0500, Gedalya wrote: > On 11/21/2014 06:12 AM, Ian Campbell wrote: > > On Fri, 2014-11-21 at 11:03 +0000, Ian Campbell wrote: > >> http://man7.org/linux/man-pages/man3/mallopt.3.html also talks about > >> various dynamic thresholds for growing and shrinking the heap. My guess > >> is that we are bouncing up and down over some

On 11/21/2014 06:12 AM, Ian Campbell wrote: > On Fri, 2014-11-21 at 11:03 +0000, Ian Campbell wrote: >> http://man7.org/linux/man-pages/man3/mallopt.3.html also talks about >> various dynamic thresholds for growing and shrinking the heap. My guess >> is that we are bouncing up and down over some threshold with every other >> reboot. > IOW I'm not overly concerned

The following two fixes by Jürgen Keil have been in qemu for a year now. They are still missing in ioemu. [Qemu-devel] PATCH: qcow2 image corruption http://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00773.html [Qemu-devel] [PATCH] qcow2: release refcount table clusters of the old table, after growing the refcount table http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00043.html