linux-kernel - [PATCH 0/7] x86: fix sparse warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun,  2 Sep 2012 23:31:39 +0200
From:	Mathias Krause <minipli@...glemail.com>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
Cc:	x86@...nel.org, linux-kernel@...r.kernel.org,
	Mathias Krause <minipli@...glemail.com>
Subject: [PATCH 0/7] x86: fix sparse warnings

This series fixes sparse warnings below arch/x86/ -- mostly address space
related, e.g. missing __user or __iomem annotations. Also minor C style
issues were fixed (duplicated const keyword; 0 instead of NULL).

All of these make spare complain less for code in arch/x86/.

Please apply!

Regards,

Mathias Krause (7):
  x86: fix __user annotations in asm/sys_ia32.h
  x86, vdso: add __user annotation to VDSO32_SYMBOL
  x86: ia32_signal.c: add __user casts to fix sparse warnings
  x86, probe_roms: add missing __iomem annotation to pci_map_biosrom()
  x86, xsave: keep __user annotation in casts
  x86, iommu: drop duplicate const in __IOMMU_INIT
  x86, iommu: use NULL instead of plain 0 for __IOMMU_INIT

 arch/x86/ia32/ia32_signal.c        |   11 ++++++-----
 arch/x86/ia32/sys_ia32.c           |    2 +-
 arch/x86/include/asm/iommu_table.h |    6 +++---
 arch/x86/include/asm/sys_ia32.h    |    2 +-
 arch/x86/include/asm/vdso.h        |    3 ++-
 arch/x86/kernel/probe_roms.c       |    2 +-
 arch/x86/kernel/xsave.c            |    6 +++---
 7 files changed, 17 insertions(+), 15 deletions(-)

-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/