similar to: Candidate for packet compression: XZ

Hello, the included XZ Utils source code contains an incorrect use of the restrict keyword. This leads to data corruption under certain circumstances. For a short discussion of the problem see http://sourceforge.net/projects/lzmautils/forums/forum/708858/topic/3306733 This was fixed in the XZ Utils git repository in commit commit 49cfc8d392cf535f8dd10233225b1fc726fec9ef Author: Lasse

flight 9061 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/9061/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-amd 5 xen-boot fail REGR. vs. 8995 Tests which are failing intermittently (not blocking): test-amd64-i386-pv 5 xen-boot fail pass in 9054 test-i386-i386-pv

From: Lasse Collin <lasse.collin@tukaani.org> Return value of rc->fill() is checked in rc_read() and error() is called when needed, but then the code continues as if nothing had happened. rc_read() is a void function and it''s on the top of performance critical call stacks, so propagating the error code via return values doesn''t sound like the best fix. It seems better

compression : xz, Level 6 here some compression rates I experienced : Diskspace usage : user1: uncompressed : 2.3GB --> compressed 1 GB user2: uncompressed : 6.2GB --> compressed 3.9 GB just for your reference Ing. Robert Nowotny Rotek GmbH Vienna/Austria

https://bugzilla.samba.org/show_bug.cgi?id=6839 Summary: more dont compress entries Product: rsync Version: 3.0.6 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: karl at freefriends.org

From: Lasse Collin <lasse.collin@tukaani.org> The code assumes that the input is valid and not truncated. Add checks to avoid reading past the end of the input buffer. Change the type of "skip" from u8 to int to fix a possible integer overflow. Signed-off-by: Lasse Collin <lasse.collin@tukaani.org> Signed-off-by: Jan Beulich <jbeulich@suse.com> ---

On Thu, May 14, 2020 at 1:32 PM Laine Stump <laine@redhat.com> wrote: > On 5/13/20 12:52 AM, Subhendu Ghosh wrote: > > Hi > > > > Couple of questions around macvtap direct usage: > > > > 1) is the document here current? > > https://libvirt.org/formatnetwork.html#examplesDirect > > Yes. None of that has changed in any major way in many years. >

Hello, Just wondering: Dovecot has gzip/bzip2 compression/decompression support. According to this: http://stephane.lesimple.fr/wiki/blog/lzop_vs_compress_vs_gzip_vs_bzip2_vs_lzma_vs_lzma2-xz_benchmark_reloaded gzip and bzip2 aren't really useful together. While gzip can offer speed and a reasonable amount of compression ratio, bzip2 is slow, especially on decompression, which Dovecot does

i have enabled the zlib plugin with xz compression but on some new mails i got now a segfault and the following lines in dovecot error.log Dec 12 08:51:23 imap(tester at domain.com): Error: lzma.read(/srv/vmail/mail/domain.com/root/storage/m.3): unexpected EOF at 136004 Dec 12 08:51:23 imap(tester at domain.com): Error: read(zlib(/srv/vmail/mail/domain.com/root/storage/m.3)) failed:

Hallo Everyone, since some days a new dovecot version is available in Debian "wheezy-backports": (1:2.2.9-1~bpo70+1) wheezy-backports As described in http://wiki2.dovecot.org/Plugins/Zlib and http://www.dovecot.org/doc/NEWS-2.2 "xz"-compression is available since Dovecot version 2.2.9. Today I tried to convert my mailboxes with the new xz compression. Therfore I changed

when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file gets corrupted. the same configuration was working ok on low load with xz compression. Dovecot Version 2.2.12 Linux Mint 16 EXT4 Filesystem another dovecot user already reported the same problem on the mailinglist, using dsync. That user switched to bz2 compression what worked for him. the answer was : > are you on

when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file gets corrupted. the same configuration was working ok on low load with xz compression. Dovecot Version 2.2.12 Linux Mint 16 EXT4 Filesystem another dovecot user already reported the same problem on the mailinglist, using dsync. That user switched to bz2 compression what worked for him. the answer was : > are you on

Hello Timo, I've successfully setup xz compression for my Dovecot installation using the version 2.2.12 from Debian unstable. Together with the activation of the "Single Instance Attachment Storage", this reduced the mail storage utilization for 20 mail accounts by 74%. *My question:* (For this test just one user was logged in. OS = Debian Wheezy, AMD64) After conversion of my

While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12 (compiled from source) dsync aborts with a backtrace on some (maybe 15 out of 800) mail accounts: (same error happens wiht or without -f flag) dsync -D -v -o mail_fsync=never mirror -f -R -u user at domain imapc: <snip> dsync(user at domain.com): Debug: brain M: in state=sync_mails dsync(user at domain.com): Debug: brain M:

Hi Michael, when I was looking for information on tinc in combination with IPv6, I also found your new tutorial at that time (earlier this month). Somehow a couple of things are less clear to me in the newer tutorial (maybe the nice network topology image is missing). OK, you added the unique local addresses to the setup. But I dont't get it how the routing is done in your setup. You

The kernel header guard to ensure that headers aren't included from userland moved in commit 69c8f52b. This causes the following message to be emitted when building klibc (which is designed to use kernel headers explicitly): /usr/local/src/git/linux-2.6//include/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see

Hello. I'm setting up a computer that will run 'CentOS 6 server'. The MB is an Asus with a hw raid controller (Promise PDC-20276), which I want to use in RAID-1 mode. I noted (from a MB website) that it also needs a driver - which is probably why it's called a 'fakeraid'. So, I've been trying to determine if any recent kernels support this chip. Using

I found that I''m able to provoke undefined behaviour with 2.6.38 with extent defragmenting + recompression, eg: mkfs.btrfs /dev/sdb mount /dev/sdb /mnt cp -xa / /mnt find /mnt -print0 | xargs -0 btrfs filesystem defragment -vc After a short time, I was seeing what looked like a secondary effect [1]. Reproducing with lock instrumentation reported recursive spinlock acquisition, probably

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -------------- next part -------------- >From 1ff2c479a63574395903361bfb037e555c69ad26 Mon Sep 17 00:00:00 2001 From:

Following up on these threads: - https://marc.info/?l=kvm&m=151929803301378&w=2 - http://www.openwall.com/lists/kernel-hardening/2018/02/22/18 I lost the original emails so I couldn't reply to them, and also sorry for being late, it was the end of semester exams. I was adviced on #qemu and #kernelnewbies IRCs to ask here as it will help having better insights. To wrap things up, the