search for: requrest

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: introduce vhost_exceeds_weight() vhost_net: fix possible infi...

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: introduce vhost_exceeds_weight() vhost_net: fix possible infi...

Asymmetric wrote: [SNIP] > > I don't know (don't use ices) but I thought I should inform you.. taking > user requests may cause you to violate the RIAA rules regarding that > topic, depending on how you handle it. Be careful. ;) > It's for my office... I'd love to play my CDs on my radio, but it would disturb those that don't like my music. Some do, so

On Fri, May 17, 2019 at 12:29:48AM -0400, Jason Wang wrote: > 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. OK I think we should clean this code some more but given it's a CVE fix maybe it's best to do as a patch on top....

From: Jason Wang <jasowang at redhat.com> Date: Fri, 17 May 2019 00:29:48 -0400 > 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 I am assuming that not only will mst review this...

...ir radio. You MUST follow the RIAA guidelines for non-interactive broadcasts for online radio, and you do not have to follow these for on-the-air radio. This isn't a simple variation. There are completely different rules. For instance, if you fulfill a request, it must be ONE HOUR after the requrest was made (I _think_). Not to mention the normal 'can't play y songs by z in x hours' stuff still applies. Even the companies that simply let users Fast Forward were getting sued by the RIAA. It's a dumb set of rules, a dumb law, and the RIAA is doing a disservice to artists (espe...

...RIAA guidelines for non-interactive broadcasts for online > radio, and you do not have to follow these for on-the-air radio. > > This isn't a simple variation. There are completely different rules. > > For instance, if you fulfill a request, it must be ONE HOUR after the > requrest was made (I _think_). Not to mention the normal 'can't play y > songs by z in x hours' stuff still applies. > > Even the companies that simply let users Fast Forward were getting sued > by the RIAA. > > It's a dumb set of rules, a dumb law, and the RIAA is doing...

On Wed, Jul 13, 2016 at 02:35:08AM -0400, Garland McAlexander wrote: > CIFS is single threaded, if you plan on using it with a large amount of Oh, "my" cifs as a protocol is multi-threaded. It's part of the Samba implementation that is single threaded. However, for large file I/O Samba is multi-threaded. Volker

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 infinite loop vhost: vsock: add weight support vhost:...

.../iodev/cpu.cc 1.7 vs edited ===== --- 1.7/tools/ioemu/iodev/cpu.cc 2005-03-28 11:56:48 -05:00 +++ edited/tools/ioemu/iodev/cpu.cc 2005-03-31 13:55:11 -05:00 @@ -51,7 +51,7 @@ if (req->state == STATE_IOREQ_READY) { req->state = STATE_IOREQ_INPROCESS; } else { - BX_INFO(("False I/O requrest ... in-service already: %lx, pvalid: %lx,port: %lx, data: %lx, count: %lx, size: %lx\n", req->state, req->pdata_valid, req->addr, req->u.data, req->count, req->size)); + BX_INFO(("False I/O request ... in-service already: %lx, pvalid: %lx,port: %lx, data: %lx, count: %l...

This is problem 1 of 3 problems we are having with live migration and/or ACPI on Xen-4.3 and Xen-4.2. Any help would be appreciated. Detailed description of problem: We are using Xen-4.3-rc1 with dom0 running Ubuntu Precise and 3.5.0-23-generic kernel, and domU running Ubuntu Precise (12.04) cloud images running 3.2.0-39-virtual. We are using the xl.conf below on qemu-upstream-dm and HVM and