similar to: Bug#812166: [PATCH] x86/mce: fix misleading indentation in init_nonfatal_mce_checker().

On 22/01/16 14:38, Ian Campbell wrote: > Debian bug 812166[0] reported this build failure due to > Wmisleading-indentation with gcc-6: > > non-fatal.c: In function 'init_nonfatal_mce_checker': > non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] > switch (c->x86_vendor) { > ^~~~~~ > >

Package: xen Version: 4.6.0-1 Severity: important User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in

On Wed, 2016-01-20 at 20:16 -0800, Martin Michlmayr wrote: > Package: xen > Version: 4.6.0-1 > Severity: important > User: debian-gcc at lists.debian.org > Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation > > This package fails to build with GCC 6.??GCC 6 has not been released > yet, but it's expected that GCC 6 will become the default compiler for > stretch. >

Dump mce log by ERST when mc panic We have implemented basic ERST logic before. Now linux3.0 as dom0 has included APEI logic. Hence it''s time to add mce apei interface and enable APEI ERST feature. With it, it can save mce log by ERST method when mc panic. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> diff -r ca2f58c2dfea xen/arch/x86/cpu/mcheck/mce.c ---

Currently number of error reporting register banks is hardcoded to 6 on AMD processors. This may break in virtualized scenarios when a hypervisor prefers to report fewer banks than what the physical HW provides. Since number of supported banks is reported in MSR_IA32_MCG_CAP[7:0] that''s what we should use. Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com> ---

Currently number of error reporting register banks is hardcoded to 6 on AMD processors. This may break in virtualized scenarios when a hypervisor prefers to report fewer banks that the physical HW provides. Since number of supported banks is reported in MSR_IA32_MCG_CAP[7:0] that''s what we should use. Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com> ---

commit cad172d7b88bd443c81d865051297875ce2551bc Author: Christoph Egger <chegger@amazon.de> Date: Thu Feb 7 14:42:29 2013 +0000 tools/libxl: fix compilation and link errors on NetBSD - Fix testidl link error that libyajl is not found - Make linking of xl and testidl consistent - fix error: array subscript has type ''char'' Signed-off-by:

Jan, This patch just used to stick all 1''s to MCi_CTL, it should not involve much argue, so I sent it separately. Thanks, Jinsong ==================== Xen/MCE: stick all 1''s to MCi_CTL of vMCE This patch is a middle-work patch, prepare for future new vMCE model. It remove mci_ctl array, and keep MCi_CTL all 1''s. Signed-off-by: Liu, Jinsong

Xen/MCE: vMCE injection In our test for win8 guest mce, we find a bug that no matter what SRAO/SRAR error xen inject to win8 guest, it always reboot. The root cause is, current Xen vMCE logic inject vMCE# only to vcpu0, this is not correct for Intel MCE (Under Intel arch, h/w generate MCE# to all CPUs). This patch fix vMCE injection bug, injecting vMCE# to all vcpus. Signed-off-by: Liu,

Processing commands for control at bugs.debian.org: > block 827061 with 828253 828367 828586 828309 828307 828513 812166 828412 828298 828277 Bug #827061 [release.debian.org] transition: openssl 827061 was blocked by: 828555 828359 828618 827076 828422 828459 828532 828330 828535 828313 828324 828547 828265 844311 835790 828533 828416 828394 828500 828255 828494 828395 828355 828443 828338

Boris, Here is the updated patch for determining number of regiter banks on AMD plus a patch removing shared_bank array, as you suggested. Offline/online testing didn''t show any issues. Boris Ostrovsky (2): x86/mce: Replace shared_bank array with is_shared_bank() helper x86/mce: Use MCG_CAP MSR to find out number of banks on AMD arch/x86/kernel/cpu/mcheck/mce_amd.c | 38

Hi, tools/misc/xencov.c fails to build. NetBSD does not have MAP_LOCKED. Christoph

tools/xenbackendd: properly cleanup Do not leave builds on gmake clean. Signed-off-by: Christoph Egger <chegger@amazon.de> diff --git a/tools/xenbackendd/Makefile b/tools/xenbackendd/Makefile index 8374ad3..31e5c62 100644 --- a/tools/xenbackendd/Makefile +++ b/tools/xenbackendd/Makefile @@ -30,7 +30,7 @@ install: build .PHONY: clean clean: - rm -f $(DEPS) + $(RM) *.a *.so *.o $(DEPS)

Please consider adding the following to the next R release (I understand that it's too late for R-2.1.0). It adds the menu item `Search R Site' in the `Help' menu in Rgui (which calls RSiteSearch() on the input string). Best, Andy --- R-beta/src/gnuwin32/rui.c 2005-03-06 09:41:40.000000000 -0500 +++ R-beta-new/src/gnuwin32/rui.c 2005-04-12 08:21:55.001824500 -0400 @@ -65,7 +65,8 @@

No, just no. You do not use goto to skip a code block. You do not return an obvious variable from a singly-inlined function and give the function a return value. You don't put unexplained comments about kmalloc in code which doesn't do dynamic allocation. And you don't leave stray warnings around for no good reason. Also, when possible, it is better to use block scoped variables

No, just no. You do not use goto to skip a code block. You do not return an obvious variable from a singly-inlined function and give the function a return value. You don't put unexplained comments about kmalloc in code which doesn't do dynamic allocation. And you don't leave stray warnings around for no good reason. Also, when possible, it is better to use block scoped variables

`memset(&mc_ext, 0, ...)'' leads to a buffer overflow and a subsequent null pointer dereference. Replace `&mc_ext'' with `mc_ext''. Signed-off-by: Xi Wang <xi@mit.edu> --- xen/arch/x86/cpu/mcheck/mce_intel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xen/arch/x86/cpu/mcheck/mce_intel.c b/xen/arch/x86/cpu/mcheck/mce_intel.c index

Hi, I was building LLVM with gcc 6.1.1 recently and it was spitting out some warnings relating to misleading indention that caught my eye. This wasn't a fresh build so I may have missed some. I've CC'ed the authors of the potentially misleading lines so they can decide what do about the warnings (if anything). I'm wondering if clang-format is making some inappropriate choices

I installed SeLinux in warn mode. HOw do i check to see what it is wanring about? This wil help me in make a decision to turn it to active mode..:) -- My "Foundation" verse: Isa 54:17 No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. This is the heritage of the servants of the LORD, and their

Heya All, Im having difficulties compiling rsync. when i run 'make' the build errors out on me. I run configure without any fancy options. The same goes for the make command. I have had this error, or a similar one since version 2.5.1 op to at least v2.5.5 I am using "-O3 -mcpu=i686 -march=i686" as additional compiler flags, however removing them does not make difference.