Displaying 11 results from an estimated 11 matches for "msg00084".
Did you mean:
msg00004
2015 Dec 30
2
Centos 7 guest - long delay on mounting /boot with host disk write cache off
Hello,
I've noticed a strange delay while booting a CentOS 7 guest on a CentOS
7 host with slow disks (7200RPM) with write cache off.
The guest and host are freshly installed Centos 7 (host was fully
patched before guest install). Guest is installed on an lvm pool
residing on an md raid1 with two SATA 7200 RPM drives with their write
caches off.
The delay is on mounting /boot, the dmesg
2015 Dec 31
0
Centos 7 guest - long delay on mounting /boot with host disk write cache off
On 12/30/2015 06:26 AM, Andrzej Szymanski wrote:
> Is is normal for the xfs mount to replay a log after a clean unmount?
Yes, apparently:
http://oss.sgi.com/archives/xfs/2009-10/msg00084.html
2017 Oct 13
2
[PATCH] virtio: avoid possible OOM lockup at virtballoon_oom_notify()
On Tue, Oct 10, 2017 at 07:47:37PM +0900, Tetsuo Handa wrote:
> In leak_balloon(), mutex_lock(&vb->balloon_lock) is called in order to
> serialize against fill_balloon(). But in fill_balloon(),
> alloc_page(GFP_HIGHUSER[_MOVABLE] | __GFP_NOMEMALLOC | __GFP_NORETRY) is
> called with vb->balloon_lock mutex held. Since GFP_HIGHUSER[_MOVABLE]
> implies __GFP_DIRECT_RECLAIM |
2017 Oct 13
2
[PATCH] virtio: avoid possible OOM lockup at virtballoon_oom_notify()
On Tue, Oct 10, 2017 at 07:47:37PM +0900, Tetsuo Handa wrote:
> In leak_balloon(), mutex_lock(&vb->balloon_lock) is called in order to
> serialize against fill_balloon(). But in fill_balloon(),
> alloc_page(GFP_HIGHUSER[_MOVABLE] | __GFP_NOMEMALLOC | __GFP_NORETRY) is
> called with vb->balloon_lock mutex held. Since GFP_HIGHUSER[_MOVABLE]
> implies __GFP_DIRECT_RECLAIM |
2017 Oct 13
0
[PATCH] virtio: avoid possible OOM lockup at virtballoon_oom_notify()
...el at I-love.SAKURA.ne.jp>
>
> This doesn't deflate on oom if lock is contended, and we acked
> DEFLATE_ON_OOM so host actually expects us to.
I still don't understand what is wrong with not deflating on OOM.
According to https://lists.oasis-open.org/archives/virtio-dev/201504/msg00084.html ,
If VIRTIO_BALLOON_F_DEFLATE_ON_OOM has been negotiated, the
driver MAY use pages from the balloon when \field{num_pages}
is less than or equal to the actual number of pages in the
balloon if this is required for system stability
(e.g. if memory is required by applications running...
2018 Aug 02
10
[PATCH 0/3] file: Zero for block devices and older file systems
...).
Changes since v1:
- Split to smaller patches
- Skip linux only includes on other systems
- Skip code using BLKZEROOUT if the macro is not defined
- Try BLKZEROOUT only if the offset and count are aligned to device
sector size.
v1 was here:
https://www.redhat.com/archives/libguestfs/2018-July/msg00084.html
Nir Soffer (3):
file: Avoid unsupported fallocate() calls
file: Support zero without ZERO_RANGE
file: Zero for block devices on old kernels
plugins/file/file.c | 194 +++++++++++++++++++++++++++++++++-----------
1 file changed, 147 insertions(+), 47 deletions(-)
--
2.17.1
2019 Nov 14
1
ANNOUNCE: libnbd 1.2 & nbdkit 1.16 - high performance NBD client and server
...ntains an up to date list of past security issues.
CVE-2019-14850 denial of service due to premature opening of back-end
connection
See the full announcement and links to mitigation, tests and fixes
here:
https://www.redhat.com/archives/libguestfs/2019-September/msg00084.html
CVE-2019-14851 assertion failure by issuing commands in the wrong order
This CVE was caused by the fix to the previous issue.
See the full announcement and links to mitigation, tests and fixes
here:
https://www.redhat.com/archives/libguestfs/2019-September...
2018 Jul 28
3
[PATCH] file: Normalize errno value for ENODEV
Fix issues Eric found in the original patch:
https://www.redhat.com/archives/libguestfs/2018-July/msg00072.html
- When handling ENODEV, the caller is expecting ENOTSUPP to trigger
fallback.
- ENODEV should be ignored in file_trim.
Tested only on Fedora 28.
---
plugins/file/file.c | 33 ++++++++++++++++++++++++---------
1 file changed, 24 insertions(+), 9 deletions(-)
diff --git
2018 Aug 03
10
[PATCH v2 0/4] file: Zero for block devices and older file systems
...acros were not defined.
- Use new h->can_punch_hole in file_can_trim, so now we report the
actual capability once we detected it.
- Use h->can_punch_hole in file_trim, so we try only once if the
operation is not supported.
v1 was here:
https://www.redhat.com/archives/libguestfs/2018-July/msg00084.html
Nir Soffer (4):
file: Avoid unsupported fallocate() calls
file: Support zero without ZERO_RANGE
common: Add isaligned helper module
file: Zero for block devices on old kernels
common/include/isaligned.h | 50 ++++++++++
plugins/file/Makefile.am | 3 +-
plugins/file/file.c...
2017 Oct 15
2
[PATCH] virtio: avoid possible OOM lockup at virtballoon_oom_notify()
...hen it's
fine as allocations fail, but if you inflate and then
enter OOM, balloon won't give up memory.
The flag is unfortunately hard for management tools to use
which led to it still not being supported by hosts.
> According to https://lists.oasis-open.org/archives/virtio-dev/201504/msg00084.html ,
>
> If VIRTIO_BALLOON_F_DEFLATE_ON_OOM has been negotiated, the
> driver MAY use pages from the balloon when \field{num_pages}
> is less than or equal to the actual number of pages in the
> balloon if this is required for system stability
> (e.g. if memory is req...
2017 Oct 15
2
[PATCH] virtio: avoid possible OOM lockup at virtballoon_oom_notify()
...hen it's
fine as allocations fail, but if you inflate and then
enter OOM, balloon won't give up memory.
The flag is unfortunately hard for management tools to use
which led to it still not being supported by hosts.
> According to https://lists.oasis-open.org/archives/virtio-dev/201504/msg00084.html ,
>
> If VIRTIO_BALLOON_F_DEFLATE_ON_OOM has been negotiated, the
> driver MAY use pages from the balloon when \field{num_pages}
> is less than or equal to the actual number of pages in the
> balloon if this is required for system stability
> (e.g. if memory is req...