---
CVE-2016-2069-x86-mm-Add-barriers.patch | 161
Makefile| 1 +
2 files changed, 162 insertions(+)
create mode 100644 CVE-2016-2069-x86-mm-Add-barriers.patch
diff --git a/CVE-2016-2069-x86-mm-Add-barriers.patch
b/CVE-2016-2069
I thing we should do that check inside the Resource->migrate()
method. That way there is no need to export that is_on_node() API.
There is no real need to do an additional check
inside exec_resource_agent()?
___
pve-devel mailing list
pve-devel@pve.prox
comments inline:
> diff --git a/src/PVE/Tools.pm b/src/PVE/Tools.pm
> index 64a57e9..58d943c 100644
> --- a/src/PVE/Tools.pm
> +++ b/src/PVE/Tools.pm
> @@ -940,6 +940,26 @@ sub upid_read_status {
> return "unable to read tail (got $br bytes)";
> }
>
> +sub upid_wait {
> +my ($upid, $wa
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> @@ -6,6 +9,13 @@ use warnings;
> sub get_index {
> my ($lang, $username, $csrftoken, $console) = @_;
>
> +my $manager_source_dir = '/usr/share/pve-manager/manager6/';
> +
> +## exit early to avoid this being run by mistake
> +if ( ! -d $manager_source_dir) {
> + return "$m
applied.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
If we pass true to the removeAll() , ExtJS6 will try to erase the leafes of a
tree,
and then try to to iterate throuch these leaves in onNodeRemove() ( this
obviously do not work)
The true parameter does not seem to be needed anyway anymore.
After a call to removeAll, the childNodes[] property o
The first and second patch are temporary changes needed for developpement , the
third patch is a bug fix
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
This way, we don't have to manage manually the list files and let the FS do it.
For development purpose only.
---
PVE/ExtJSIndex6.pm | 424 -
1 file changed, 223 insertions(+), 201 deletions(-)
diff --git a/PVE/ExtJSIndex6.pm b/PVE/ExtJSIndex6.p
---
www/manager6/lxc/Config.js | 152
www/manager6/qemu/Config.js | 12 ++--
www/manager6/storage/Browser.js | 19 +++--
3 files changed, 98 insertions(+), 85 deletions(-)
diff --git a/www/manager6/lxc/Config.js b/www/manager6/lxc/Config.js
inde
To prevent error at VM starting, when we passthrough a harddrive from host to
vm.
---
PVE/QemuServer.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index d72ed6d..70a03e0 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@ -1285,6 +1285,7 @@ sub
>>Is it really a problem? It thought it is just a warning?
Yes, it's just a warning. I don't see problem.
- Mail original -
De: "dietmar"
À: "aderumier" , "pve-devel"
Envoyé: Lundi 25 Janvier 2016 13:25:43
Objet: Re: [pve-devel] watchdog-mux.socket has been removed, but not disabled
>
>
> #systemctl daemon-reload
>
> don't fix the problem
Is it really a problem? It thought it is just a warning?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
I just tried to to last updates from pvetest repository,
without reboot after.
restarting pve-manager service, trigger a
systemd[1]: Cannot add dependency job for unit watchdog-mux.socket, ignoring:
Unit watchdog-mux.socket failed to load: No such file or directory
#systemctl daemon-reload
Waits for a process identified by a UPID to end by busy waiting
and is intended for long running workers.
waitfunc gets called every wait cycle after min $sleep_interval
seconds and can be used for outputting/logging something or timing
out the wait.
---
changes v3:
* do it in a sane way without
---
As separate commit...
infinite-loop-fix.patch | 11 +++
1 file changed, 11 insertions(+)
diff --git a/infinite-loop-fix.patch b/infinite-loop-fix.patch
index ba37890..cdef6b8 100644
--- a/infinite-loop-fix.patch
+++ b/infinite-loop-fix.patch
@@ -14,6 +14,17 @@ Date: Tue Nov 3 18:0
Waits for a process identified by a UPID to end by busy waiting
and is intended for long running workers.
waitfunc gets called every wait cycle after min $sleep_interval
seconds and can be used for outputting/logging something.
$sleep_intervall denotes how long the wait periods between two
checks
---
Makefile| 1 +
infinite-loop-fix.patch | 97 +
2 files changed, 98 insertions(+)
create mode 100644 infinite-loop-fix.patch
diff --git a/Makefile b/Makefile
index d13e9a9..deb7656 100644
--- a/Makefile
+++ b/Makefile
@@ -207,6
This does not compile for me:
CC [M] arch/x86/kvm/svm.o
arch/x86/kvm/svm.c: In function ‘init_vmcb’:
arch/x86/kvm/svm.c:794:12: error: ‘AC_VECTOR’ undeclared (first use in this
function)
arch/x86/kvm/svm.c:794:12: note: each undeclared identifier is reported only
once for each function it appears
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
This is useful on large zfs pools because they take longer to response.
---
PVE/Storage/ZFSPlugin.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/PVE/Storage/ZFSPlugin.pm b/PVE/Storage/ZFSPlugin.pm
index 5074ba4..d6339ce 100644
--- a/PVE/Storage/ZFSPlugin.pm
+++ b/PVE/Storag
applied.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Am 25.01.2016 um 09:20 schrieb Wolfgang Bumiller:
>> On January 25, 2016 at 8:50 AM Stefan Priebe - Profihost AG
>> wrote:
>>
>>
>> Am 22.01.2016 um 10:37 schrieb Dietmar Maurer:
Am 20.01.2016 um 10:26 schrieb Wolfgang Bumiller:
> Just a quick follow-up question: Is this not supposed to
> On January 25, 2016 at 9:20 AM Wolfgang Bumiller
> wrote:
>
>
> > On January 25, 2016 at 8:50 AM Stefan Priebe - Profihost AG
> > wrote:
> >
> >
> > Am 22.01.2016 um 10:37 schrieb Dietmar Maurer:
> > >> Am 20.01.2016 um 10:26 schrieb Wolfgang Bumiller:
> > >>> Just a quick follow-up ques
> On January 25, 2016 at 8:50 AM Stefan Priebe - Profihost AG
> wrote:
>
>
> Am 22.01.2016 um 10:37 schrieb Dietmar Maurer:
> >> Am 20.01.2016 um 10:26 schrieb Wolfgang Bumiller:
> >>> Just a quick follow-up question: Is this not supposed to include
> >>> data blocked by the firewall?
> >>
> >>
Am 25.01.2016 um 09:11 schrieb Dietmar Maurer:
>
>> I just looked at the code regarding #871 which just adds veth devices.
>> Which patch do you mean?
>
> Yes, I am talking about those patches.
>
Sorry seems i miss something. This single patch
(http://comments.gmane.org/gmane.linux.pve.devel/1
> I just looked at the code regarding #871 which just adds veth devices.
> Which patch do you mean?
Yes, I am talking about those patches.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
29 matches
Mail list logo
