LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* linux-next: Tree for Aug 20
@ 2021-08-20  9:26 Stephen Rothwell
  2021-08-20 21:54 ` linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than) Randy Dunlap
  0 siblings, 1 reply; 13+ messages in thread
From: Stephen Rothwell @ 2021-08-20  9:26 UTC (permalink / raw)
  To: Linux Next Mailing List; +Cc: Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 38500 bytes --]

Hi all,

Changes since 20210819:

The net-next tree still had its build failure for which I applied a patch.

The drm tree gained a semantic conflict against the kbuild tree.

The ftrace tree gained a conflict against the jc_docs tree.

The drivers-x86 tree gained a build failure so I used the version from
next-20210819.

The driver-core tree gained a conflict against the pci-current tree.

Non-merge commits (relative to Linus' tree): 8514
 8252 files changed, 481311 insertions(+), 196532 deletions(-)

----------------------------------------------------------------------------

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig and htmldocs. And finally, a simple boot test
of the powerpc pseries_le_defconfig kernel in qemu (with and without
kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 334 trees (counting Linus' and 90 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (f87d64319e6f Merge tag 'net-5.14-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net)
Merging fixes/fixes (614124bea77e Linux 5.13-rc5)
Merging kbuild-current/fixes (36a21d51725a Linux 5.14-rc5)
Merging arc-current/for-curr (7c60610d4767 Linux 5.14-rc6)
Merging arm-current/fixes (463dbba4d189 ARM: 9104/2: Fix Keystone 2 kernel mapping regression)
Merging arm64-fixes/for-next/fixes (bde8fff82e4a arm64: initialize all of CNTHCTL_EL2)
Merging arm-soc-fixes/arm/fixes (1e16a4021120 Merge tag 'omap-for-v5.14/gpt12-fix-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into arm/fixes)
Merging drivers-memory-fixes/fixes (e73f0f0ee754 Linux 5.14-rc1)
Merging m68k-current/for-linus (21ed49265986 m68k: MAC should select HAVE_PATA_PLATFORM)
Merging powerpc-fixes/fixes (9f7853d7609d powerpc/mm: Fix set_memory_*() against concurrent accesses)
Merging s390-fixes/fixes (2a671f77ee49 s390/pci: fix use after free of zpci_dev)
Merging sparc/master (05a59d79793d Merge git://git.kernel.org:/pub/scm/linux/kernel/git/netdev/net)
Merging fscrypt-current/for-stable (d19d8d345eec fscrypt: fix inline encryption not used on new files)
Merging net/master (f87d64319e6f Merge tag 'net-5.14-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net)
Merging bpf/master (316749009fdf Merge https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf)
Merging ipsec/master (480e93e12aa0 net: xfrm: Fix end of loop tests for list_for_each_entry)
Merging netfilter/master (e3245a7b7b34 netfilter: nft_ct: protect nft_ct_pcpu_template_refcnt with mutex)
Merging ipvs/master (269fc69533de netfilter: nfnetlink_hook: translate inet ingress to netdev)
Merging wireless-drivers/master (abf3d98dee7c mt76: fix enum type mismatch)
Merging mac80211/master (0a298d133893 net: qlcnic: add missed unlock in qlcnic_83xx_flash_read32)
Merging rdma-fixes/for-rc (17f2569dce18 RDMA/bnxt_re: Add missing spin lock initialization)
Merging sound-current/for-linus (65ca89c2b12c ASoC: intel: atom: Fix breakage for PCM buffer address setup)
Merging sound-asoc-fixes/for-linus (70212c4c657f Merge remote-tracking branch 'asoc/for-5.14' into asoc-linus)
Merging regmap-fixes/for-linus (ff1176468d36 Linux 5.14-rc3)
Merging regulator-fixes/for-linus (3f00f451f6d1 Merge remote-tracking branch 'regulator/for-5.14' into regulator-linus)
Merging spi-fixes/for-linus (80b3a9808557 Merge remote-tracking branch 'spi/for-5.14' into spi-linus)
Merging pci-current/for-linus (045a9277b561 PCI/sysfs: Use correct variable for the legacy_mem sysfs object)
Merging driver-core.current/driver-core-linus (36a21d51725a Linux 5.14-rc5)
Merging tty.current/tty-linus (36a21d51725a Linux 5.14-rc5)
Merging usb.current/usb-linus (5571ea3117ca usb: typec: tcpm: Fix VDMs sometimes not being forwarded to alt-mode drivers)
Merging usb-gadget-fixes/fixes (e49d033bddf5 Linux 5.12-rc6)
Merging usb-serial-fixes/usb-linus (8da0e55c7988 USB: serial: ftdi_sio: add device ID for Auto-M3 OP-COM v2)
Merging usb-chipidea-fixes/for-usb-fixes (5df09c15bab9 usb: cdnsp: Fix the IMAN_IE_SET and IMAN_IE_CLEAR macro)
Merging phy/fixes (e73f0f0ee754 Linux 5.14-rc1)
Merging staging.current/staging-linus (7c60610d4767 Linux 5.14-rc6)
Merging iio-fixes/fixes-togreg (a5056c0bc24f Merge tag 'iio-fixes-5.14a' of https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-linus)
Merging char-misc.current/char-misc-linus (d30836a95289 Merge tag 'icc-5.14-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc into char-misc-linus)
Merging soundwire-fixes/fixes (e73f0f0ee754 Linux 5.14-rc1)
Merging thunderbolt-fixes/fixes (7c60610d4767 Linux 5.14-rc6)
Merging input-current/for-linus (818b26588994 Merge branch 'next' into for-linus)
Merging crypto-current/master (5261cdf457ce crypto: drbg - select SHA512)
Merging vfio-fixes/for-linus (dc51ff91cf2d vfio/platform: fix module_put call in error flow)
Merging kselftest-fixes/fixes (567c39047dbe selftests/sgx: Fix Q1 and Q2 calculation in sigstruct.c)
Merging modules-fixes/modules-linus (055f23b74b20 module: check for exit sections in layout_sections() instead of module_init_section())
Merging dmaengine-fixes/fixes (7199ddede9f0 dmaengine: imx-dma: configure the generic DMA type to make it work)
Merging backlight-fixes/for-backlight-fixes (a38fd8748464 Linux 5.12-rc2)
Merging mtd-fixes/mtd/fixes (b48027083a78 mtd: rawnand: Fix probe failure due to of_get_nand_secure_regions())
Merging mfd-fixes/for-mfd-fixes (a61f4661fba4 mfd: intel_quark_i2c_gpio: Revert "Constify static struct resources")
Merging v4l-dvb-fixes/fixes (f1de1c780359 media: atmel: fix build when ISC=m and XISC=y)
Merging reset-fixes/reset/fixes (1435f82689e1 reset: RESET_MCHP_SPARX5 should depend on ARCH_SPARX5)
Merging mips-fixes/mips-fixes (6aa32467299e MIPS: check return value of pgtable_pmd_page_ctor)
Merging at91-fixes/at91-fixes (6efb943b8616 Linux 5.13-rc1)
Merging omap-fixes/fixes (e879f855e590 bus: ti-sysc: Add break in switch statement in sysc_init_soc())
Merging kvm-fixes/master (c7dfa4009965 KVM: nSVM: always intercept VMLOAD/VMSAVE when nested (CVE-2021-3656))
Merging kvms390-fixes/master (cd4220d23bf3 KVM: selftests: do not require 64GB in set_memory_region_test)
Merging hwmon-fixes/hwmon (03726fd90f4b hwmon: sht4x: update Documentation for Malformed table)
Merging nvdimm-fixes/libnvdimm-fixes (96dcb97d0a40 Merge branch 'for-5.14/dax' into libnvdimm-fixes)
Merging cxl-fixes/fixes (fae8817ae804 cxl/mem: Fix memory device capacity probing)
Merging btrfs-fixes/next-fixes (01e9fcf19c13 Merge branch 'misc-5.14' into next-fixes)
Merging vfs-fixes/fixes (173e84953eaa fs: fix reporting supported extra file attributes for statx())
Merging dma-mapping-fixes/for-linus (18a3c5f7abfd Merge tag 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost)
Merging i3c-fixes/i3c/fixes (fe07bfda2fb9 Linux 5.12-rc1)
Merging drivers-x86-fixes/fixes (1e35b8a7780a platform/x86: gigabyte-wmi: add support for B450M S2H V2)
Merging samsung-krzk-fixes/fixes (e73f0f0ee754 Linux 5.14-rc1)
Merging pinctrl-samsung-fixes/fixes (e73f0f0ee754 Linux 5.14-rc1)
Merging devicetree-fixes/dt/linus (50d8d7e19c43 dt-bindings: display: renesas,du: Make resets optional on R-Car H1)
Merging scsi-fixes/fixes (40d32727931c scsi: mpt3sas: Fix incorrectly assigned error return and check)
Merging drm-fixes/drm-fixes (7c60610d4767 Linux 5.14-rc6)
Merging amdgpu-fixes/drm-fixes (2c409ba81be2 drm/radeon: fix si_enable_smc_cac() failed issue)
Merging drm-intel-fixes/for-linux-next-fixes (e3e86f41385b drm/i915/dp: remove superfluous EXPORT_SYMBOL())
Merging mmc-fixes/fixes (419dd626e357 mmc: sdhci-iproc: Set SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN on BCM2711)
Merging rtc-fixes/rtc-fixes (bd33335aa93d rtc: cmos: Disable irq around direct invocation of cmos_interrupt())
Merging gnss-fixes/gnss-linus (e73f0f0ee754 Linux 5.14-rc1)
Merging hyperv-fixes/hyperv-fixes (f5a11c69b699 Revert "x86/hyperv: fix logical processor creation")
Merging soc-fsl-fixes/fix (c1e64c0aec8c soc: fsl: qe: fix static checker warning)
Merging risc-v-fixes/fixes (fdf3a7a1e0a6 riscv: Fix comment regarding kernel mapping overlapping with IS_ERR_VALUE)
Merging pidfd-fixes/fixes (03ba0fe4d09f file: simplify logic in __close_range())
Merging fpga-fixes/fixes (1d345c3e5941 fpga: machxo2-spi: Fix missing error code in machxo2_write_complete())
Merging spdx/spdx-linus (36a21d51725a Linux 5.14-rc5)
Merging gpio-brgl-fixes/gpio/for-current (9b87f43537ac gpio: tqmx86: really make IRQ optional)
Merging gpio-intel-fixes/fixes (e73f0f0ee754 Linux 5.14-rc1)
Merging pinctrl-intel-fixes/fixes (2f658f7a3953 pinctrl: tigerlake: Fix GPIO mapping for newer version of software)
Merging erofs-fixes/fixes (0852b6ca941e erofs: fix 1 lcluster-sized pcluster for big pcluster)
Merging integrity-fixes/fixes (843385694721 evm: Fix a small race in init_desc())
Merging kunit-fixes/kunit-fixes (2734d6c1b1a0 Linux 5.14-rc2)
Merging ubifs-fixes/fixes (78c7d49f55d8 ubifs: journal: Make sure to not dirty twice for auth nodes)
Merging memblock-fixes/fixes (024591f9a6e0 arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM)
Merging cel-fixes/for-rc (9f4ad9e425a1 Linux 5.12)
Merging irqchip-fixes/irq/irqchip-fixes (1fee9db9b42d irqchip/mips: Fix RCU violation when using irqdomain lookup on interrupt entry)
Merging renesas-fixes/fixes (432b52eea3dc ARM: shmobile: defconfig: Restore graphical consoles)
Merging drm-misc-fixes/for-linux-next-fixes (fa0b1ef5f7a6 drm: Copy drm_wait_vblank to user before returning)
Merging kspp-gustavo/for-next/kspp (7bc04ce6b914 Makefile: Enable -Wimplicit-fallthrough for Clang)
Merging kbuild/for-next (fb3fdea45030 kbuild: Fix 'no symbols' warning when CONFIG_TRIM_UNUSD_KSYMS=y)
Merging compiler-attributes/compiler-attributes (7ed012969bbc Compiler Attributes: fix __has_attribute(__no_sanitize_coverage__) for GCC 4)
CONFLICT (content): Merge conflict in include/linux/compiler_attributes.h
Merging dma-mapping/for-next (c1dec343d7ab hexagon: use the generic global coherent pool)
Merging asm-generic/master (8f76f9c46952 bitops/non-atomic: make @nr unsigned to avoid any DIV)
Merging arc/for-next (28bfbfd7a713 ARC: mm: move MMU specific bits out of entry code ...)
Merging arm/for-next (3e9a47a71364 Merge branches 'fixes' and 'misc' into for-next)
Merging arm64/for-next/core (92b5529ab76e Merge branch 'for-next/entry' into for-next/core)
Merging arm-perf/for-next/perf (fd264b310579 arm64/perf: Replace '0xf' instances with ID_AA64DFR0_PMUVER_IMP_DEF)
Merging arm-soc/for-next (4364229fd558 soc: document merges)
Merging actions/for-next (444d018d8d38 ARM: dts: owl-s500-roseapplepi: Add ATC2603C PMIC)
Merging amlogic/for-next (6285af2a2821 Merge tags 'amlogic-arm-configs-for-v5.15', 'amlogic-arm64-dt-for-v5.15' and 'amlogic-arm-dt-for-v5.15' into for-next)
Merging aspeed/for-next (0f32f00af344 Merge branches 'dt-for-v5.15', 'soc-for-v5.15' and 'defconfig-for-v5.15' into for-next)
Merging at91/at91-next (b102356e5bc1 Merge branch 'at91-dt' into at91-next)
Merging drivers-memory/for-next (c28b584deb1b Merge branch 'for-v5.15/omap-gpmc' into for-next)
Merging imx-mxs/for-next (2cb411d89676 Merge branch 'imx/defconfig' into for-next)
Merging keystone/next (cb293d3b430e Merge branch 'for_5.15/drivers-soc' into next)
Merging mediatek/for-next (69862ae4e378 Merge branch 'v5.14-next/soc' into for-next)
Merging mvebu/for-next (930af8dda750 Merge branch 'mvebu/dt64' into mvebu/for-next)
Merging omap/for-next (7911f95d1713 Merge branch 'fixes' into for-next)
Merging qcom/for-next (57249830120b Merge remote-tracking branch 'refs/remotes/origin/for-next' into for-next)
Merging raspberrypi/for-next (b1f2fcb28228 ARM: dts: bcm283x: Fix VEC address for BCM2711)
Merging renesas/next (59d7f78144a8 Merge branches 'renesas-arm-dt-for-v5.15' and 'renesas-drivers-for-v5.15' into renesas-next)
Merging reset/reset/next (bee08559701f reset: renesas: Add RZ/G2L usbphy control driver)
Merging rockchip/for-next (abfe14de9197 Merge branch 'v5.15-armsoc/drivers' into for-next)
Merging samsung-krzk/for-next (90861bf54255 Merge branch 'next/dt64' into for-next)
Merging scmi/for-linux-next (7c414a7d93c6 Merge branch 'for-next/scmi' of git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux into for-linux-next)
Merging stm32/stm32-next (1e6bc5987a52 ARM: dts: stm32: Update AV96 adv7513 node per dtbs_check)
Merging sunxi/sunxi/for-next (3f1c53207cf0 Merge branches 'sunxi/dt-for-5.14' and 'sunxi/fixes-for-5.13' into sunxi/for-next)
Merging tegra/for-next (cc701ccede61 Merge branch for-5.15/arm64/dt into for-next)
Merging ti-k3/ti-k3-next (1e3d655fe7b4 Merge branch 'ti-k3-config-next' into ti-k3-next)
Merging ti-k3-new/ti-k3-next (c1fa5ac6c2f4 arm64: dts: ti: k3-am642-sk: Add pwm nodes)
Merging xilinx/for-next (4cddd9be7ef6 Merge branch 'zynq/soc' of https://github.com/Xilinx/linux-xlnx into for-next)
Merging clk/clk-next (765f4fa0e9f1 Merge branch 'clk-qcom' into clk-next)
Merging clk-imx/for-next (fb3f4bca19b3 clk: imx: clk-divider-gate: Switch to clk_divider.determine_rate)
Merging clk-renesas/renesas-clk (e8425dd55abb clk: renesas: Make CLK_R9A06G032 invisible)
Merging clk-samsung/for-next (a38fd8748464 Linux 5.12-rc2)
Merging csky/linux-next (90dc8c0e664e csky: Kconfig: Remove unused selects)
Merging h8300/h8300-next (1ec10274d436 h8300: don't implement set_fs)
Merging m68k/for-next (2189e928b62e m68k: Fix invalid RMW_INSNS on CPUs that lack CAS)
Merging m68knommu/for-next (07c4e80124d1 m68knommu: only set CONFIG_ISA_DMA_API for ColdFire sub-arch)
Merging microblaze/next (14a832498c23 arch: microblaze: Fix spelling mistake "vesion" -> "version")
Merging mips/mips-next (4d2ee1be4c2a MIPS: generic: Return true/false (not 1/0) from bool functions)
Merging nds32/next (40e0dd851e7b nds32: Fix bogus reference to <asm/procinfo.h>)
Merging nios2/for-next (7f7bc20bc41a nios2: Don't use _end for calculating min_low_pfn)
Merging openrisc/for-next (94effcedaa54 openrisc: Fix compiler warnings in setup)
Merging parisc-hd/for-next (ca2b19a4bdb6 parisc: Increase gcc stack frame check to 2048 for 32- and 64-bit)
Merging powerpc/next (8b893ef190b0 powerpc/pseries: Fix build error when NUMA=n)
CONFLICT (content): Merge conflict in arch/powerpc/sysdev/xive/common.c
Merging soc-fsl/next (242b0b398ccd soc: fsl: enable acpi support in RCPM driver)
Merging risc-v/for-next (8ba1a8b77ba1 riscv: Support allocating gigantic hugepages using CMA)
Merging s390/for-next (54157006715d Merge branch 'features' into for-next)
Merging sh/for-next (2882b7626f49 sh: kernel: traps: remove unused variable)
Merging sparc-next/master (dd0d718152e4 Merge tag 'spi-fix-v5.8-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi)
Merging uml/linux-next (1aee020155f3 um: remove unneeded semicolon in um_arch.c)
Merging xtensa/xtensa-for-next (7b7cec477fc3 xtensa: move core-y in arch/xtensa/Makefile to arch/xtensa/Kbuild)
Merging pidfd/for-next (f4dd02cd8631 Merge branch 'kernel.sys' into for-next)
Merging fscrypt/master (38ef66b05cfa fscrypt: document struct fscrypt_operations)
Merging fscache/fscache-next (5193f26aef59 fscache: Use refcount_t for the cookie refcount instead of atomic_t)
Merging afs/afs-next (7af08140979a Revert "gcov: clang: fix clang-11+ build")
Merging btrfs/for-next (b61bdbb49be3 Merge branch 'for-next-next-v5.14-20210817' into for-next-20210817)
Merging ceph/master (8434ffe71c87 ceph: take snap_empty_lock atomically with snaprealm refcount change)
Merging cifs/for-next (1c2809b3d6e6 cifs: fix wrong release in sess_alloc_buffer() failed path)
Merging cifsd/cifsd-for-next (bdbb7400523b Merge pull request #65 from namjaejeon/cifsd-for-next)
Merging configfs/for-next (769f52676756 configfs: restore the kernel v5.13 text attribute write behavior)
Merging ecryptfs/next (682a8e2b41ef Merge tag 'ecryptfs-5.13-rc1-updates' of git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs)
Merging erofs/dev (eadcd6b5a1eb erofs: add fiemap support with iomap)
Merging exfat/dev (50be9417e23a Merge tag 'io_uring-5.14-2021-07-09' of git://git.kernel.dk/linux-block)
Merging ext3/for_next (a95dc17633ab Pull utf8 handling fixes from Pali Rohar)
Merging ext4/dev (6c6ce4d71465 jbd2: add sparse annotations for add_transaction_credits())
Merging f2fs/dev (bbe1da7e34ac f2fs: compress: do sanity check on cluster)
Applying: fxup for "f2fs: Convert to using invalidate_lock"
Merging fsverity/fsverity (07c99001312c fs-verity: support reading signature with ioctl)
Merging fuse/for-next (76224355db75 fuse: truncate pagecache on atomic_o_trunc)
Merging gfs2/for-next (98fd6514d37b gfs2: Remove redundant check from gfs2_glock_dq)
Merging jfs/jfs-next (5d299f44d765 jfs: Avoid field-overflowing memcpy())
Merging nfs/linux-next (2734d6c1b1a0 Linux 5.14-rc2)
Merging nfs-anna/linux-next (ca7d1d1a0b97 NFSv4.2: remove restriction of copy size for inter-server copy.)
Merging nfsd/nfsd-next (ab1016d39cc0 nfsd: fix NULL dereference in nfs3svc_encode_getaclres)
Merging cel/for-next (729580ddc53e svcrdma: xpt_bc_xprt is already clear in __svc_rdma_free())
Merging ntfs3/master (96b18047a717 fs/ntfs3: Add MAINTAINERS)
Merging orangefs/for-next (0fdec1b3c9fb orangefs: fix orangefs df output.)
Merging overlayfs/overlayfs-next (332f606b32b6 ovl: enable RCU'd ->get_acl())
Applying: ntfs3: fix up for "vfs: add rcu argument to ->get_acl() callback"
Merging ubifs/next (a801fcfeef96 ubifs: Set/Clear I_LINKABLE under i_lock for whiteout inode)
Merging v9fs/9p-next (732b33d0dbf1 9p/xen: Fix end of loop tests for list_for_each_entry)
Merging xfs/for-next (a437b9b488e3 xfs: remove support for untagged lookups in xfs_icwalk*)
Merging zonefs/for-next (95b115332a83 zonefs: remove redundant null bio check)
Merging iomap/iomap-for-next (742dd4b8c5bb mm/swap: consider max pages in iomap_swapfile_add_extent)
Merging djw-vfs/vfs-for-next (d03ef4daf33a fs: forbid invalid project ID)
Merging file-locks/locks-next (e1cc6e8c1969 fcntl: fix potential deadlock for &fasync_struct.fa_lock)
Merging vfs/for-next (d75b9fa053e4 gfs2: Switch to may_setattr in gfs2_setattr)
Merging printk/for-next (23d8adcf8022 Merge branch 'rework/printk_safe-removal' into for-next)
Merging pci/next (7fc74df20a87 Merge branch 'remotes/lorenzo/pci/tools')
Merging pstore/for-next/pstore (c5d4fb2539ca pstore/blk: Use "%lu" to format unsigned long)
Merging hid/for-next (e2e4893180f3 Merge branch 'for-5.14/upstream-fixes' into for-next)
Merging i2c/i2c/for-next (ec1127b4dd61 Merge branch 'i2c/for-mergewindow' into i2c/for-next)
CONFLICT (content): Merge conflict in include/uapi/linux/virtio_ids.h
Merging i3c/i3c/next (e73f0f0ee754 Linux 5.14-rc1)
Merging dmi/dmi-for-next (3cb4d29a2633 MAINTAINERS: The DMI/SMBIOS tree has moved)
Merging hwmon-staging/hwmon-next (b51f752c586c hwmon: (dell-smm) Rework SMM function debugging)
Merging jc_docs/docs-next (37397b092e7f docs: sphinx-requirements: Move sphinx_rtd_theme to top)
Merging v4l-dvb/master (9c3a0f285248 Merge tag 'v5.14-rc4' into media_tree)
Merging v4l-dvb-next/master (19e95228c722 media: netup_unidvb: handle interrupt properly according to the firmware)
Merging pm/linux-next (10bc7fbefe3a Merge branch 'pm-cpufreq-fixes' into linux-next)
Merging cpufreq-arm/cpufreq/arm/linux-next (86afc1df661a cpufreq: qcom-cpufreq-hw: Add dcvs interrupt support)
Merging cpupower/cpupower (5499f2b80b56 tools: cpupower: fix typo in cpupower-idle-set(1) manpage)
Merging devfreq/devfreq-next (e73f0f0ee754 Linux 5.14-rc1)
Merging opp/opp/linux-next (e122d7edf1a2 dt-bindings: opp: Convert to DT schema)
Merging thermal/thermal/linux-next (0284b52e8534 dt-bindings: thermal: Add dt binding for QCOM LMh)
Merging ieee1394/for-next (54b3bd99f094 firewire: nosy: switch from 'pci_' to 'dma_' API)
Merging dlm/next (aee742c9928a fs: dlm: fix return -EINTR on recovery stopped)
Merging swiotlb/linux-next (a449ffaf9181 powerpc/svm: Don't issue ultracalls if !mem_encrypt_active())
CONFLICT (content): Merge conflict in kernel/dma/direct.c
Merging rdma/for-next (d2b10794fc13 RDMA/core: Create clean QP creations interface for uverbs)
Merging net-next/master (9e5f10fe577b octeontx2-af: remove redudant second error check on variable err)
CONFLICT (content): Merge conflict in drivers/ptp/Kconfig
Applying: NET_VENDOR_CIRRUS is not ready for COMPILE_TEST
Merging bpf-next/for-next (f2a6ee924d26 selftests/bpf: Add tests for {set|get} socket option from setsockopt BPF)
Merging ipsec-next/master (5d8dbb7fb82b net: xfrm: fix shift-out-of-bounce)
Merging mlx5-next/mlx5-next (598fe77df855 net/mlx5: Lag, Create shared FDB when in switchdev mode)
Merging netfilter-next/master (6f45933dfed0 Merge git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next)
Merging ipvs-next/master (9344988d2979 netfilter: ctnetlink: allow to filter dump by status bits)
Merging wireless-drivers-next/master (d249ff28b1d8 intersil: remove obsolete prism54 wireless driver)
CONFLICT (content): Merge conflict in MAINTAINERS
Merging bluetooth/master (61969ef867d4 Bluetooth: Fix return value in hci_dev_do_close())
CONFLICT (content): Merge conflict in net/bluetooth/hci_sysfs.c
CONFLICT (content): Merge conflict in net/bluetooth/hci_core.c
CONFLICT (content): Merge conflict in include/net/bluetooth/hci_core.h
Merging mac80211-next/master (c448f0fd2ce5 cfg80211: fix BSS color notify trace enum confusion)
Merging mtd/mtd/next (a89d69a44e28 mtd: mtdconcat: Check _read, _write callbacks existence before assignment)
Merging nand/nand/next (0792ec82175e mtd: rawnand: intel: Fix error handling in probe)
Merging spi-nor/spi-nor/next (2734d6c1b1a0 Linux 5.14-rc2)
Merging crypto/master (9491923e4a68 crypto: wp512 - correct a non-kernel-doc comment)
Merging drm/drm-next (397ab98e2d69 Merge tag 'drm-msm-next-2021-08-12' of https://gitlab.freedesktop.org/drm/msm into drm-next)
CONFLICT (content): Merge conflict in drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
CONFLICT (content): Merge conflict in drivers/gpu/drm/msm/dp/dp_display.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_device_info.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/i915_pci.c
CONFLICT (modify/delete): drivers/gpu/drm/i915/i915_globals.c deleted in drm/drm-next and modified in HEAD. Version HEAD of drivers/gpu/drm/i915/i915_globals.c left in tree.
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/display/intel_display.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/amd/amdgpu/amdgpu_ras_eeprom.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
CONFLICT (content): Merge conflict in drivers/firmware/Makefile
$ git rm -f drivers/gpu/drm/i915/i915_globals.c
Merging drm-misc/for-linux-next (d03a493f6782 drm/mgag200: Fix uninitialized variable delta)
Merging amdgpu/drm-next (06a631a08050 drm/radeon: Add HD-audio component notifier support (v2))
Merging drm-intel/for-linux-next (c00e14cd4d3f drm/i915/adl_p: Also disable underrun recovery with MSO)
Merging drm-tegra/drm/tegra/for-next (fed028939417 gpu: host1x: debug: Dump DMASTART and DMAEND register)
Merging drm-msm/msm-next (cb0927ab80d2 drm/msi/mdp4: populate priv->kms in mdp4_kms_init)
Merging imx-drm/imx-drm/next (59e4e762a17d gpu: ipu-v3: Fix i.MX IPU-v3 offset calculations for (semi)planar U/V formats)
Merging etnaviv/etnaviv/next (81fd23e2b3cc drm/etnaviv: Implement mmap as GEM object function)
Applying: drm/i915: use linux/stddef.h due to "isystem: trim/fixup stdarg.h and other headers"
Merging regmap/for-next (cc15156265f0 Merge remote-tracking branch 'regmap/for-5.15' into regmap-next)
Merging sound/for-next (d2d837563743 ALSA: hda/analog - Sink ad198x_shutup() and shuffle CONFIG_PM guards)
Merging sound-asoc/for-next (dc392f00eb58 Merge remote-tracking branch 'asoc/for-5.15' into asoc-next)
Merging modules/modules-next (ced75a2f5da7 MAINTAINERS: Add Luis Chamberlain as modules maintainer)
Merging input/next (76ba1900cb67 dt-bindings: power: reset: qcom-pon: Convert qcom PON binding to yaml)
Merging block/for-next (39916d4054e7 Merge branch 'for-5.15/io_uring' into for-next)
CONFLICT (modify/delete): block/mq-deadline-cgroup.c deleted in HEAD and modified in block/for-next. Version block/for-next of block/mq-deadline-cgroup.c left in tree.
$ git rm -f block/mq-deadline-cgroup.c
Merging device-mapper/for-next (528b16bfc3ae dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc())
Merging pcmcia/pcmcia-next (e39cdacf2f66 pcmcia: i82092: fix a null pointer dereference bug)
Merging mmc/next (7d6fab2c3ea8 mmc: renesas_sdhi: Refactor renesas_sdhi_probe())
Merging mfd/for-mfd-next (be722576fd63 dt-bindings: mfd: Add Broadcom CRU)
Merging backlight/for-backlight-next (79fad92f2e59 backlight: pwm_bl: Improve bootloader/kernel device handover)
Merging battery/for-next (eaa2c490514d power: supply: max17042_battery: log SOC threshold using debug log level)
Merging regulator/for-next (aa9f92097dcc Merge remote-tracking branch 'regulator/for-5.15' into regulator-next)
Merging security/next-testing (047843bdb316 Merge branch 'landlock_lsm_v34' into next-testing)
Merging apparmor/apparmor-next (d108370c644b apparmor: fix error check)
Merging integrity/next-integrity (d07eeeb87459 Merge branch 'restrict-digest-alg-v8' into next-integrity)
Applying: dm ima: fix for "ima: Add digest and digest_len params to the functions to measure a buffer"
Merging keys/keys-next (e377c31f788f integrity: Load mokx variables into the blacklist keyring)
CONFLICT (content): Merge conflict in certs/system_keyring.c
Merging safesetid/safesetid-next (1b8b71922919 LSM: SafeSetID: Mark safesetid_initialized as __initdata)
Merging selinux/next (893c47d1964f selinux: return early for possible NULL audit buffers)
Merging smack/next (bfc3cac0c761 smack: mark 'smack_enabled' global variable as __initdata)
Merging tomoyo/master (ff1176468d36 Linux 5.14-rc3)
Merging tpmdd/next (ada16d6b0f0a tpm: ibmvtpm: Avoid error message when process gets signal while waiting)
Merging watchdog/master (cf813c67d961 watchdog: iTCO_wdt: use dev_err() instead of pr_err())
Merging iommu/next (cf1f65a86d45 Merge branches 'apple/dart', 'arm/smmu', 'iommu/fixes', 'x86/amd' and 'x86/vt-d' into next)
Merging audit/next (d97e99386ad0 audit: add header protection to kernel/audit.h)
Merging devicetree/for-next (ec6c6c9c1386 dt-bindings: eeprom-93xx46: Convert to json schema)
CONFLICT (modify/delete): Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt deleted in devicetree/for-next and modified in HEAD. Version HEAD of Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt left in tree.
$ git rm -f Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.txt
Applying: dt-bindings: arm: mediatek: mmsys: fixup for conversion to yaml
Merging mailbox/mailbox-for-next (4f197188da66 MAINTAINERS: add entry for polarfire soc mailbox)
Merging spi/for-next (5d14499b5016 Merge remote-tracking branch 'spi/for-5.15' into spi-next)
Merging tip/auto-latest (a27fdfde0570 Merge branch 'locking/core')
CONFLICT (content): Merge conflict in include/asm-generic/bitops/non-atomic.h
Merging clockevents/timers/drivers/next (631c7c0df0ef dt-bindings: timer: Add ABIs for new Ingenic SoCs)
Merging edac/edac-for-next (7d07deb3b838 EDAC/altera: Skip defining unused structures for specific configs)
Merging irqchip/irq/irqchip-next (cf39e60c83f1 Merge branch irq/generic_handle_domain_irq into irq/irqchip-next)
Merging ftrace/for-next (db396be6ddc4 MAINTAINERS: Add an entry for os noise/latency)
CONFLICT (content): Merge conflict in MAINTAINERS
Merging rcu/rcu/next (213605c149ff kcsan: selftest: Cleanup and add missing __init)
CONFLICT (content): Merge conflict in kernel/time/tick-internal.h
Merging kvm/next (5a4bfabcc865 KVM: SVM: Add 5-level page table support for SVM)
Merging kvm-arm/next (f2267b87ecd5 Merge branch kvm-arm64/misc-5.15 into kvmarm-master/next)
CONFLICT (content): Merge conflict in arch/arm64/include/asm/sysreg.h
Merging kvm-ppc/kvm-ppc-next (72476aaa4691 KVM: PPC: Book3S HV: Fix host radix SLB optimisation with hash guests)
Merging kvms390/next (1f703d2cf204 KVM: s390: allow facility 192 (vector-packed-decimal-enhancement facility 2))
Merging xen-tip/linux-next (88ca2521bd5b xen/events: Fix race in set_evtchn_to_irq)
Merging percpu/for-next (a81a52b325ec Merge branch 'for-5.14-fixes' into for-next)
Merging workqueues/for-next (bdb0a6548d22 workqueue: Remove unused WORK_NO_COLOR)
Merging drivers-x86/for-next (c58259bc83a2 asus-wmi: Add support for platform_profile)
$ git reset --hard HEAD^
Merging next-20210819 version of drivers-x86
Merging chrome-platform/for-next (e73f0f0ee754 Linux 5.14-rc1)
Merging hsi/for-next (e73f0f0ee754 Linux 5.14-rc1)
Merging leds/for-next (3d3d65bd2764 leds: pwm: add support for default-state device property)
Merging ipmi/for-next (bf064c7bec3b char: ipmi: use DEVICE_ATTR helper macro)
Merging driver-core/driver-core-next (bd1e336aa853 driver core: platform: Remove platform_device_add_properties())
CONFLICT (content): Merge conflict in drivers/pci/pci-sysfs.c
Merging usb/usb-next (e4788edc730a USB: EHCI: Add alias for Broadcom INSNREG)
CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/sc7280.dtsi
CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/sc7280-idp.dts
Merging usb-gadget/next (e49d033bddf5 Linux 5.12-rc6)
Merging usb-serial/usb-next (4e9340bb551a USB: serial: cp210x: determine fw version for CP2105 and CP2108)
Merging usb-chipidea-next/for-usb-next (956df1bb0ab8 usb: chipidea: host: fix port index underflow and UBSAN complains)
Merging tty/tty-next (88c1d2478ec8 tty: serial: fsl_lpuart: check dma_tx_in_progress in tx dma callback)
Merging char-misc/char-misc-next (b2159182dd49 lkdtm: remove IDE_CORE_CP crashpoint)
Merging extcon/extcon-next (07de34f5ce1e extcon: max3355: Drop unused include)
Merging phy-next/next (34633219b894 phy: qmp: Provide unique clock names for DP clocks)
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/phy/qcom,qmp-usb3-dp-phy.yaml
Merging soundwire/next (dd81e7c3f0bb soundwire: cadence: override PDI configurations to create loopback)
Merging thunderbolt/next (42716425ad7e thunderbolt: Fix port linking by checking all adapters)
Merging vfio/next (eb24c1007e68 vfio: Remove struct vfio_device_ops open/release)
Merging staging/staging-next (093991aaadf0 staging: r8188eu: Remove empty rtw_mfree_xmit_priv_lock())
CONFLICT (modify/delete): drivers/staging/rtl8188eu/os_dep/os_intfs.c deleted in staging/staging-next and modified in HEAD. Version HEAD of drivers/staging/rtl8188eu/os_dep/os_intfs.c left in tree.
CONFLICT (modify/delete): drivers/staging/rtl8188eu/os_dep/ioctl_linux.c deleted in staging/staging-next and modified in HEAD. Version HEAD of drivers/staging/rtl8188eu/os_dep/ioctl_linux.c left in tree.
CONFLICT (modify/delete): drivers/staging/rtl8188eu/include/osdep_intf.h deleted in staging/staging-next and modified in HEAD. Version HEAD of drivers/staging/rtl8188eu/include/osdep_intf.h left in tree.
CONFLICT (content): Merge conflict in drivers/staging/r8188eu/os_dep/rtw_android.c
CONFLICT (content): Merge conflict in drivers/staging/r8188eu/include/rtw_android.h
CONFLICT (content): Merge conflict in drivers/misc/Kconfig
$ git rm -f drivers/staging/rtl8188eu/include/osdep_intf.h drivers/staging/rtl8188eu/os_dep/ioctl_linux.c drivers/staging/rtl8188eu/os_dep/os_intfs.c
Merging iio/togreg (d484c21bacfa iio: adc: Add driver for Renesas RZ/G2L A/D converter)
Merging mux/for-next (3516bd729358 Merge tag 's390-5.11-3' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux)
Merging icc/icc-next (8bf5d31c4f06 interconnect: qcom: osm-l3: Use driver-specific naming)
Merging dmaengine/next (9760383b22ed Merge tag 'v5.14-rc5' into next)
Merging cgroup/for-next (c5b6c8a56ef3 Merge branch 'for-5.15' into for-next)
Merging scsi/for-next (52e22d4d4e37 Merge branch 'misc' into for-next)
Merging scsi-mkp/for-next (848ade90ba9c scsi: sd: Do not exit sd_spinup_disk() quietly)
Merging vhost/linux-next (879753c816db vdpa/mlx5: Fix queue type selection logic)
Merging rpmsg/for-next (c93ca5f21d93 Merge branches 'hwspinlock-next', 'rpmsg-next' and 'rproc-next' into for-next)
Merging gpio/for-next (7ac554888233 MAINTAINERS: Remove reference to non-existing file)
Merging gpio-brgl/gpio/for-next (d0ef631d40ba gpio: mlxbf2: Use DEFINE_RES_MEM_NAMED() helper macro)
Merging gpio-intel/for-next (5111c2b6b019 gpio: dwapb: Get rid of legacy platform data)
Merging pinctrl/for-next (04853352952b Merge tag 'samsung-pinctrl-5.15' of https://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/samsung into devel)
Merging pinctrl-intel/for-next (2f658f7a3953 pinctrl: tigerlake: Fix GPIO mapping for newer version of software)
Merging pinctrl-renesas/renesas-pinctrl (c4c4637eb57f pinctrl: renesas: Add RZ/G2L pin and gpio controller driver)
Merging pinctrl-samsung/for-next (cdd3d945dcec pinctrl: samsung: Add Exynos850 SoC specific data)
Merging pwm/for-next (7954f76161ea pwm: ab8500: Fix register offset calculation to not depend on probe order)
Merging userns/for-next (534471c614f8 Merge of ucount-fixes-for-5.14, and siginfo-si_trapno-for-v5.15 for testing in linux-next)
Merging ktest/for-next (170f4869e662 ktest.pl: Fix the logic for truncating the size of the log file for email)
Merging kselftest/next (2734d6c1b1a0 Linux 5.14-rc2)
Merging livepatching/for-next (cd2d68f2d6b2 Merge branch 'for-5.15/cpu-hotplug' into for-next)
Merging coresight/next (1efbcec2ef8c coresight: cti: Reduce scope for the variable “cs_fwnode” in cti_plat_create_connection())
Merging rtc/rtc-next (8158da6a33f2 dt-bindings: rtc: add Epson RX-8025 and RX-8035)
Merging nvdimm/libnvdimm-for-next (30c10d32152d Merge branch 'for-5.12/cxl' into libnvdimm-for-next)
Merging at24/at24/for-next (658ae44345c1 dt-bindings: at24: add ON Semi CAT24C04 and CAT24C05)
Merging ntb/ntb-next (28293b6c68cd ntb: ntb_pingpong: remove redundant initialization of variables msg_data and spad_data)
Merging seccomp/for-next/seccomp (b4d8a58f8dcf seccomp: Fix setting loaded filter count during TSYNC)
Merging kspp/for-next/kspp (b88972649fa0 lib/test_stackinit: Add assigned initializers)
Merging cisco/for-next (9e98c678c2d6 Linux 5.1-rc1)
Merging gnss/gnss-next (0f79ce970e79 gnss: drop stray semicolons)
Merging fsi/next (9ab1428dfe2c fsi/sbefifo: Fix reset timeout)
Merging slimbus/for-next (e5c578adcdd9 slimbus: ngd: reset dma setup during runtime pm)
Merging nvmem/for-next (80c3356bea4e nvmem: nintendo-otp: Add new driver for the Wii and Wii U OTP)
Merging xarray/main (2c7e57a02708 idr test suite: Improve reporting from idr_find_test_1)
Merging hyperv/hyperv-next (7aff79e297ee Drivers: hv: Enable Hyper-V code to be built on ARM64)
Merging auxdisplay/auxdisplay (24ebc044c72e auxdisplay: Replace symbolic permissions with octal permissions)
Merging kgdb/kgdb/for-next (e868f0a3c4b9 kdb: Rename members of struct kdbtab_t)
Merging hmm/hmm (fe07bfda2fb9 Linux 5.12-rc1)
Merging fpga/for-next (4f45f3404960 spi: spi-altera-dfl: support n5010 feature revision)
Merging kunit/test (e73f0f0ee754 Linux 5.14-rc1)
Merging cfi/cfi/next (ff1176468d36 Linux 5.14-rc3)
Merging kunit-next/kunit (acd8e8407b8f kunit: Print test statistics on failure)
Merging trivial/for-next (9ff9b0d392ea Merge tag 'net-next-5.10' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next)
Merging mhi/mhi-next (813272ed5238 Merge 5.14-rc5 into char-misc-next)
Merging memblock/for-next (e888fa7bb882 memblock: Check memory add/cap ordering)
Merging init/init-user-pointers (38b082236e77 initramfs: use vfs_utimes in do_copy)
Merging counters/counters (e71ba9452f0b Linux 5.11-rc2)
Merging rust/rust-next (5d3986cf8ed6 MAINTAINERS: Rust)
CONFLICT (content): Merge conflict in include/linux/kallsyms.h
CONFLICT (content): Merge conflict in Makefile
Applying: fixup for rust integration with Makefile.clang creation
Merging cxl/next (ceeb0da0a032 cxl/mem: Adjust ram/pmem range to represent DPA ranges)
Merging folio/for-next (1a90e9dae32c mm/writeback: Add folio_write_one)
CONFLICT (content): Merge conflict in mm/util.c
CONFLICT (content): Merge conflict in mm/rmap.c
CONFLICT (content): Merge conflict in mm/filemap.c
Merging akpm-current/current (2832d098abfd ipc: replace costly bailout check in sysvipc_find_ipc())
CONFLICT (content): Merge conflict in mm/page-writeback.c
CONFLICT (content): Merge conflict in mm/memcontrol.c
CONFLICT (content): Merge conflict in include/linux/units.h
CONFLICT (content): Merge conflict in include/linux/sched.h
CONFLICT (content): Merge conflict in include/linux/memcontrol.h
$ git checkout -b akpm remotes/origin/akpm/master
$ git rebase --onto master remotes/origin/akpm/master-base
Merging akpm/master (652afd45cf13 arch: remove compat_alloc_user_space)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-20  9:26 linux-next: Tree for Aug 20 Stephen Rothwell
@ 2021-08-20 21:54 ` Randy Dunlap
  2021-08-21  5:48   ` Kees Cook
  0 siblings, 1 reply; 13+ messages in thread
From: Randy Dunlap @ 2021-08-20 21:54 UTC (permalink / raw)
  To: Stephen Rothwell, Linux Next Mailing List
  Cc: Linux Kernel Mailing List, Andrew Morton, Kees Cook, Nathan Chancellor

On 8/20/21 2:26 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20210819:
> 

Both linux-next and mmotm have many of these warnings when using
gcc (SUSE Linux) 7.5.0:

cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'


-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-20 21:54 ` linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than) Randy Dunlap
@ 2021-08-21  5:48   ` Kees Cook
  2021-08-21 19:09     ` Randy Dunlap
  0 siblings, 1 reply; 13+ messages in thread
From: Kees Cook @ 2021-08-21  5:48 UTC (permalink / raw)
  To: Randy Dunlap, Andrew Morton
  Cc: Stephen Rothwell, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

On Fri, Aug 20, 2021 at 02:54:05PM -0700, Randy Dunlap wrote:
> On 8/20/21 2:26 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20210819:
> > 
> 
> Both linux-next and mmotm have many of these warnings when using
> gcc (SUSE Linux) 7.5.0:
> 
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'

Ew. Thanks for letting me know. I thought I'd verified this existed in
gcc going back to 4.9, but it looks like I did something wrong in that
test.

I think this should fix it:

diff --git a/Makefile b/Makefile
index b0fafc41b686..e33ffa05899e 100644
--- a/Makefile
+++ b/Makefile
@@ -1097,7 +1097,7 @@ endif
 ifdef CONFIG_CC_IS_GCC
 # The allocators already balk at large sizes, so silence the compiler
 # warnings for bounds checks involving those possible values.
-KBUILD_CFLAGS += -Wno-alloc-size-larger-than
+KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
 endif
 
 # disable invalid "can't wrap" optimizations for signed / pointers

-- 
Kees Cook

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-21  5:48   ` Kees Cook
@ 2021-08-21 19:09     ` Randy Dunlap
  2021-08-23 10:37       ` Stephen Rothwell
  0 siblings, 1 reply; 13+ messages in thread
From: Randy Dunlap @ 2021-08-21 19:09 UTC (permalink / raw)
  To: Kees Cook, Andrew Morton
  Cc: Stephen Rothwell, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

On 8/20/21 10:48 PM, Kees Cook wrote:
> On Fri, Aug 20, 2021 at 02:54:05PM -0700, Randy Dunlap wrote:
>> On 8/20/21 2:26 AM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20210819:
>>>
>>
>> Both linux-next and mmotm have many of these warnings when using
>> gcc (SUSE Linux) 7.5.0:
>>
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
> Ew. Thanks for letting me know. I thought I'd verified this existed in
> gcc going back to 4.9, but it looks like I did something wrong in that
> test.
> 
> I think this should fix it:
> 
> diff --git a/Makefile b/Makefile
> index b0fafc41b686..e33ffa05899e 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1097,7 +1097,7 @@ endif
>   ifdef CONFIG_CC_IS_GCC
>   # The allocators already balk at large sizes, so silence the compiler
>   # warnings for bounds checks involving those possible values.
> -KBUILD_CFLAGS += -Wno-alloc-size-larger-than
> +KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
>   endif
>   
>   # disable invalid "can't wrap" optimizations for signed / pointers
> 

Well. That didn't help. This is very weird.

This -Wno... option works (is accepted, no warning) on most files
that are being built, but a few files report an error with it:

../drivers/gpu/drm/radeon/radeon_object.c: At top level:
cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'

../drivers/gpu/drm/amd/amdgpu/amdgpu_object.c: At top level:
cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'

../drivers/hwmon/dell-smm-hwmon.c: At top level:
cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'

   CC      arch/x86/kernel/cpu/proc.o
cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'

../arch/x86/kvm/mmu/mmu.c: At top level:
cc1: error: unrecognized command line option '-Wno-alloc-size-larger-than' [-Werror]

../drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_chardev.c: At top level:
cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'

../kernel/trace/trace_osnoise.c: At top level:
cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'

   CC      kernel/dma/mapping.o
cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'


It seems like it might be related to some .config option.

I did a couple of partial builds with V=1 but that info didn't help me any.


If I am the only person seeing (reporting) this build warning, it could
just be (another) SUSE GCC-ism. (had one just last week with  -Wmain and
kernel/trace/trace_osnoise.c)


-- 
~Randy


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-21 19:09     ` Randy Dunlap
@ 2021-08-23 10:37       ` Stephen Rothwell
  2021-08-24  1:24         ` Randy Dunlap
  0 siblings, 1 reply; 13+ messages in thread
From: Stephen Rothwell @ 2021-08-23 10:37 UTC (permalink / raw)
  To: Randy Dunlap
  Cc: Kees Cook, Andrew Morton, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

[-- Attachment #1: Type: text/plain, Size: 3232 bytes --]

Hi all,

On Sat, 21 Aug 2021 12:09:48 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 8/20/21 10:48 PM, Kees Cook wrote:
> > On Fri, Aug 20, 2021 at 02:54:05PM -0700, Randy Dunlap wrote:  
> >> On 8/20/21 2:26 AM, Stephen Rothwell wrote:  
> >>> Hi all,
> >>>
> >>> Changes since 20210819:
> >>>  
> >>
> >> Both linux-next and mmotm have many of these warnings when using
> >> gcc (SUSE Linux) 7.5.0:
> >>
> >> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'  
> > 
> > Ew. Thanks for letting me know. I thought I'd verified this existed in
> > gcc going back to 4.9, but it looks like I did something wrong in that
> > test.
> > 
> > I think this should fix it:
> > 
> > diff --git a/Makefile b/Makefile
> > index b0fafc41b686..e33ffa05899e 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1097,7 +1097,7 @@ endif
> >   ifdef CONFIG_CC_IS_GCC
> >   # The allocators already balk at large sizes, so silence the compiler
> >   # warnings for bounds checks involving those possible values.
> > -KBUILD_CFLAGS += -Wno-alloc-size-larger-than
> > +KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
> >   endif  
> >   >   # disable invalid "can't wrap" optimizations for signed / pointers  
> >   
> 
> Well. That didn't help. This is very weird.
> 
> This -Wno... option works (is accepted, no warning) on most files
> that are being built, but a few files report an error with it:
> 
> ../drivers/gpu/drm/radeon/radeon_object.c: At top level:
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
> ../drivers/gpu/drm/amd/amdgpu/amdgpu_object.c: At top level:
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
> ../drivers/hwmon/dell-smm-hwmon.c: At top level:
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
>    CC      arch/x86/kernel/cpu/proc.o
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
> ../arch/x86/kvm/mmu/mmu.c: At top level:
> cc1: error: unrecognized command line option '-Wno-alloc-size-larger-than' [-Werror]
> 
> ../drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_chardev.c: At top level:
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
> ../kernel/trace/trace_osnoise.c: At top level:
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
>    CC      kernel/dma/mapping.o
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
> 
> It seems like it might be related to some .config option.
> 
> I did a couple of partial builds with V=1 but that info didn't help me any.
> 
> 
> If I am the only person seeing (reporting) this build warning, it could
> just be (another) SUSE GCC-ism. (had one just last week with  -Wmain and
> kernel/trace/trace_osnoise.c)

Today, I am also seeing thsese, but only with my sparc{,64} defconfig
cross builds.  This is with gcc 7.3.1 built from sources.  I also just
get a few of them.

Also, I have the above "fix" patch applied (Andrew added it to mmots
today).

So something weird is happening.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-23 10:37       ` Stephen Rothwell
@ 2021-08-24  1:24         ` Randy Dunlap
  2021-08-24  1:58           ` Stephen Rothwell
  0 siblings, 1 reply; 13+ messages in thread
From: Randy Dunlap @ 2021-08-24  1:24 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Kees Cook, Andrew Morton, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

On 8/23/21 3:37 AM, Stephen Rothwell wrote:
> Hi all,
> 
> On Sat, 21 Aug 2021 12:09:48 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> On 8/20/21 10:48 PM, Kees Cook wrote:
>>> On Fri, Aug 20, 2021 at 02:54:05PM -0700, Randy Dunlap wrote:
>>>> On 8/20/21 2:26 AM, Stephen Rothwell wrote:
>>>>> Hi all,
>>>>>
>>>>> Changes since 20210819:
>>>>>   
>>>>
>>>> Both linux-next and mmotm have many of these warnings when using
>>>> gcc (SUSE Linux) 7.5.0:
>>>>
>>>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>>
>>> Ew. Thanks for letting me know. I thought I'd verified this existed in
>>> gcc going back to 4.9, but it looks like I did something wrong in that
>>> test.
>>>
>>> I think this should fix it:
>>>
>>> diff --git a/Makefile b/Makefile
>>> index b0fafc41b686..e33ffa05899e 100644
>>> --- a/Makefile
>>> +++ b/Makefile
>>> @@ -1097,7 +1097,7 @@ endif
>>>    ifdef CONFIG_CC_IS_GCC
>>>    # The allocators already balk at large sizes, so silence the compiler
>>>    # warnings for bounds checks involving those possible values.
>>> -KBUILD_CFLAGS += -Wno-alloc-size-larger-than
>>> +KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
>>>    endif
>>>    >   # disable invalid "can't wrap" optimizations for signed / pointers
>>>    
>>
>> Well. That didn't help. This is very weird.
>>
>> This -Wno... option works (is accepted, no warning) on most files
>> that are being built, but a few files report an error with it:
>>
>> ../drivers/gpu/drm/radeon/radeon_object.c: At top level:
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>
>> ../drivers/gpu/drm/amd/amdgpu/amdgpu_object.c: At top level:
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>
>> ../drivers/hwmon/dell-smm-hwmon.c: At top level:
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>
>>     CC      arch/x86/kernel/cpu/proc.o
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>
>> ../arch/x86/kvm/mmu/mmu.c: At top level:
>> cc1: error: unrecognized command line option '-Wno-alloc-size-larger-than' [-Werror]
>>
>> ../drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_chardev.c: At top level:
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>
>> ../kernel/trace/trace_osnoise.c: At top level:
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>
>>     CC      kernel/dma/mapping.o
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>
>>
>> It seems like it might be related to some .config option.
>>
>> I did a couple of partial builds with V=1 but that info didn't help me any.
>>
>>
>> If I am the only person seeing (reporting) this build warning, it could
>> just be (another) SUSE GCC-ism. (had one just last week with  -Wmain and
>> kernel/trace/trace_osnoise.c)
> 
> Today, I am also seeing thsese, but only with my sparc{,64} defconfig
> cross builds.  This is with gcc 7.3.1 built from sources.  I also just
> get a few of them.
> 
> Also, I have the above "fix" patch applied (Andrew added it to mmots
> today).
> 
> So something weird is happening.

This is just weird. What I am seeing is that for every source file
where gcc emits a warning: it then follows that up with this
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'

E.g.:

../kernel/printk/index.c:146:13: warning: ‘pi_remove_file’ defined but not used [-Wunused-function]
  static void pi_remove_file(struct module *mod)
              ^~~~~~~~~~~~~~
cc1: warning: unrecognized command line option ‘-Wno-alloc-size-larger-than’

../fs/remap_range.c: In function ‘remap_verify_area’:
../fs/remap_range.c:102:16: warning: unused variable ‘inode’ [-Wunused-variable]
   struct inode *inode = file_inode(file);
                 ^~~~~
../fs/remap_range.c: At top level:
cc1: warning: unrecognized command line option ‘-Wno-alloc-size-larger-than’

../fs/locks.c: In function ‘fcntl_setlk64’:
../fs/locks.c:2509:16: warning: unused variable ‘inode’ [-Wunused-variable]
   struct inode *inode = locks_inode(filp);
                 ^~~~~
../fs/locks.c: At top level:
cc1: warning: unrecognized command line option ‘-Wno-alloc-size-larger-than’

../drivers/platform/chrome/./cros_ec_trace.h: In function ‘trace_raw_output_cros_ec_sensorhub_filter’:
../drivers/platform/chrome/./cros_ec_trace.h:156:12: warning: format ‘%d’ expects argument of type ‘int’, but argument 7 has type ‘s64 {aka long long int}’ [-Wformat=]
   TP_printk("dx: %12lld. dy: %12lld median_m: %12lld median_error: %12lld len: %d x: %12lld y: %12lld",
             ^
../include/trace/trace_events.h:399:27: note: in definition of macro ‘DECLARE_EVENT_CLASS’
   trace_event_printf(iter, print);    \
                            ^~~~~
../include/trace/trace_events.h:80:9: note: in expansion of macro ‘PARAMS’
          PARAMS(print));         \
          ^~~~~~
../drivers/platform/chrome/./cros_ec_trace.h:135:1: note: in expansion of macro ‘TRACE_EVENT’
  TRACE_EVENT(cros_ec_sensorhub_filter,
  ^~~~~~~~~~~
../drivers/platform/chrome/./cros_ec_trace.h:156:2: note: in expansion of macro ‘TP_printk’
   TP_printk("dx: %12lld. dy: %12lld median_m: %12lld median_error: %12lld len: %d x: %12lld y: %12lld",
   ^~~~~~~~~
In file included from ../include/trace/trace_events.h:433:0,
                  from ../include/trace/define_trace.h:102,
                  from ../drivers/platform/chrome/cros_ec_trace.h:178,
                  from ../drivers/platform/chrome/cros_ec_trace.c:215:
../drivers/platform/chrome/./cros_ec_trace.h:156:80: note: format string is defined here
   TP_printk("dx: %12lld. dy: %12lld median_m: %12lld median_error: %12lld len: %d x: %12lld y: %12lld",
                                                                                ~^
                                                                                %lld
../drivers/platform/chrome/cros_ec_trace.c: At top level:
cc1: warning: unrecognized command line option ‘-Wno-alloc-size-larger-than’

warning: unsafe strscpy() usage lacked '__write_overflow' warning in ../lib/test_fortify/write_overflow-strscpy.c
   CC      drivers/base/driver.o
In file included from ../include/linux/string.h:253:0,
                  from ../arch/x86/include/asm/page_32.h:35,
                  from ../arch/x86/include/asm/page.h:14,
                  from ../arch/x86/include/asm/thread_info.h:12,
                  from ../include/linux/thread_info.h:60,
                  from ../arch/x86/include/asm/preempt.h:7,
                  from ../include/linux/preempt.h:78,
                  from ../include/linux/spinlock.h:55,
                  from ../include/linux/mmzone.h:8,
                  from ../include/linux/gfp.h:6,
                  from ../include/linux/slab.h:15,
                  from ../lib/test_fortify/test_fortify.h:4,
                  from ../lib/test_fortify/write_overflow-strscpy.c:5:
In function ‘strscpy’,
     inlined from ‘do_fortify_tests’ at ../lib/test_fortify/test_fortify.h:34:2:
../include/linux/fortify-string.h:154:3: error: call to ‘__write_overflow’ declared with attribute error: detected write beyond size of object (1st parameter)
    __write_overflow();
    ^~~~~~~~~~~~~~~~~~
../lib/test_fortify/write_overflow-strscpy.c: At top level:
cc1: error: unrecognized command line option ‘-Wno-alloc-size-larger-than’ [-Werror]

Smells like a gcc bug to me.

-- 
~Randy


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-24  1:24         ` Randy Dunlap
@ 2021-08-24  1:58           ` Stephen Rothwell
  2021-08-25  1:59             ` Kees Cook
  2021-08-25 17:04             ` Kees Cook
  0 siblings, 2 replies; 13+ messages in thread
From: Stephen Rothwell @ 2021-08-24  1:58 UTC (permalink / raw)
  To: Randy Dunlap
  Cc: Kees Cook, Andrew Morton, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

[-- Attachment #1: Type: text/plain, Size: 718 bytes --]

Hi Randy,

On Mon, 23 Aug 2021 18:24:44 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> This is just weird. What I am seeing is that for every source file
> where gcc emits a warning: it then follows that up with this
> >> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'  

I see the same, as well as:

<stdin>:1515:2: warning: #warning syscall clone3 not implemented [-Wcpp]
cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'

But only on my gcc 7.3.1 builds (the rest are gcc 10).

> Smells like a gcc bug to me.

Yes

Also noted here: https://github.com/DynamoRIO/drmemory/issues/2099 (second comment)
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-24  1:58           ` Stephen Rothwell
@ 2021-08-25  1:59             ` Kees Cook
  2021-08-25 17:04             ` Kees Cook
  1 sibling, 0 replies; 13+ messages in thread
From: Kees Cook @ 2021-08-25  1:59 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Randy Dunlap, Andrew Morton, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

On Tue, Aug 24, 2021 at 11:58:59AM +1000, Stephen Rothwell wrote:
> Hi Randy,
> 
> On Mon, 23 Aug 2021 18:24:44 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > This is just weird. What I am seeing is that for every source file
> > where gcc emits a warning: it then follows that up with this
> > >> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'  
> 
> I see the same, as well as:
> 
> <stdin>:1515:2: warning: #warning syscall clone3 not implemented [-Wcpp]
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
> But only on my gcc 7.3.1 builds (the rest are gcc 10).
> 
> > Smells like a gcc bug to me.
> 
> Yes
> 
> Also noted here: https://github.com/DynamoRIO/drmemory/issues/2099 (second comment)

Wow, this is really weird. Okay, thanks for the pointers. I'll keep
investigating. I may need to version-limit the use of __alloc_size,
though I'd rather not. We've been able to depend on has_builtin() nicely
for a while now. :P

-- 
Kees Cook

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-24  1:58           ` Stephen Rothwell
  2021-08-25  1:59             ` Kees Cook
@ 2021-08-25 17:04             ` Kees Cook
  2021-08-25 17:49               ` Randy Dunlap
  1 sibling, 1 reply; 13+ messages in thread
From: Kees Cook @ 2021-08-25 17:04 UTC (permalink / raw)
  To: Andrew Morton
  Cc: Randy Dunlap, Stephen Rothwell, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

On Tue, Aug 24, 2021 at 11:58:59AM +1000, Stephen Rothwell wrote:
> On Mon, 23 Aug 2021 18:24:44 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > This is just weird. What I am seeing is that for every source file
> > where gcc emits a warning: it then follows that up with this
> > >> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'  
> 
> I see the same, as well as:
> 
> <stdin>:1515:2: warning: #warning syscall clone3 not implemented [-Wcpp]
> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> 
> But only on my gcc 7.3.1 builds (the rest are gcc 10).
> 
> > Smells like a gcc bug to me.
> 
> Yes
> 
> Also noted here: https://github.com/DynamoRIO/drmemory/issues/2099 (second comment)

Okay, I think this work-around should work. I've been able to reproduce
the weird conditions, and this seems to behave correctly. Andrew, can
you fixup the fixup with this?


diff --git a/Makefile b/Makefile
index 26640899e7ca..c1842014a5de 100644
--- a/Makefile
+++ b/Makefile
@@ -1094,8 +1094,13 @@ endif
 
 ifdef CONFIG_CC_IS_GCC
 # The allocators already balk at large sizes, so silence the compiler
-# warnings for bounds checks involving those possible values.
-KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
+# warnings for bounds checks involving those possible values. While
+# -Wno-alloc-size-larger-than would normally be used here, some versions
+# of gcc (<9.1) weirdly don't handle the option correctly when _other_
+# warnings are produced (?!), so instead use SIZE_MAX to effectively
+# disable it.
+# https://lore.kernel.org/lkml/20210824115859.187f272f@canb.auug.org.au
+KBUILD_CFLAGS += $(call cc-option, -Walloc-size-larger-than=SIZE_MAX)
 endif
 
 # disable invalid "can't wrap" optimizations for signed / pointers


-- 
Kees Cook

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-25 17:04             ` Kees Cook
@ 2021-08-25 17:49               ` Randy Dunlap
  2021-08-26  3:54                 ` Kees Cook
  0 siblings, 1 reply; 13+ messages in thread
From: Randy Dunlap @ 2021-08-25 17:49 UTC (permalink / raw)
  To: Kees Cook, Andrew Morton
  Cc: Stephen Rothwell, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

On 8/25/21 10:04 AM, Kees Cook wrote:
> On Tue, Aug 24, 2021 at 11:58:59AM +1000, Stephen Rothwell wrote:
>> On Mon, 23 Aug 2021 18:24:44 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>>>
>>> This is just weird. What I am seeing is that for every source file
>>> where gcc emits a warning: it then follows that up with this
>>>>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>
>> I see the same, as well as:
>>
>> <stdin>:1515:2: warning: #warning syscall clone3 not implemented [-Wcpp]
>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>
>> But only on my gcc 7.3.1 builds (the rest are gcc 10).
>>
>>> Smells like a gcc bug to me.
>>
>> Yes
>>
>> Also noted here: https://github.com/DynamoRIO/drmemory/issues/2099 (second comment)
> 
> Okay, I think this work-around should work. I've been able to reproduce
> the weird conditions, and this seems to behave correctly. Andrew, can
> you fixup the fixup with this?
> 
> 
> diff --git a/Makefile b/Makefile
> index 26640899e7ca..c1842014a5de 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1094,8 +1094,13 @@ endif
>   
>   ifdef CONFIG_CC_IS_GCC
>   # The allocators already balk at large sizes, so silence the compiler
> -# warnings for bounds checks involving those possible values.
> -KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
> +# warnings for bounds checks involving those possible values. While
> +# -Wno-alloc-size-larger-than would normally be used here, some versions
> +# of gcc (<9.1) weirdly don't handle the option correctly when _other_
> +# warnings are produced (?!), so instead use SIZE_MAX to effectively
> +# disable it.
> +# https://lore.kernel.org/lkml/20210824115859.187f272f@canb.auug.org.au
> +KBUILD_CFLAGS += $(call cc-option, -Walloc-size-larger-than=SIZE_MAX)
>   endif
>   
>   # disable invalid "can't wrap" optimizations for signed / pointers
> 

Hi Kees,

I get a lot of these:

../include/linux/slab.h: In function ‘keyctl_instantiate_key_common’:
cc1: warning: invalid argument ‘SIZE_MAX’ to ‘-Walloc-size-larger-than=’



-- 
~Randy


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-25 17:49               ` Randy Dunlap
@ 2021-08-26  3:54                 ` Kees Cook
  2021-08-26  5:10                   ` Randy Dunlap
  0 siblings, 1 reply; 13+ messages in thread
From: Kees Cook @ 2021-08-26  3:54 UTC (permalink / raw)
  To: Randy Dunlap
  Cc: Andrew Morton, Stephen Rothwell, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

On Wed, Aug 25, 2021 at 10:49:19AM -0700, Randy Dunlap wrote:
> On 8/25/21 10:04 AM, Kees Cook wrote:
> > On Tue, Aug 24, 2021 at 11:58:59AM +1000, Stephen Rothwell wrote:
> > > On Mon, 23 Aug 2021 18:24:44 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> > > > 
> > > > This is just weird. What I am seeing is that for every source file
> > > > where gcc emits a warning: it then follows that up with this
> > > > > > cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> > > 
> > > I see the same, as well as:
> > > 
> > > <stdin>:1515:2: warning: #warning syscall clone3 not implemented [-Wcpp]
> > > cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> > > 
> > > But only on my gcc 7.3.1 builds (the rest are gcc 10).
> > > 
> > > > Smells like a gcc bug to me.
> > > 
> > > Yes
> > > 
> > > Also noted here: https://github.com/DynamoRIO/drmemory/issues/2099 (second comment)
> > 
> > Okay, I think this work-around should work. I've been able to reproduce
> > the weird conditions, and this seems to behave correctly. Andrew, can
> > you fixup the fixup with this?
> > 
> > 
> > diff --git a/Makefile b/Makefile
> > index 26640899e7ca..c1842014a5de 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1094,8 +1094,13 @@ endif
> >   ifdef CONFIG_CC_IS_GCC
> >   # The allocators already balk at large sizes, so silence the compiler
> > -# warnings for bounds checks involving those possible values.
> > -KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
> > +# warnings for bounds checks involving those possible values. While
> > +# -Wno-alloc-size-larger-than would normally be used here, some versions
> > +# of gcc (<9.1) weirdly don't handle the option correctly when _other_
> > +# warnings are produced (?!), so instead use SIZE_MAX to effectively
> > +# disable it.
> > +# https://lore.kernel.org/lkml/20210824115859.187f272f@canb.auug.org.au
> > +KBUILD_CFLAGS += $(call cc-option, -Walloc-size-larger-than=SIZE_MAX)
> >   endif
> >   # disable invalid "can't wrap" optimizations for signed / pointers
> > 
> 
> Hi Kees,
> 
> I get a lot of these:
> 
> ../include/linux/slab.h: In function ‘keyctl_instantiate_key_common’:
> cc1: warning: invalid argument ‘SIZE_MAX’ to ‘-Walloc-size-larger-than=’

O_o

I love how the documentation on this option is consistently wrong. :)

I haven't been able to exactly reproduce this error on godbolt.org, but
I got close with trunk GCC:
gcc: error: argument to '-Walloc-size-larger-than=' should be a non-negative integer optionally followed by a size unit

Even though stdint.h is included. :(

Okay. How about _this_ fix?

diff --git a/Makefile b/Makefile
index efa9bd36b158..141a851930e6 100644
--- a/Makefile
+++ b/Makefile
@@ -1096,8 +1096,17 @@ endif
 
 ifdef CONFIG_CC_IS_GCC
 # The allocators already balk at large sizes, so silence the compiler
-# warnings for bounds checks involving those possible values.
-KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
+# warnings for bounds checks involving those possible values. While
+# -Wno-alloc-size-larger-than would normally be used here, earlier versions
+# of gcc (<9.1) weirdly don't handle the option correctly when _other_
+# warnings are produced (?!). Using -Walloc-size-larger-than=SIZE_MAX
+# doesn't work (as it is documented to), silently resolving to "0" prior to
+# version 9.1 (and producing an error more recently). Numeric values larger
+# than PTRDIFF_MAX also don't work prior to version 9.1, which are silently
+# ignored, continuing to default to PTRDIFF_MAX. So, left with no other
+# choice, we must perform a versioned check to disable this warning.
+# https://lore.kernel.org/lkml/20210824115859.187f272f@canb.auug.org.au
+KBUILD_CFLAGS += $(call cc-ifversion, -ge, 0901, -Wno-alloc-size-larger-than)
 endif
 
 # disable invalid "can't wrap" optimizations for signed / pointers


-- 
Kees Cook

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-26  3:54                 ` Kees Cook
@ 2021-08-26  5:10                   ` Randy Dunlap
  2021-08-26  5:23                     ` Kees Cook
  0 siblings, 1 reply; 13+ messages in thread
From: Randy Dunlap @ 2021-08-26  5:10 UTC (permalink / raw)
  To: Kees Cook
  Cc: Andrew Morton, Stephen Rothwell, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

On 8/25/21 8:54 PM, Kees Cook wrote:
> On Wed, Aug 25, 2021 at 10:49:19AM -0700, Randy Dunlap wrote:
>> On 8/25/21 10:04 AM, Kees Cook wrote:
>>> On Tue, Aug 24, 2021 at 11:58:59AM +1000, Stephen Rothwell wrote:
>>>> On Mon, 23 Aug 2021 18:24:44 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>>>>>
>>>>> This is just weird. What I am seeing is that for every source file
>>>>> where gcc emits a warning: it then follows that up with this
>>>>>>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>>>
>>>> I see the same, as well as:
>>>>
>>>> <stdin>:1515:2: warning: #warning syscall clone3 not implemented [-Wcpp]
>>>> cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
>>>>
>>>> But only on my gcc 7.3.1 builds (the rest are gcc 10).
>>>>
>>>>> Smells like a gcc bug to me.
>>>>
>>>> Yes
>>>>
>>>> Also noted here: https://github.com/DynamoRIO/drmemory/issues/2099 (second comment)
>>>
>>> Okay, I think this work-around should work. I've been able to reproduce
>>> the weird conditions, and this seems to behave correctly. Andrew, can
>>> you fixup the fixup with this?
>>>
>>>
>>> diff --git a/Makefile b/Makefile
>>> index 26640899e7ca..c1842014a5de 100644
>>> --- a/Makefile
>>> +++ b/Makefile
>>> @@ -1094,8 +1094,13 @@ endif
>>>    ifdef CONFIG_CC_IS_GCC
>>>    # The allocators already balk at large sizes, so silence the compiler
>>> -# warnings for bounds checks involving those possible values.
>>> -KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
>>> +# warnings for bounds checks involving those possible values. While
>>> +# -Wno-alloc-size-larger-than would normally be used here, some versions
>>> +# of gcc (<9.1) weirdly don't handle the option correctly when _other_
>>> +# warnings are produced (?!), so instead use SIZE_MAX to effectively
>>> +# disable it.
>>> +# https://lore.kernel.org/lkml/20210824115859.187f272f@canb.auug.org.au
>>> +KBUILD_CFLAGS += $(call cc-option, -Walloc-size-larger-than=SIZE_MAX)
>>>    endif
>>>    # disable invalid "can't wrap" optimizations for signed / pointers
>>>
>>
>> Hi Kees,
>>
>> I get a lot of these:
>>
>> ../include/linux/slab.h: In function ‘keyctl_instantiate_key_common’:
>> cc1: warning: invalid argument ‘SIZE_MAX’ to ‘-Walloc-size-larger-than=’
> 
> O_o
> 
> I love how the documentation on this option is consistently wrong. :)
> 
> I haven't been able to exactly reproduce this error on godbolt.org, but
> I got close with trunk GCC:
> gcc: error: argument to '-Walloc-size-larger-than=' should be a non-negative integer optionally followed by a size unit
> 
> Even though stdint.h is included. :(
> 
> Okay. How about _this_ fix?
> 
> diff --git a/Makefile b/Makefile
> index efa9bd36b158..141a851930e6 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1096,8 +1096,17 @@ endif
>   
>   ifdef CONFIG_CC_IS_GCC
>   # The allocators already balk at large sizes, so silence the compiler
> -# warnings for bounds checks involving those possible values.
> -KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
> +# warnings for bounds checks involving those possible values. While
> +# -Wno-alloc-size-larger-than would normally be used here, earlier versions
> +# of gcc (<9.1) weirdly don't handle the option correctly when _other_
> +# warnings are produced (?!). Using -Walloc-size-larger-than=SIZE_MAX
> +# doesn't work (as it is documented to), silently resolving to "0" prior to
> +# version 9.1 (and producing an error more recently). Numeric values larger
> +# than PTRDIFF_MAX also don't work prior to version 9.1, which are silently
> +# ignored, continuing to default to PTRDIFF_MAX. So, left with no other
> +# choice, we must perform a versioned check to disable this warning.
> +# https://lore.kernel.org/lkml/20210824115859.187f272f@canb.auug.org.au
> +KBUILD_CFLAGS += $(call cc-ifversion, -ge, 0901, -Wno-alloc-size-larger-than)
>   endif
>   
>   # disable invalid "can't wrap" optimizations for signed / pointers

Yes, this works for me. Thanks.

Tested-by: Randy Dunlap <rdunlap@infradead.org>

-- 
~Randy


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than)
  2021-08-26  5:10                   ` Randy Dunlap
@ 2021-08-26  5:23                     ` Kees Cook
  0 siblings, 0 replies; 13+ messages in thread
From: Kees Cook @ 2021-08-26  5:23 UTC (permalink / raw)
  To: Randy Dunlap
  Cc: Andrew Morton, Stephen Rothwell, Linux Next Mailing List,
	Linux Kernel Mailing List, Nathan Chancellor

On Wed, Aug 25, 2021 at 10:10:24PM -0700, Randy Dunlap wrote:
> On 8/25/21 8:54 PM, Kees Cook wrote:
> > On Wed, Aug 25, 2021 at 10:49:19AM -0700, Randy Dunlap wrote:
> > > On 8/25/21 10:04 AM, Kees Cook wrote:
> > > > On Tue, Aug 24, 2021 at 11:58:59AM +1000, Stephen Rothwell wrote:
> > > > > On Mon, 23 Aug 2021 18:24:44 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> > > > > > 
> > > > > > This is just weird. What I am seeing is that for every source file
> > > > > > where gcc emits a warning: it then follows that up with this
> > > > > > > > cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> > > > > 
> > > > > I see the same, as well as:
> > > > > 
> > > > > <stdin>:1515:2: warning: #warning syscall clone3 not implemented [-Wcpp]
> > > > > cc1: warning: unrecognized command line option '-Wno-alloc-size-larger-than'
> > > > > 
> > > > > But only on my gcc 7.3.1 builds (the rest are gcc 10).
> > > > > 
> > > > > > Smells like a gcc bug to me.
> > > > > 
> > > > > Yes
> > > > > 
> > > > > Also noted here: https://github.com/DynamoRIO/drmemory/issues/2099 (second comment)
> > > > 
> > > > Okay, I think this work-around should work. I've been able to reproduce
> > > > the weird conditions, and this seems to behave correctly. Andrew, can
> > > > you fixup the fixup with this?
> > > > 
> > > > 
> > > > diff --git a/Makefile b/Makefile
> > > > index 26640899e7ca..c1842014a5de 100644
> > > > --- a/Makefile
> > > > +++ b/Makefile
> > > > @@ -1094,8 +1094,13 @@ endif
> > > >    ifdef CONFIG_CC_IS_GCC
> > > >    # The allocators already balk at large sizes, so silence the compiler
> > > > -# warnings for bounds checks involving those possible values.
> > > > -KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
> > > > +# warnings for bounds checks involving those possible values. While
> > > > +# -Wno-alloc-size-larger-than would normally be used here, some versions
> > > > +# of gcc (<9.1) weirdly don't handle the option correctly when _other_
> > > > +# warnings are produced (?!), so instead use SIZE_MAX to effectively
> > > > +# disable it.
> > > > +# https://lore.kernel.org/lkml/20210824115859.187f272f@canb.auug.org.au
> > > > +KBUILD_CFLAGS += $(call cc-option, -Walloc-size-larger-than=SIZE_MAX)
> > > >    endif
> > > >    # disable invalid "can't wrap" optimizations for signed / pointers
> > > > 
> > > 
> > > Hi Kees,
> > > 
> > > I get a lot of these:
> > > 
> > > ../include/linux/slab.h: In function ‘keyctl_instantiate_key_common’:
> > > cc1: warning: invalid argument ‘SIZE_MAX’ to ‘-Walloc-size-larger-than=’
> > 
> > O_o
> > 
> > I love how the documentation on this option is consistently wrong. :)
> > 
> > I haven't been able to exactly reproduce this error on godbolt.org, but
> > I got close with trunk GCC:
> > gcc: error: argument to '-Walloc-size-larger-than=' should be a non-negative integer optionally followed by a size unit
> > 
> > Even though stdint.h is included. :(
> > 
> > Okay. How about _this_ fix?
> > 
> > diff --git a/Makefile b/Makefile
> > index efa9bd36b158..141a851930e6 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1096,8 +1096,17 @@ endif
> >   ifdef CONFIG_CC_IS_GCC
> >   # The allocators already balk at large sizes, so silence the compiler
> > -# warnings for bounds checks involving those possible values.
> > -KBUILD_CFLAGS += $(call cc-option, -Wno-alloc-size-larger-than)
> > +# warnings for bounds checks involving those possible values. While
> > +# -Wno-alloc-size-larger-than would normally be used here, earlier versions
> > +# of gcc (<9.1) weirdly don't handle the option correctly when _other_
> > +# warnings are produced (?!). Using -Walloc-size-larger-than=SIZE_MAX
> > +# doesn't work (as it is documented to), silently resolving to "0" prior to
> > +# version 9.1 (and producing an error more recently). Numeric values larger
> > +# than PTRDIFF_MAX also don't work prior to version 9.1, which are silently
> > +# ignored, continuing to default to PTRDIFF_MAX. So, left with no other
> > +# choice, we must perform a versioned check to disable this warning.
> > +# https://lore.kernel.org/lkml/20210824115859.187f272f@canb.auug.org.au
> > +KBUILD_CFLAGS += $(call cc-ifversion, -ge, 0901, -Wno-alloc-size-larger-than)
> >   endif
> >   # disable invalid "can't wrap" optimizations for signed / pointers
> 
> Yes, this works for me. Thanks.
> 
> Tested-by: Randy Dunlap <rdunlap@infradead.org>

Oh good! I've slowly been losing my mind trying to find a solution. :)
Thanks for testing each attempt!

-Kees

-- 
Kees Cook

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2021-08-26  5:23 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-20  9:26 linux-next: Tree for Aug 20 Stephen Rothwell
2021-08-20 21:54 ` linux-next: Tree for Aug 20 (Wno-alloc-size-larger-than) Randy Dunlap
2021-08-21  5:48   ` Kees Cook
2021-08-21 19:09     ` Randy Dunlap
2021-08-23 10:37       ` Stephen Rothwell
2021-08-24  1:24         ` Randy Dunlap
2021-08-24  1:58           ` Stephen Rothwell
2021-08-25  1:59             ` Kees Cook
2021-08-25 17:04             ` Kees Cook
2021-08-25 17:49               ` Randy Dunlap
2021-08-26  3:54                 ` Kees Cook
2021-08-26  5:10                   ` Randy Dunlap
2021-08-26  5:23                     ` Kees Cook

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).