Excessive virtio_balloon inflation can cause invocation of OOM-killer, when
Linux is under severe memory pressure. Various mechanisms are responsible for
correct virtio_balloon memory management. Nevertheless it is often the case
that these control tools does not have enough time to react on fast c
From: Raushaniya Maksudova
This value would be useful in the next patch to provide the amount of
the freed memory for OOM killer.
Accessing to vb->num_pfns outside of vb->balloon_lock is wrong and unsafe.
Signed-off-by: Raushaniya Maksudova
Signed-off-by: Denis V. Lunev
CC: Rusty Russell
CC:
From: Raushaniya Maksudova
Excessive virtio_balloon inflation can cause invocation of OOM-killer,
when Linux is under severe memory pressure. Various mechanisms are
responsible for correct virtio_balloon memory management. Nevertheless
it is often the case that these control tools does not have e
Hi,
I'm hitting this bug with both ext4 and btrfs.
Here's an example of the backtrace:
https://gist.github.com/vzctl/e888a821333979120932
I tried raising this BUG only for direct ring and it solved the problem:
- BUG_ON(total_sg > vq->vring.num);
+ BUG_ON(total_sg > vq->vring.num &
On Tue, 07 Oct 2014 18:24:22 -0700
Andy Lutomirski wrote:
> On 10/07/2014 07:39 AM, Cornelia Huck wrote:
> > This patchset aims to get us some way to implement virtio-1 compliant
> > and transitional devices in qemu. Branch available at
> >
> > git://github.com/cohuck/qemu virtio-1
> >
> > I've