similar to: Xen Security Advisory 82 (CVE-2013-6885) - Guest triggerable AMD CPU erratum may cause host hang

Author: kucharsk Repository: /hg/zfs-crypto/gate Revision: b1f167e9bcec854103004aa601a56ab937e1223c Log message: 6288246 amd64 kernel needs to detect AMD Opteron erratum 131 Files: update: usr/src/uts/i86pc/Makefile.workarounds update: usr/src/uts/i86pc/os/cpuid.c update: usr/src/uts/i86pc/os/mp_startup.c update: usr/src/uts/intel/sys/controlregs.h

I will reply those comments tomorrow. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191204/f1111299/attachment.html>

Hi, Ooops, mistake, please read host# tapdisk2 -n vhd:/storage/test.vhd instead of host# tapdisk2 -n vhc:/storage/test.vhd in my previous post. Kind regards, Sébastien _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Author: kchow Repository: /hg/zfs-crypto/gate Revision: 1d1ea58da530f01d6bbadddd7bf5d0db64a0c96f Log message: 6295986 False AMD Erratum 123 warning message on stinger dual-core machines Files: update: usr/src/uts/i86pc/Makefile.workarounds update: usr/src/uts/i86pc/os/mp_startup.c

Hi I''ve installed Solaris snv111 in a QEMU virtual machine using qemu 0.10.2 with kqemu 1.4 enabled. The installation worked without problems but after rebooting from the virtual disk Solaris panics: qemu usage: /opt/qemu_0.10.x/bin/qemu-system-x86_64 -net user -net nic -usb -usbdevice tablet -L /usr/local/share/qemu_0.9.x -boot c -m 1024 -net nic,model=rtl8139 -net nic -net nic

Hi: This series try to prevent a guest triggerable CPU hogging through vhost kthread. This is done by introducing and checking the weight after each requrest. The patch has been tested with reproducer of vsock and virtio-net. Only compile test is done for vhost-scsi. Please review. This addresses CVE-2019-3900. Changs from V1: - fix user-ater-free in vosck patch Jason Wang (4): vhost:

Hi: This series try to prevent a guest triggerable CPU hogging through vhost kthread. This is done by introducing and checking the weight after each requrest. The patch has been tested with reproducer of vsock and virtio-net. Only compile test is done for vhost-scsi. Please review. This addresses CVE-2019-3900. Changs from V1: - fix user-ater-free in vosck patch Jason Wang (4): vhost:

I have been run into a weird problem with dovecot. We have 4 identical servers running dovecot, serving both IMAP and POP3 clients. Every few hours, clients start timing out after the PASS command. Here is what the process tree looks like at that time: 6718 ? Ss 0:00 /usr/sbin/dovecot 6719 ? S 0:00 \_ dovecot-auth 6881 ? S 0:00 | \_ dovecot-auth 6883

CentOS Errata and Security Advisory 2014:X005 (Xen4CentOS) The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) ----------------------------- X86_64 ----------------------------- 4d780927c1273021f707954531d4f8363f96001a09101ac3b828c02dcf640fc5 e1000e-2.5.4-3.10.29.2.el6.centos.alt.x86_64.rpm

I have wondershaper to limit my upload at 400kilobits (my line is 600kbps). I do a lot of torrent seeding and I dont want my pings killed when I''m uploading so I set low prority source ports as follows (by the way, I have bittornet to only use ports 6881-6910): NOPRIOPORTSRC="6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901

Fence lock needs to be initialized before any call to nouveau_channel_put because it calls nouveau_channel_idle->nouveau_fence_update which uses fence lock. BUG: spinlock bad magic on CPU#0, test/24134 lock: ffff88019f90dba8, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0 Pid: 24134, comm: test Not tainted 3.0.0-nv+ #800 Call Trace: spin_bug+0x9c/0xa3 do_raw_spin_lock+0x29/0x13c

[It seems the last time this came up was in march, under the heading of "Sony Cybershot should be in hardware notes". This message is intended mainly to document what I've managed to track down.] The m500s still will not sync with pilot-link 0.11.7 in -STABLE. An easily triggerable panic is another issue [1]. The pilot-link code first opens /dev/ugenX and then switches to

Hi: This series try to prvernt a guest triggerable CPU hogging through vhost kthread. This is done by introducing and checking the weight after each requrest. The patch has been tested with reproducer of vsock and virtio-net. Only compile test is done for vhost-scsi. Please review. This addresses CVE-2019-3900. Jason Wang (4): vhost: introduce vhost_exceeds_weight() vhost_net: fix possible

Hello, There is still a problem with the _exit_cleanup() function in cleanup.c despite the patch that was put in last week that prevented recursion. It turns out that sometimes multiple calls in close sequence are done and this causes rsync to spin out of control instead of exiting. This bug was found by Marc Espie and the patch I'm including is his as well. It hasn't been commited

Hi list, on my workstation I've a md raid (mirror) for / on md1. This raid has 2 ssd as members (each corsair GT force 120GB MLC). This disks are ~ 5 years old. Today I've checked my ssds smart status and I get: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 050 Pre-fail Always -

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi Jan Back before 4.3 release you complaint about the hardcoded modprobe for blktap / blktap2 in xencommons script. I started to look into it this week and tried to do this modprobe automatically in libxl (that''s the idea we discussed before 4.3 IIRC). Unfortunately I didn''t manage to find any canonical documents on how a user space process can trigger a modprobe.

Has anyone experienced this before? This happened to me even under CentOS 4.x. But basically what happens is that when I play MP3s, whatever the right speaker crackles at higher volume. And it's always that speaker and only that speaker. If I turn the balance to the other speaker I have no problems. So it feels like it might be a mixer issue. I use Alsa, of course, as that's what the

Hi, You may have seen a thread about this issue on the forums, but I wanted post a mail about it here to be sure that it gets noticed by you compiz developers. The problem is that compiz seems to make the screen edges insensitive to clicks, meaning that e.g. a panel item isn't clickable when the pointer is directly at the screen edge. This breaks Fitt's Law and should therefore be fixed

CentOS Errata and Security Advisory 2013:X017 (Xen4CentOS) The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) ----------------------------- X86_64 ----------------------------- 588443b1936d3da45e5872a1578722fdac5ddf0eaeb02b8e47854a3c1d7a45f5 xen-4.2.3-26.el6.centos.alt.x86_64.rpm