Displaying 20 results from an estimated 10000 matches similar to: "[PATCH] also override library path for hotplug scripts"
2012 Jun 01
2
[PATCH] pygrub Makefile cleanup.
This patch removes the extra command `install pygrub` because this is already
done by the setup.py script.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
---
This patch need to be applied after the patch named "Fix pygrub install."
tools/pygrub/Makefile | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/tools/pygrub/Makefile
1998 May 19
1
Beware of dangerous enviroment (Re: Overflows in minicom)
On Tue, 12 May 1998, Andi Kleen wrote on BUGTRAQ:
> I assumed the libc would ignore NLSPATH when the app runs suid (similar
> like it does with LD_LIBRARY_PATH etc.). If it doesn''t that is a bad bug.
>
> [... clickety click ... ]
>
> At least glibc 2.1 uses __secure_getenv() for NLSPATH. Don''t know about 2.0,
> separate GNU gettext, or libc5.
I have
2024 Dec 20
1
PAM session setup and environment variables
On Fri, Dec 20, 2024 at 09:25:11AM +1100, Damien Miller wrote:
> On Thu, 19 Dec 2024, Dmitry V. Levin wrote:
>
> > > We could potentially allow-list some variables, but I'd like to get
> > > some input from people who (for example) maintain PAM for distributions
> > > on what is acceptable.
> >
> > With my Linux-PAM hat on, the most essential
2012 Dec 19
1
[PATCH] x86: also print CRn register values upon double fault
Do so by simply re-using _show_registers().
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/xen/arch/x86/x86_64/traps.c
+++ b/xen/arch/x86/x86_64/traps.c
@@ -225,6 +225,7 @@ void double_fault(void);
void do_double_fault(struct cpu_user_regs *regs)
{
unsigned int cpu;
+ unsigned long crs[8];
watchdog_disable();
@@ -235,22 +236,18 @@ void do_double_fault(struct
2024 Dec 19
1
PAM session setup and environment variables
On Thu, 19 Dec 2024, Dmitry V. Levin wrote:
> > We could potentially allow-list some variables, but I'd like to get
> > some input from people who (for example) maintain PAM for distributions
> > on what is acceptable.
>
> With my Linux-PAM hat on, the most essential difference between the
> authenticated user code that currently gets the environment variables
>
2014 Jul 19
1
[PATCH] don't always call setlocale() on Windows
Windows (MSVC, MinGW) version of setlocale don't care about LC_*
environment variables. For example, flac cannot pass the test for
--until and --skip options the script calls it with --skip=0:01.1001
and it expects decimal comma (--skip=0:01,1001) on my system.
One solution is to write a local version of strtod that always accepts
both decimal comma and decimal point.
Another solution is not
2014 Feb 27
1
R and LANGUAGE
Diverted from ESS-help.
It is really about R's LANGUAGE, locales and
then a wish for sessionInfo() :
>>>>> Sparapani, Rodney <rsparapa at mcw.edu>
>>>>> on Thu, 20 Feb 2014 19:39:33 +0000 writes:
>> Just guessing: perhaps this is something that is set when
>> R is initialized and not queried every time something is
>>
2012 Jun 28
4
[xen-unstable test] 13383: regressions - FAIL
flight 13383 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/13383/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pair 16 guest-start fail REGR. vs. 13379
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 12
2007 Feb 13
0
[Bug 1285] no way to override SendEnv directive in /etc/ssh/ssh_config
http://bugzilla.mindrot.org/show_bug.cgi?id=1285
Summary: no way to override SendEnv directive in
/etc/ssh/ssh_config
Product: Portable OpenSSH
Version: 4.2p1
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: bitbucket at
2012 Oct 02
3
[PATCH] VT-d: make remap_entry_to_msi_msg() return consistent message
During debugging of another problem I found that in x2APIC mode, the
destination field of the low address value wasn''t passed back
correctly. While this is benign in most cases (as the value isn''t being
used anywhere), it can be confusing (and misguiding) when printing the
value read or when comparing it to the one previously passed into the
inverse function.
Signed-off-by: Jan
2013 Jan 23
10
[PATCH 0/6] x86/HVM: miscellaneous RTC emulation adjustments
Finally I got around to breaking up the similarly named monolithic
patch that caused a regression shortly before the 4.2 release and
got therefore reverted. This series consists of the broken up
pieces that - according to my testing - don''t expose the reported
lockup; the 7th will need debugging to understand what''s wrong
there.
1: use RTC_* names instead of literal numbers
2:
2013 Mar 19
7
[PATCH 0/3] IOMMU errata treatment adjustments
1: IOMMU: properly check whether interrupt remapping is enabled
2: AMD IOMMU: only disable when certain IVRS consistency checks fail
3: VT-d: deal with 5500/5520/X58 errata
Patch 1 and 2 are version 2 of a previously submitted, then
withdrawn patch following up after XSA-36. Patch 3 is version 3 of
a patch previously sent by Malcolm and Andrew.
Signed-off-by: Jan Beulich
2012 Nov 02
4
[PATCH] ACPI/cpuidle: remove unused "power" field from Cx state data
It has never been used for anything, and Linux 3.7 doesn''t propagate
this information anymore.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
---
Konrad, on the pv-ops side it may be better to pass zero rather than
leaving the field completely uninitialized.
--- a/xen/arch/x86/acpi/cpu_idle.c
+++ b/xen/arch/x86/acpi/cpu_idle.c
@@ -935,7 +935,6 @@ static void set_cx(
}
2007 Sep 26
2
[Bridge] [PATCH] Module use count must be updated as bridges are created/destroyed
Otherwise 'modprobe -r' on a module having a dependency on bridge will
implicitly unload bridge, bringing down all connectivity that was using
bridges.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
net/bridge/br_if.c | 9 +++++++++
1 file changed, 9 insertions(+)
--- linux-2.6.23-rc8/net/bridge/br_if.c 2007-09-26 09:23:54.000000000 +0200
+++
2013 May 21
12
[PATCH] fix XSA-46 regression with xend/xm
The hypervisor side changes for XSA-46 require the tool stack to now
always map the guest pIRQ before granting access permission to the
underlying host IRQ (GSI). This in particular requires that pciif.py
no longer can skip this step (assuming qemu would do it) for HVM
guests.
This in turn exposes, however, an inconsistency between xend and qemu:
The former wants to always establish 1:1 mappings
2020 Feb 18
2
[PATCH] x86/ioperm: add new paravirt function update_io_bitmap
Commit 111e7b15cf10f6 ("x86/ioperm: Extend IOPL config to control
ioperm() as well") reworked the iopl syscall to use I/O bitmaps.
Unfortunately this broke Xen PV domains using that syscall as there
is currently no I/O bitmap support in PV domains.
Add I/O bitmap support via a new paravirt function update_io_bitmap
which Xen PV domains can use to update their I/O bitmaps via a
2020 Feb 18
2
[PATCH] x86/ioperm: add new paravirt function update_io_bitmap
Commit 111e7b15cf10f6 ("x86/ioperm: Extend IOPL config to control
ioperm() as well") reworked the iopl syscall to use I/O bitmaps.
Unfortunately this broke Xen PV domains using that syscall as there
is currently no I/O bitmap support in PV domains.
Add I/O bitmap support via a new paravirt function update_io_bitmap
which Xen PV domains can use to update their I/O bitmaps via a
2012 Sep 10
3
[PATCH] docs: document "ucode=" hypervisor command line option
Signed-off-by: Jan Beulich <jbeulich@suse.com>
--- a/docs/misc/xen-command-line.markdown
+++ b/docs/misc/xen-command-line.markdown
@@ -785,6 +785,19 @@ Specify the per-cpu trace buffer size in
> `= unstable | skewed`
### ucode
+> `= <integer>`
+
+Specify the CPU microcode update blob module index. When positive, this
+specifies the n-th module (in the GrUB entry, zero based)
2013 Aug 29
7
[PATCH 0/3] x86: mwait_idle improvements ported from Linux
1: x86/mwait_idle: remove assumption of one C-state per MWAIT flag
2: x86/mwait_idle: export both C1 and C1E
3: x86/mwait_idle: initial C8, C9, C10 support
Signed-off-by: Len Brown <len.brown@intel.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
2012 Nov 22
41
[PATCH V3] vmx/nmi: Do not use self_nmi() in VMEXIT handler
The self_nmi() code cause''s an NMI to be triggered by sending an APIC
message to the local processor. However, NMIs are blocked by the
VMEXIT, until the next iret or VMENTER.
Volume 3 Chapter 27 Section 1 of the Intel SDM states:
An NMI causes subsequent NMIs to be blocked, but only after the VM exit
completes.
As a result, as soon as the VMENTER happens, an immediate VMEXIT
happens