I've run into some problems which appear due to (a) recent patch(es) on
the wlcore wifi driver.
4.4.160 - commit 3fdd34643ffc378b5924941fad40352c04610294
4.9.131 - commit afeeecc764436f31d4447575bb9007732333818c
Earlier versions (4.9.130 and 4.4.159 - tested back to 4.4.49) do not
exhibit this problem. It is still present in 4.9.141.
master as of 4.20.0-rc4 does not exhibit this problem.
Basically, during client association when in AP mode (running hostapd),
handshake may or may not complete following a noticeable delay. If
successful, then the driver fails consistently in warn_slowpath_null
during disassociation. If unsuccessful, the wifi client attempts
multiple times, sometimes failing repeatedly. I've had clients unable to
connect for 3-5 minutes during testing, with the syslog filled with
dozens of backtraces. syslog details are below.
I'm working on an embedded device with a TI 3352 ARM processor and a
murata wl1271 module in sdio mode. We're running a fully patched ubuntu
18.04 ARM build, with a kernel built from kernel.org's stable/linux repo
<https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=…>.
Relevant parts of the kernel config are included below.
The commit message states:
> /I've only seen this few times with the runtime PM patches enabled so
> this one is probably not needed before that. This seems to work
> currently based on the current PM implementation timer. Let's apply
> this separately though in case others are hitting this issue./
We're not doing anything explicit with power management. The device is
an IoT edge gateway with battery backup, normally running on wall power.
The battery is currently used solely to shut down the system cleanly to
avoid filesystem corruption.
The device tree is configured to keep power in suspend; but the device
should never suspend, so in our case, there is no need to call
wl1271_ps_elp_wakeup() or wl1271_ps_elp_sleep(), as occurs in the patch.
&mmc2 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&wl1271_pins>;
vmmc-supply = <&vwifi>;
bus-width = <4>;
ti,non-removable;
/* am335x-evm.dts: ti,needs-special-hs-handling; - evm has wl18xx not
wl12xx */
cap-power-off-card;
keep-power-in-suspend;
#address-cells = <1>;
#size-cells = <0>;
wlcore: wlcore@2 {
compatible = "ti,wl1271";
reg = <2>;
interrupt-parent = <&gpio1>;
interrupts = <14 IRQ_TYPE_LEVEL_HIGH>; /* gpio1[14] */
ref-clock-frequency = <38400000>;
};
};
At this point, we're unable to ship a kernel version later than 4.9.130;
so it's important to us to get this issue resolved.
The simplest thing for us would be if these changes could be reverted;
but I'd be happy to debug or try some things out.
Thanks,
Dietmar May
Software Architect
Intellastar LLC
_Association_
Nov 16 15:25:52 ice hostapd: wlan0: STA 84:3a:4b:00:8d:04 IEEE 802.11:
authenticated
Nov 16 15:25:52 ice hostapd: wlan0: STA 84:3a:4b:00:8d:04 IEEE 802.11:
associated (aid 1)
Nov 16 15:25:52 ice hostapd: wlan0: STA 84:3a:4b:00:8d:04 RADIUS:
starting accounting session 5BEEE158-00000000
Nov 16 15:25:52 ice hostapd: wlan0: STA 84:3a:4b:00:8d:04 WPA: pairwise
key handshake completed (RSN)
_Disassociation_
Nov 16 15:26:05 ice kernel: ------------[ cut here ]------------
Nov 16 15:26:05 ice kernel: WARNING: CPU: 0 PID: 1067 at
drivers/net/wireless/ti/wlcore/ps.c:91 wl12xx_op_sta_state+0x208/0x56c
[wlcore]
Nov 16 15:26:05 ice kernel: Modules linked in: bridge stp llc cdc_ncm
usbnet mii cdc_acm usb_serial_simple usbserial bnep hci_uart bluetooth
xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
nf_nat nf_conntrack arc4 wl12xx wlcore mac80211 cfg80211 musb_dsps
musb_hdrc usbcore phy_am335x cppi41 phy_am335x_control phy_generic
usb_common ti_am335x_adc kfifo_buf industrialio wlcore_sdio omap_rng
rng_core musb_am335x rtc_omap omap_wdt ti_am335x_tscadc cpufreq_dt
leds_gpio led_class thermal_sys hwmon autofs4
Nov 16 15:26:05 ice kernel: CPU: 0 PID: 1067 Comm: hostapd Not tainted
4.9.131-ice245 #1
Nov 16 15:26:05 ice kernel: Hardware name: Generic AM33XX (Flattened
Device Tree)
Nov 16 15:26:05 ice kernel: [<c010d2e0>] (unwind_backtrace) from
[<c010b50c>] (show_stack+0x10/0x14)
Nov 16 15:26:05 ice kernel: [<c010b50c>] (show_stack) from [<c012e3ac>]
(__warn+0xd8/0x100)
Nov 16 15:26:05 ice kernel: [<c012e3ac>] (__warn) from [<c012e480>]
(warn_slowpath_null+0x20/0x28)
Nov 16 15:26:05 ice kernel: [<c012e480>] (warn_slowpath_null) from
[<bf2e521c>] (wl12xx_op_sta_state+0x208/0x56c [wlcore])
Nov 16 15:26:05 ice kernel: [<bf2e521c>] (wl12xx_op_sta_state [wlcore])
from [<bf20dbf8>] (drv_sta_state+0x84/0x6c8 [mac80211])
Nov 16 15:26:05 ice kernel: [<bf20dbf8>] (drv_sta_state [mac80211]) from
[<bf215284>] (__sta_info_destroy_part2+0x160/0x1b4 [mac80211])
Nov 16 15:26:05 ice kernel: [<bf215284>] (__sta_info_destroy_part2
[mac80211]) from [<bf2152f8>] (__sta_info_destroy+0x20/0x28 [mac80211])
Nov 16 15:26:05 ice kernel: [<bf2152f8>] (__sta_info_destroy [mac80211])
from [<bf21537c>] (sta_info_destroy_addr_bss+0x30/0x4c [mac80211])
Nov 16 15:26:05 ice kernel: [<bf21537c>] (sta_info_destroy_addr_bss
[mac80211]) from [<bf171c70>] (nl80211_del_station+0xe8/0x2b8 [cfg80211])
Nov 16 15:26:05 ice kernel: [<bf171c70>] (nl80211_del_station
[cfg80211]) from [<c05535c4>] (genl_rcv_msg+0x308/0x3e4)
Nov 16 15:26:05 ice kernel: [<c05535c4>] (genl_rcv_msg) from
[<c05527a0>] (netlink_rcv_skb+0xa4/0xe8)
Nov 16 15:26:05 ice kernel: [<c05527a0>] (netlink_rcv_skb) from
[<c05532a8>] (genl_rcv+0x20/0x34)
Nov 16 15:26:05 ice kernel: [<c05532a8>] (genl_rcv) from [<c0552100>]
(netlink_unicast+0x168/0x1f4)
Nov 16 15:26:05 ice kernel: [<c0552100>] (netlink_unicast) from
[<c0552540>] (netlink_sendmsg+0x2e8/0x378)
Nov 16 15:26:05 ice kernel: [<c0552540>] (netlink_sendmsg) from
[<c050396c>] (sock_sendmsg+0x14/0x24)
Nov 16 15:26:05 ice kernel: [<c050396c>] (sock_sendmsg) from
[<c05041f8>] (___sys_sendmsg+0x1ec/0x200)
Nov 16 15:26:05 ice kernel: [<c05041f8>] (___sys_sendmsg) from
[<c0504fa0>] (__sys_sendmsg+0x40/0x6c)
Nov 16 15:26:05 ice kernel: [<c0504fa0>] (__sys_sendmsg) from
[<c0107560>] (ret_fast_syscall+0x0/0x1c)
Nov 16 15:26:05 ice kernel: ---[ end trace 44f73265865f31c4 ]---
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="am335x-pm-firmware.elf"
CONFIG_AM335X_PHY_USB=m
CONFIG_ARCH_MULTI_V6=y
CONFIG_ARCH_OMAP2PLUS=y
CONFIG_ARCH_OMAP2=y
CONFIG_ARCH_OMAP3=y
CONFIG_ARCH_OMAP=y
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_ARM_CRYPTO=y
CONFIG_ARM_ERRATA_411920=y
CONFIG_ARM_ERRATA_430973=y
CONFIG_ARM_THUMBEE=y
CONFIG_CFG80211=m
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
CONFIG_CPUFREQ_DT=m
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ=y
CONFIG_CPU_IDLE=y
CONFIG_CPUSETS=y
CONFIG_CPU_THERMAL=y
CONFIG_DMA_CMA=y
CONFIG_DMADEVICES=y
CONFIG_DMA_OMAP=yCONFIG_MAC80211=m
CONFIG_MMC_OMAP_HS=y
CONFIG_MMC_OMAP=y
CONFIG_MMC=y
CONFIG_OMAP3_THERMAL=y
CONFIG_OMAP_IOMMU=y
CONFIG_OMAP_MUX_DEBUG=n
CONFIG_OMAP_OCP2SCP=y
CONFIG_OMAP_RESET_CLOCKS=y
CONFIG_OMAP_SSI=m
CONFIG_OMAP_USB2=m
CONFIG_OMAP_WATCHDOG=m
CONFIG_POWER_AVS_OMAP_CLASS3=y
CONFIG_POWER_AVS_OMAP=y
CONFIG_POWER_AVS=y
CONFIG_POWER_RESET=y
CONFIG_SLUB=y
CONFIG_SOC_AM33XX=y
CONFIG_SOC_TI=y
CONFIG_THERMAL_GOV_FAIR_SHARE=y
CONFIG_THERMAL_GOV_USER_SPACE=y
CONFIG_THERMAL=m
CONFIG_TI_AM335X_ADC=m
CONFIG_TI_CPSW=y
CONFIG_TI_CPTS=y
CONFIG_TI_DAVINCI_EMAC=y
CONFIG_TI_EDMA=y
CONFIG_TI_EMIF=m
CONFIG_TIMER_STATS=y
CONFIG_TI_PIPE3=y
CONFIG_TI_SOC_THERMAL=m
CONFIG_TI_THERMAL=y
CONFIG_WIRELESS=y
CONFIG_WL12XX=m
CONFIG_WL18XX=m
CONFIG_WLAN=y
CONFIG_WLCORE_SDIO=m
CONFIG_WLCORE_SPI=m
CONFIG_WL_TI=y
--
This email and any information disclosed in connection herewith, whether
written or oral, is the property of Intellastar LLC, and is intended only
for the person or entity to which it is addressed. This email may contain
information that is privileged confidential or otherwise protected from
disclosure. Distributing or copying any information contained in this email
to anyone other than the intended recipient is strictly prohibited.
From: "Steven Rostedt (VMware)" <rostedt(a)goodmis.org>
The following commands will cause a memory leak:
# cd /sys/kernel/tracing
# mkdir instances/foo
# echo schedule > instance/foo/set_ftrace_filter
# rmdir instances/foo
The reason is that the hashes that hold the filters to set_ftrace_filter and
set_ftrace_notrace are not freed if they contain any data on the instance
and the instance is removed.
Found by kmemleak detector.
Cc: stable(a)vger.kernel.org
Fixes: 591dffdade9f ("ftrace: Allow for function tracing instance to filter functions")
Signed-off-by: Steven Rostedt (VMware) <rostedt(a)goodmis.org>
---
kernel/trace/ftrace.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index 77734451cb05..e23eb9fc77aa 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace/ftrace.c
@@ -5460,6 +5460,7 @@ void ftrace_destroy_filter_files(struct ftrace_ops *ops)
if (ops->flags & FTRACE_OPS_FL_ENABLED)
ftrace_shutdown(ops, 0);
ops->flags |= FTRACE_OPS_FL_DELETED;
+ ftrace_free_filter(ops);
mutex_unlock(&ftrace_lock);
}
--
2.19.1
From: "Steven Rostedt (VMware)" <rostedt(a)goodmis.org>
When create_event_filter() fails in set_trigger_filter(), the filter may
still be allocated and needs to be freed. The caller expects the
data->filter to be updated with the new filter, even if the new filter
failed (we could add an error message by setting set_str parameter of
create_event_filter(), but that's another update).
But because the error would just exit, filter was left hanging and
nothing could free it.
Found by kmemleak detector.
Cc: stable(a)vger.kernel.org
Fixes: bac5fb97a173a ("tracing: Add and use generic set_trigger_filter() implementation")
Reviewed-by: Tom Zanussi <tom.zanussi(a)linux.intel.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt(a)goodmis.org>
---
kernel/trace/trace_events_trigger.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
index 2152d1e530cb..cd12ecb66eb9 100644
--- a/kernel/trace/trace_events_trigger.c
+++ b/kernel/trace/trace_events_trigger.c
@@ -732,8 +732,10 @@ int set_trigger_filter(char *filter_str,
/* The filter is for the 'trigger' event, not the triggered event */
ret = create_event_filter(file->event_call, filter_str, false, &filter);
- if (ret)
- goto out;
+ /*
+ * If create_event_filter() fails, filter still needs to be freed.
+ * Which the calling code will do with data->filter.
+ */
assign:
tmp = rcu_access_pointer(data->filter);
--
2.19.1
stable-rc/linux-3.18.y build: 185 builds: 2 failed, 183 passed, 4 errors, 1590 warnings (v3.18.128-55-g93a539f50736)
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.128-5…
Tree: stable-rc
Branch: linux-3.18.y
Git Describe: v3.18.128-55-g93a539f50736
Git Commit: 93a539f507363d7acb7eafbbd58942574b7ff4f5
Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Built: 6 unique architectures
Build Failures Detected:
arc: gcc version 7.1.1 20170710 (ARCv2 ISA Linux uClibc toolchain 2017.09)
allnoconfig: FAIL
tinyconfig: FAIL
Errors and Warnings Detected:
arc: gcc version 7.1.1 20170710 (ARCv2 ISA Linux uClibc toolchain 2017.09)
allnoconfig: 2 errors, 666 warnings
tinyconfig: 2 errors, 664 warnings
arm64: gcc version 7.3.0 (Debian 7.3.0-28)
allnoconfig: 2 warnings
defconfig: 2 warnings
tinyconfig: 2 warnings
arm: gcc version 7.3.0 (Debian 7.3.0-28)
acs5k_defconfig: 2 warnings
acs5k_tiny_defconfig: 2 warnings
allnoconfig: 2 warnings
am200epdkit_defconfig: 2 warnings
ape6evm_defconfig: 2 warnings
armadillo800eva_defconfig: 2 warnings
assabet_defconfig: 2 warnings
at91_dt_defconfig: 2 warnings
at91rm9200_defconfig: 2 warnings
at91sam9260_9g20_defconfig: 2 warnings
at91sam9261_9g10_defconfig: 2 warnings
at91sam9263_defconfig: 2 warnings
at91sam9g45_defconfig: 2 warnings
at91sam9rl_defconfig: 2 warnings
at91x40_defconfig: 2 warnings
axm55xx_defconfig: 2 warnings
badge4_defconfig: 2 warnings
bcm2835_defconfig: 2 warnings
bcm_defconfig: 2 warnings
bockw_defconfig: 2 warnings
cerfcube_defconfig: 2 warnings
clps711x_defconfig: 2 warnings
cm_x2xx_defconfig: 2 warnings
cm_x300_defconfig: 2 warnings
cns3420vb_defconfig: 2 warnings
colibri_pxa270_defconfig: 2 warnings
colibri_pxa300_defconfig: 2 warnings
collie_defconfig: 2 warnings
corgi_defconfig: 2 warnings
davinci_all_defconfig: 2 warnings
dove_defconfig: 2 warnings
ebsa110_defconfig: 2 warnings
efm32_defconfig: 2 warnings
em_x270_defconfig: 2 warnings
ep93xx_defconfig: 2 warnings
eseries_pxa_defconfig: 2 warnings
exynos_defconfig: 2 warnings
ezx_defconfig: 2 warnings
footbridge_defconfig: 2 warnings
h3600_defconfig: 2 warnings
h5000_defconfig: 2 warnings
hackkit_defconfig: 2 warnings
hisi_defconfig: 2 warnings
imote2_defconfig: 2 warnings
imx_v4_v5_defconfig: 2 warnings
imx_v6_v7_defconfig: 2 warnings
integrator_defconfig: 2 warnings
iop13xx_defconfig: 2 warnings
iop32x_defconfig: 2 warnings
iop33x_defconfig: 2 warnings
ixp4xx_defconfig: 2 warnings
jornada720_defconfig: 2 warnings
keystone_defconfig: 2 warnings
koelsch_defconfig: 2 warnings
ks8695_defconfig: 2 warnings
kzm9g_defconfig: 2 warnings
lager_defconfig: 2 warnings
lart_defconfig: 2 warnings
lpc32xx_defconfig: 2 warnings
lpd270_defconfig: 2 warnings
lubbock_defconfig: 2 warnings
mackerel_defconfig: 2 warnings
magician_defconfig: 2 warnings
mainstone_defconfig: 2 warnings
marzen_defconfig: 2 warnings
mini2440_defconfig: 2 warnings
mmp2_defconfig: 2 warnings
moxart_defconfig: 2 warnings
msm_defconfig: 2 warnings
multi_v5_defconfig: 2 warnings
multi_v7_defconfig: 2 warnings
mv78xx0_defconfig: 2 warnings
mvebu_v5_defconfig: 2 warnings
mvebu_v7_defconfig: 2 warnings
mxs_defconfig: 2 warnings
neponset_defconfig: 2 warnings
netwinder_defconfig: 2 warnings
netx_defconfig: 2 warnings
nhk8815_defconfig: 2 warnings
nuc910_defconfig: 2 warnings
nuc950_defconfig: 2 warnings
nuc960_defconfig: 2 warnings
omap1_defconfig: 2 warnings
omap2plus_defconfig: 2 warnings
orion5x_defconfig: 2 warnings
palmz72_defconfig: 2 warnings
pcm027_defconfig: 2 warnings
pleb_defconfig: 2 warnings
prima2_defconfig: 2 warnings
pxa168_defconfig: 2 warnings
pxa255-idp_defconfig: 2 warnings
pxa3xx_defconfig: 2 warnings
pxa910_defconfig: 2 warnings
qcom_defconfig: 2 warnings
raumfeld_defconfig: 2 warnings
realview-smp_defconfig: 2 warnings
realview_defconfig: 2 warnings
rpc_defconfig: 2 warnings
s3c2410_defconfig: 2 warnings
s3c6400_defconfig: 2 warnings
s5pv210_defconfig: 2 warnings
sama5_defconfig: 2 warnings
shannon_defconfig: 2 warnings
shmobile_defconfig: 2 warnings
simpad_defconfig: 2 warnings
socfpga_defconfig: 2 warnings
spear13xx_defconfig: 2 warnings
spear3xx_defconfig: 2 warnings
spear6xx_defconfig: 2 warnings
spitz_defconfig: 2 warnings
sunxi_defconfig: 2 warnings
tct_hammer_defconfig: 2 warnings
tegra_defconfig: 2 warnings
tinyconfig: 2 warnings
trizeps4_defconfig: 2 warnings
u300_defconfig: 2 warnings
u8500_defconfig: 2 warnings
versatile_defconfig: 2 warnings
vexpress_defconfig: 2 warnings
viper_defconfig: 2 warnings
vt8500_v6_v7_defconfig: 2 warnings
xcep_defconfig: 2 warnings
zeus_defconfig: 2 warnings
i386: gcc version 7.3.0 (Debian 7.3.0-30)
allnoconfig: 3 warnings
tinyconfig: 3 warnings
x86_64: gcc version 7.3.0 (Debian 7.3.0-30)
allnoconfig: 1 warning
tinyconfig: 1 warning
Errors summary:
2 arch/arc/mm/tlbex.S:348: Error: unknown opcode 'lsl'
2 arch/arc/mm/tlbex.S:291: Error: unknown opcode 'lsl'
Warnings summary:
663 arc-linux-gcc: warning: '-mno-mpy' is deprecated
654 cc1: warning: '-mno-mpy' is deprecated
128 scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
128 scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
2 mm/memory.c:581:7: warning: assignment makes integer from pointer without a cast [-Wint-conversion]
2 lib/string_helpers.c:64:33: warning: '%03lld' directive output may be truncated writing between 3 and 13 bytes into a region of size 7 [-Wformat-truncation=]
2 kernel/sched/core.c:2766:1: warning: control reaches end of non-void function [-Wreturn-type]
2 include/linux/kernel.h:707:17: warning: comparison of distinct pointer types lacks a cast
2 arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
2 arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
2 arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
1 mm/mmap.c:684:2: warning: 'rb_parent' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 mm/mmap.c:684:2: warning: 'rb_link' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 mm/mmap.c:683:2: warning: 'prev' may be used uninitialized in this function [-Wmaybe-uninitialized]
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
acs5k_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
acs5k_tiny_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
allnoconfig (x86_64) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
lib/string_helpers.c:64:33: warning: '%03lld' directive output may be truncated writing between 3 and 13 bytes into a region of size 7 [-Wformat-truncation=]
--------------------------------------------------------------------------------
allnoconfig (arm64) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
allnoconfig (i386) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
--------------------------------------------------------------------------------
allnoconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
allnoconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
allnoconfig (arc) — FAIL, 2 errors, 666 warnings, 0 section mismatches
Errors:
arch/arc/mm/tlbex.S:291: Error: unknown opcode 'lsl'
arch/arc/mm/tlbex.S:348: Error: unknown opcode 'lsl'
Warnings:
arc-linux-gcc: warning: '-mno-mpy' is deprecated
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
mm/memory.c:581:7: warning: assignment makes integer from pointer without a cast [-Wint-conversion]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
mm/mmap.c:684:2: warning: 'rb_link' may be used uninitialized in this function [-Wmaybe-uninitialized]
mm/mmap.c:684:2: warning: 'rb_parent' may be used uninitialized in this function [-Wmaybe-uninitialized]
mm/mmap.c:683:2: warning: 'prev' may be used uninitialized in this function [-Wmaybe-uninitialized]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
include/linux/kernel.h:707:17: warning: comparison of distinct pointer types lacks a cast
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
kernel/sched/core.c:2766:1: warning: control reaches end of non-void function [-Wreturn-type]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
--------------------------------------------------------------------------------
am200epdkit_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ape6evm_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ar7_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
armadillo800eva_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
assabet_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91_dt_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91rm9200_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9260_9g20_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9261_9g10_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9263_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9g45_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9rl_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91x40_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ath79_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
axm55xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
badge4_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
bcm2835_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
bcm47xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
bcm63xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
bcm_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
bigsur_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
bockw_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
capcella_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cavium_octeon_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cerfcube_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
clps711x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cm_x2xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cm_x300_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cns3420vb_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cobalt_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
colibri_pxa270_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
colibri_pxa300_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
collie_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
corgi_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
davinci_all_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
db1xxx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
decstation_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig (arm64) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
dove_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
e55_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ebsa110_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
efm32_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
em_x270_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ep93xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
eseries_pxa_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
exynos_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ezx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
footbridge_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
fuloong2e_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
gpr_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
h3600_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
h5000_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
hackkit_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
hisi_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
imote2_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
imx_v4_v5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
imx_v6_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
integrator_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
iop13xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
iop32x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
iop33x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ip22_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ip27_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ip28_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ip32_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ixp4xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
jazz_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
jmr3927_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
jornada720_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
keystone_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
koelsch_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ks8695_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
kzm9g_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lager_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lart_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lasat_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
lemote2f_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
loongson3_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
lpc32xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lpd270_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ls1b_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
lubbock_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mackerel_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
magician_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mainstone_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
malta_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
malta_kvm_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
malta_kvm_guest_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltaaprp_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltasmvp_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltasmvp_eva_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltaup_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
markeins_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
marzen_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mini2440_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mips_paravirt_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
mmp2_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
moxart_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mpc30x_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
msm_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
msp71xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
mtx1_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
multi_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mv78xx0_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mvebu_v5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mvebu_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mxs_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
neponset_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
netwinder_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
netx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nhk8815_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nlm_xlp_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nlm_xlr_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nuc910_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nuc950_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nuc960_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
omap1_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
omap2plus_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
orion5x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
palmz72_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pcm027_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pleb_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pnx8335_stb225_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
prima2_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa168_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa255-idp_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa3xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa910_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
qcom_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
qi_lb60_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
raumfeld_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
rb532_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
rbtx49xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
realview-smp_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
realview_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
rm200_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
rpc_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
rt305x_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
s3c2410_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
s3c6400_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
s5pv210_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
sama5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
sb1250_swarm_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
sead3_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
sead3micro_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
shannon_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
shmobile_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
simpad_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
socfpga_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spear13xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spear3xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spear6xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spitz_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
sunxi_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tb0219_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tb0226_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tb0287_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tct_hammer_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tegra_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tinyconfig (x86_64) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
lib/string_helpers.c:64:33: warning: '%03lld' directive output may be truncated writing between 3 and 13 bytes into a region of size 7 [-Wformat-truncation=]
--------------------------------------------------------------------------------
tinyconfig (i386) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
--------------------------------------------------------------------------------
tinyconfig (arm64) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tinyconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tinyconfig (arc) — FAIL, 2 errors, 664 warnings, 0 section mismatches
Errors:
arch/arc/mm/tlbex.S:291: Error: unknown opcode 'lsl'
arch/arc/mm/tlbex.S:348: Error: unknown opcode 'lsl'
Warnings:
arc-linux-gcc: warning: '-mno-mpy' is deprecated
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
kernel/sched/core.c:2766:1: warning: control reaches end of non-void function [-Wreturn-type]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
mm/memory.c:581:7: warning: assignment makes integer from pointer without a cast [-Wint-conversion]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
include/linux/kernel.h:707:17: warning: comparison of distinct pointer types lacks a cast
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
--------------------------------------------------------------------------------
tinyconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
trizeps4_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
u300_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
u8500_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
versatile_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
vexpress_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
viper_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
vt8500_v6_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
workpad_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
xcep_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
xway_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
zeus_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
---
For more info write to <info(a)kernelci.org>
Greg,
Attached are 2 more patches backported for 4.9 adjusted for context.
This allows Android to drop two more out of tree patches that already
landed further upstream. I did a quick build test locally.
They are needed for 4.4 as well. The mbox doesn't apply cleanly, so I
will resolve that and send them for 4.4 tomorrow.
--
Thanks,
~Nick Desaulniers
> From: Sasha Levin <sashal(a)kernel.org>
> Sent: Monday, December 3, 2018 6:16 AM
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 8195b1396ec8 hv_netvsc: fix deadlock on hotplug.
>
> The bot has tested the following trees: v4.19.6, v4.14.85,
>
> v4.19.6: Build OK!
> v4.14.85: Failed to apply! Possible dependencies:
> 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
> vmbus_process_offer()")
> c2e5df616e1a ("vmbus: add per-channel sysfs info")
>
> How should we proceed with this patch?
> Sasha
BTW, the patch went into char-misc.git's char-misc-linus branch 13 hours ago:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two workqueues")
linux-4.14.y (v4.14.85) lacks c2e5df616e1a ("vmbus: add per-channel sysfs info")
and the other related patches so this patch can't apply cleanly.
I suggest we cherry-pick all the related patches to linux-4.14.y in this order:
(Note: 37c2578c0c40 is in char-misc.git's char-misc-linus branch and is not in Linus's tree yet)
c2e5df616e1a ("vmbus: add per-channel sysfs info")
869b5567e12f ("vmbus: unregister device_obj->channels_kset")
6712cc9c2211 ("vmbus: don't return values for uninitalized channels")
50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in vmbus_process_offer()")
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two workqueues")
Alternatively, we can skip c2e5df616e1a ("vmbus: add per-channel sysfs info"), and then
please use the attached rebased patch for v4.14.85.
I prefer the first solution.
Thanks,
-- Dexuan
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From 43a1b0cb4cd6dbfd3cd9c10da663368394d299d8 Mon Sep 17 00:00:00 2001
From: Masami Hiramatsu <mhiramat(a)kernel.org>
Date: Fri, 24 Aug 2018 02:16:12 +0900
Subject: [PATCH] kprobes/x86: Fix instruction patching corruption when copying
more than one RIP-relative instruction
After copy_optimized_instructions() copies several instructions
to the working buffer it tries to fix up the real RIP address, but it
adjusts the RIP-relative instruction with an incorrect RIP address
for the 2nd and subsequent instructions due to a bug in the logic.
This will break the kernel pretty badly (with likely outcomes such as
a kernel freeze, a crash, or worse) because probed instructions can refer
to the wrong data.
For example putting kprobes on cpumask_next() typically hits this bug.
cpumask_next() is normally like below if CONFIG_CPUMASK_OFFSTACK=y
(in this case nr_cpumask_bits is an alias of nr_cpu_ids):
<cpumask_next>:
48 89 f0 mov %rsi,%rax
8b 35 7b fb e2 00 mov 0xe2fb7b(%rip),%esi # ffffffff82db9e64 <nr_cpu_ids>
55 push %rbp
...
If we put a kprobe on it and it gets jump-optimized, it gets
patched by the kprobes code like this:
<cpumask_next>:
e9 95 7d 07 1e jmpq 0xffffffffa000207a
7b fb jnp 0xffffffff81f8a2e2 <cpumask_next+2>
e2 00 loop 0xffffffff81f8a2e9 <cpumask_next+9>
55 push %rbp
This shows that the first two MOV instructions were copied to a
trampoline buffer at 0xffffffffa000207a.
Here is the disassembled result of the trampoline, skipping
the optprobe template instructions:
# Dump of assembly code from 0xffffffffa000207a to 0xffffffffa00020ea:
54 push %rsp
...
48 83 c4 08 add $0x8,%rsp
9d popfq
48 89 f0 mov %rsi,%rax
8b 35 82 7d db e2 mov -0x1d24827e(%rip),%esi # 0xffffffff82db9e67 <nr_cpu_ids+3>
This dump shows that the second MOV accesses *(nr_cpu_ids+3) instead of
the original *nr_cpu_ids. This leads to a kernel freeze because
cpumask_next() always returns 0 and for_each_cpu() never ends.
Fix this by adding 'len' correctly to the real RIP address while
copying.
[ mingo: Improved the changelog. ]
Reported-by: Michael Rodin <michael(a)rodin.online>
Signed-off-by: Masami Hiramatsu <mhiramat(a)kernel.org>
Reviewed-by: Steven Rostedt (VMware) <rostedt(a)goodmis.org>
Cc: Arnaldo Carvalho de Melo <acme(a)kernel.org>
Cc: Linus Torvalds <torvalds(a)linux-foundation.org>
Cc: Peter Zijlstra <peterz(a)infradead.org>
Cc: Ravi Bangoria <ravi.bangoria(a)linux.ibm.com>
Cc: Steven Rostedt <rostedt(a)goodmis.org>
Cc: Thomas Gleixner <tglx(a)linutronix.de>
Cc: stable(a)vger.kernel.org # v4.15+
Fixes: 63fef14fc98a ("kprobes/x86: Make insn buffer always ROX and use text_poke()")
Link: http://lkml.kernel.org/r/153504457253.22602.1314289671019919596.stgit@devbox
Signed-off-by: Ingo Molnar <mingo(a)kernel.org>
diff --git a/arch/x86/kernel/kprobes/opt.c b/arch/x86/kernel/kprobes/opt.c
index 40b16b270656..6adf6e6c2933 100644
--- a/arch/x86/kernel/kprobes/opt.c
+++ b/arch/x86/kernel/kprobes/opt.c
@@ -189,7 +189,7 @@ static int copy_optimized_instructions(u8 *dest, u8 *src, u8 *real)
int len = 0, ret;
while (len < RELATIVEJUMP_SIZE) {
- ret = __copy_instruction(dest + len, src + len, real, &insn);
+ ret = __copy_instruction(dest + len, src + len, real + len, &insn);
if (!ret || !can_boost(&insn, src + len))
return -EINVAL;
len += ret;
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From 2189463dba3eac10d7264a40ede12fc1a3c06fb1 Mon Sep 17 00:00:00 2001
From: Robert Foss <robert.foss(a)collabora.com>
Date: Mon, 5 Nov 2018 11:13:12 +0100
Subject: [PATCH] drm/msm: Move fence put to where failure occurs
If dma_fence_wait fails to wait for a supplied in-fence in
msm_ioctl_gem_submit, make sure we release that in-fence.
Also remove this dma_fence_put() from the 'out' label.
Signed-off-by: Robert Foss <robert.foss(a)collabora.com>
Reviewed-by: Chris Wilson <chris(a)chris-wilson.co.uk>
Cc: stable(a)vger.kernel.org
Signed-off-by: Rob Clark <robdclark(a)gmail.com>
Signed-off-by: Sean Paul <seanpaul(a)chromium.org>
diff --git a/drivers/gpu/drm/msm/msm_gem_submit.c b/drivers/gpu/drm/msm/msm_gem_submit.c
index 66673ea9bf6f..6942604ad9a8 100644
--- a/drivers/gpu/drm/msm/msm_gem_submit.c
+++ b/drivers/gpu/drm/msm/msm_gem_submit.c
@@ -413,7 +413,6 @@ int msm_ioctl_gem_submit(struct drm_device *dev, void *data,
struct msm_file_private *ctx = file->driver_priv;
struct msm_gem_submit *submit;
struct msm_gpu *gpu = priv->gpu;
- struct dma_fence *in_fence = NULL;
struct sync_file *sync_file = NULL;
struct msm_gpu_submitqueue *queue;
struct msm_ringbuffer *ring;
@@ -446,6 +445,8 @@ int msm_ioctl_gem_submit(struct drm_device *dev, void *data,
ring = gpu->rb[queue->prio];
if (args->flags & MSM_SUBMIT_FENCE_FD_IN) {
+ struct dma_fence *in_fence;
+
in_fence = sync_file_get_fence(args->fence_fd);
if (!in_fence)
@@ -455,11 +456,13 @@ int msm_ioctl_gem_submit(struct drm_device *dev, void *data,
* Wait if the fence is from a foreign context, or if the fence
* array contains any fence from a foreign context.
*/
- if (!dma_fence_match_context(in_fence, ring->fctx->context)) {
+ ret = 0;
+ if (!dma_fence_match_context(in_fence, ring->fctx->context))
ret = dma_fence_wait(in_fence, true);
- if (ret)
- return ret;
- }
+
+ dma_fence_put(in_fence);
+ if (ret)
+ return ret;
}
ret = mutex_lock_interruptible(&dev->struct_mutex);
@@ -585,8 +588,6 @@ int msm_ioctl_gem_submit(struct drm_device *dev, void *data,
}
out:
- if (in_fence)
- dma_fence_put(in_fence);
submit_cleanup(submit);
if (ret)
msm_gem_submit_free(submit);
From: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
[for older kernels only, atomisp has been removed from upstream]
gcc-8 rightfully warns that this instance of strncpy is just copying
from the source, to the same source, for a few bytes. Meaning this call
does nothing. As the author of the code obviously meant it to do
something, but this code must be working properly, just replace the call
to the kernel internal strscpy() which gcc doesn't know about, so the
warning goes away.
As this driver was deleted from newer kernel versions, none of this
really matters but now at least we do not have to worry about a build
warning in the stable trees.
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/debug/src/ia_css_debug.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
--- a/drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/debug/src/ia_css_debug.c
+++ b/drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/debug/src/ia_css_debug.c
@@ -2860,9 +2860,7 @@ ia_css_debug_pipe_graph_dump_stage(
if (l <= ENABLE_LINE_MAX_LENGTH) {
/* It fits on one line, copy string and init */
/* other helper strings with empty string */
- strcpy_s(enable_info,
- sizeof(enable_info),
- ei);
+ strscpy(enable_info, ei, sizeof(enable_info));
} else {
/* Too big for one line, find last comma */
p = ENABLE_LINE_MAX_LENGTH;
From: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
[for older kernels only, lustre has been removed from upstream]
When someone writes:
strncpy(dest, source, sizeof(source));
they really are just doing the same thing as:
strcpy(dest, source);
but somehow they feel better because they are now using the "safe"
version of the string functions. Cargo-cult programming at its
finest...
gcc-8 rightfully warns you about doing foolish things like this. Now
that the stable kernels are all starting to be built using gcc-8, let's
get rid of this warning so that we do not have to gaze at this horror.
To dropt the warning, just convert the code to using strcpy() so that if
someone really wants to audit this code and find all of the obvious
problems, it will be easier to do so.
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/staging/lustre/lnet/lnet/config.c | 3 +--
drivers/staging/lustre/lustre/lmv/lmv_obd.c | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
--- a/drivers/staging/lustre/lnet/lnet/config.c
+++ b/drivers/staging/lustre/lnet/lnet/config.c
@@ -354,8 +354,7 @@ lnet_parse_networks(struct list_head *ni
CERROR("Can't allocate net interface name\n");
goto failed;
}
- strncpy(ni->ni_interfaces[niface], iface,
- strlen(iface));
+ strcpy(ni->ni_interfaces[niface], iface);
niface++;
iface = comma;
} while (iface);
--- a/drivers/staging/lustre/lustre/lmv/lmv_obd.c
+++ b/drivers/staging/lustre/lustre/lmv/lmv_obd.c
@@ -645,7 +645,7 @@ repeat_fid2path:
memmove(ptr + strlen(gf->gf_path) + 1, ptr,
strlen(ori_gf->gf_path));
- strncpy(ptr, gf->gf_path, strlen(gf->gf_path));
+ strcpy(ptr, gf->gf_path);
ptr += strlen(gf->gf_path);
*ptr = '/';
}
We recently addressed a VMID generation race by introducing a read/write
lock around accesses and updates to the vmid generation values.
However, kvm_arch_vcpu_ioctl_run() also calls need_new_vmid_gen() but
does so without taking the read lock.
As far as I can tell, this can lead to the same kind of race:
VM 0, VCPU 0 VM 0, VCPU 1
------------ ------------
update_vttbr (vmid 254)
update_vttbr (vmid 1) // roll over
read_lock(kvm_vmid_lock);
force_vm_exit()
local_irq_disable
need_new_vmid_gen == false //because vmid gen matches
enter_guest (vmid 254)
kvm_arch.vttbr = <PGD>:<VMID 1>
read_unlock(kvm_vmid_lock);
enter_guest (vmid 1)
Which results in running two VCPUs in the same VM with different VMIDs
and (even worse) other VCPUs from other VMs could now allocate clashing
VMID 254 from the new generation as long as VCPU 0 is not exiting.
Attempt to solve this by making sure vttbr is updated before another CPU
can observe the updated VMID generation.
Cc: stable(a)vger.kernel.org
Fixes: f0cf47d939d0 "KVM: arm/arm64: Close VMID generation race"
Reviewed-by: Julien Thierry <julien.thierry(a)arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall(a)arm.com>
---
virt/kvm/arm/arm.c | 23 +++++++++++------------
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/virt/kvm/arm/arm.c b/virt/kvm/arm/arm.c
index 23774970c9df..abcd29db2d7a 100644
--- a/virt/kvm/arm/arm.c
+++ b/virt/kvm/arm/arm.c
@@ -66,7 +66,7 @@ static DEFINE_PER_CPU(struct kvm_vcpu *, kvm_arm_running_vcpu);
static atomic64_t kvm_vmid_gen = ATOMIC64_INIT(1);
static u32 kvm_next_vmid;
static unsigned int kvm_vmid_bits __read_mostly;
-static DEFINE_RWLOCK(kvm_vmid_lock);
+static DEFINE_SPINLOCK(kvm_vmid_lock);
static bool vgic_present;
@@ -484,7 +484,9 @@ void force_vm_exit(const cpumask_t *mask)
*/
static bool need_new_vmid_gen(struct kvm *kvm)
{
- return unlikely(kvm->arch.vmid_gen != atomic64_read(&kvm_vmid_gen));
+ u64 current_vmid_gen = atomic64_read(&kvm_vmid_gen);
+ smp_rmb(); /* Orders read of kvm_vmid_gen and kvm->arch.vmid */
+ return unlikely(READ_ONCE(kvm->arch.vmid_gen) != current_vmid_gen);
}
/**
@@ -499,16 +501,11 @@ static void update_vttbr(struct kvm *kvm)
{
phys_addr_t pgd_phys;
u64 vmid, cnp = kvm_cpu_has_cnp() ? VTTBR_CNP_BIT : 0;
- bool new_gen;
- read_lock(&kvm_vmid_lock);
- new_gen = need_new_vmid_gen(kvm);
- read_unlock(&kvm_vmid_lock);
-
- if (!new_gen)
+ if (!need_new_vmid_gen(kvm))
return;
- write_lock(&kvm_vmid_lock);
+ spin_lock(&kvm_vmid_lock);
/*
* We need to re-check the vmid_gen here to ensure that if another vcpu
@@ -516,7 +513,7 @@ static void update_vttbr(struct kvm *kvm)
* use the same vmid.
*/
if (!need_new_vmid_gen(kvm)) {
- write_unlock(&kvm_vmid_lock);
+ spin_unlock(&kvm_vmid_lock);
return;
}
@@ -539,7 +536,6 @@ static void update_vttbr(struct kvm *kvm)
kvm_call_hyp(__kvm_flush_vm_context);
}
- kvm->arch.vmid_gen = atomic64_read(&kvm_vmid_gen);
kvm->arch.vmid = kvm_next_vmid;
kvm_next_vmid++;
kvm_next_vmid &= (1 << kvm_vmid_bits) - 1;
@@ -550,7 +546,10 @@ static void update_vttbr(struct kvm *kvm)
vmid = ((u64)(kvm->arch.vmid) << VTTBR_VMID_SHIFT) & VTTBR_VMID_MASK(kvm_vmid_bits);
kvm->arch.vttbr = kvm_phys_to_vttbr(pgd_phys) | vmid | cnp;
- write_unlock(&kvm_vmid_lock);
+ smp_wmb();
+ WRITE_ONCE(kvm->arch.vmid_gen, atomic64_read(&kvm_vmid_gen));
+
+ spin_unlock(&kvm_vmid_lock);
}
static int kvm_vcpu_first_run_init(struct kvm_vcpu *vcpu)
--
2.18.0
When restoring the active state from userspace, we don't know which CPU
was the source for the active state, and this is not architecturally
exposed in any of the register state.
Set the active_source to 0 in this case. In the future, we can expand
on this and exposse the information as additional information to
userspace for GICv2 if anyone cares.
Cc: stable(a)vger.kernel.org
Signed-off-by: Christoffer Dall <christoffer.dall(a)arm.com>
---
virt/kvm/arm/vgic/vgic-mmio.c | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/virt/kvm/arm/vgic/vgic-mmio.c b/virt/kvm/arm/vgic/vgic-mmio.c
index f56ff1cf52ec..2b450d49a046 100644
--- a/virt/kvm/arm/vgic/vgic-mmio.c
+++ b/virt/kvm/arm/vgic/vgic-mmio.c
@@ -338,11 +338,26 @@ static void vgic_mmio_change_active(struct kvm_vcpu *vcpu, struct vgic_irq *irq,
vgic_hw_irq_change_active(vcpu, irq, active, !requester_vcpu);
} else {
u32 model = vcpu->kvm->arch.vgic.vgic_model;
+ u8 active_source;
irq->active = active;
+
+ /*
+ * The GICv2 architecture indicates that the source CPUID for
+ * an SGI should be provided during an EOI which implies that
+ * the active state is stored somewhere, but at the same time
+ * this state is not architecturally exposed anywhere and we
+ * have no way of knowing the right source.
+ *
+ * This may lead to a VCPU not being able to receive
+ * additional instances of a particular SGI after migration
+ * for a GICv2 VM on some GIC implementations. Oh well.
+ */
+ active_source = (requester_vcpu) ? requester_vcpu->vcpu_id : 0;
+
if (model == KVM_DEV_TYPE_ARM_VGIC_V2 &&
active && vgic_irq_is_sgi(irq->intid))
- irq->active_source = requester_vcpu->vcpu_id;
+ irq->active_source = active_source;
}
if (irq->active)
--
2.18.0
On Sun, Dec 09, 2018 at 03:21:00PM +0000, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v4.19.8, v4.14.87, v4.9.144, v4.4.166, v3.18.128,
>
> v4.19.8: Build OK!
> v4.14.87: Build OK!
> v4.9.144: Build OK!
> v4.4.166: Build OK!
> v3.18.128: Failed to apply! Possible dependencies:
> 5d03a2fd2292 ("USB: serial: option: add device ID for HP lt2523 (Novatel E371)")
I thought 3.18 was finally EOLed?
> How should we proceed with this patch?
It applies just fine to mainline, but looks like your scripts found a
missing stable patch which would also make it apply to 3.18 without the
need to adjust any context.
Thanks,
Johan
On Mon, 10 Dec 2018, Sasha Levin wrote:
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v4.19.8, v4.14.87, v4.9.144, v4.4.166, v3.18.128,
>
> v4.19.8: Build OK!
> v4.14.87: Build OK!
> v4.9.144: Build failed! Errors:
> kernel/futex.c:1186:28: error: ???uaddr??? undeclared (first use in this function)
>
> v4.4.166: Build failed! Errors:
> kernel/futex.c:1181:28: error: ???uaddr??? undeclared (first use in this function)
>
> v3.18.128: Build failed! Errors:
> kernel/futex.c:1103:28: error: ???uaddr??? undeclared (first use in this function)
>
> How should we proceed with this patch?
I'll look into that once this is sorted... I so love these rotten kernels.
Thanks,
tglx
The driver adds different MFD child devices via mfd_add_devices() and
hence it is required to call mfd_remove_devices() to remove MFD child
devices.
Fixes: 5e0115581bbc ("cros_ec: Move cros_ec_dev module to drivers/mfd")
Cc: stable(a)vger.kernel.org
Signed-off-by: Enric Balletbo i Serra <enric.balletbo(a)collabora.com>
---
Hi Lee,
I saw that you send a mfd-fixes pull request this morning, so sorry in
advance for sending this too late. This was broken since the driver
moved from platform/chrome to mfd (and probably before that), so
it's an old problem. Note that I plan to send a patch series that depends
on this to apply cleanly. If the patch is fine with you and there is any
possibility to go in this version that will be good, if not, let me know
if you prefer queue this in your for-next branch or if you prefer I
include the patch on the series I plan to send on top of it to not mess
things.
Thanks,
Enric
drivers/mfd/cros_ec_dev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mfd/cros_ec_dev.c b/drivers/mfd/cros_ec_dev.c
index b99a194ce5a4..2d0fee488c5a 100644
--- a/drivers/mfd/cros_ec_dev.c
+++ b/drivers/mfd/cros_ec_dev.c
@@ -499,6 +499,7 @@ static int ec_device_remove(struct platform_device *pdev)
cros_ec_debugfs_remove(ec);
+ mfd_remove_devices(ec->dev);
cdev_del(&ec->cdev);
device_unregister(&ec->class_dev);
return 0;
--
2.19.2
The only users of free_spa() are alloc_link() and free_link(), and
in both cases:
- link->spa != NULL
- free_spa(link) is immediatly followed by kfree(link)
The check isn't needed, and it doesn't bring much to clear the link->spa
pointer. Drop both.
Signed-off-by: Greg Kurz <groug(a)kaod.org>
---
drivers/misc/ocxl/link.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/misc/ocxl/link.c b/drivers/misc/ocxl/link.c
index 31695a078485..eed92055184d 100644
--- a/drivers/misc/ocxl/link.c
+++ b/drivers/misc/ocxl/link.c
@@ -352,11 +352,8 @@ static void free_spa(struct link *link)
pr_debug("Freeing SPA for %x:%x:%x\n", link->domain, link->bus,
link->dev);
- if (spa && spa->spa_mem) {
- free_pages((unsigned long) spa->spa_mem, spa->spa_order);
- kfree(spa);
- link->spa = NULL;
- }
+ free_pages((unsigned long) spa->spa_mem, spa->spa_order);
+ kfree(spa);
}
static int alloc_link(struct pci_dev *dev, int PE_mask, struct link **out_link)
The patch titled
Subject: panic: Avoid the extra noise dmesg
has been added to the -mm tree. Its filename is
panic-avoid-the-extra-noise-dmesg.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/panic-avoid-the-extra-noise-dmesg.…
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/panic-avoid-the-extra-noise-dmesg.…
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Feng Tang <feng.tang(a)intel.com>
Subject: panic: Avoid the extra noise dmesg
When kernel panic happens, it will first print the panic call stack,
then the ending msg like:
[ 35.743249] ---[ end Kernel panic - not syncing: Fatal exception
[ 35.749975] ------------[ cut here ]------------
The above message are very useful for debugging.
But if system is configured to not reboot on panic, say the "panic_timeout"
parameter equals 0, it will likely print out many noisy message like
WARN() call stack for each and every CPU except the panic one, messages
like below:
WARNING: CPU: 1 PID: 280 at kernel/sched/core.c:1198 set_task_cpu+0x183/0x190
Call Trace:
<IRQ>
try_to_wake_up
default_wake_function
autoremove_wake_function
__wake_up_common
__wake_up_common_lock
__wake_up
wake_up_klogd_work_func
irq_work_run_list
irq_work_tick
update_process_times
tick_sched_timer
__hrtimer_run_queues
hrtimer_interrupt
smp_apic_timer_interrupt
apic_timer_interrupt
For people working in console mode, the screen will first show the panic
call stack, but immediately overridded by these noisy extra messages, which
makes debugging much more difficult, as the original context gets lost on
screen.
Also these noisy messages will confuse some users, as I have seen many bug
reporters posted the noisy message into bugzilla, instead of the real panic
call stack and context.
Removing the "local_irq_enable" will avoid the noisy message.
The justification for the removing is: when code runs to this point, it
means user has chosed to not reboot, or do any special handling by using
the panic notifier method, no much point in re-enabling the interrupt.
Link: http://lkml.kernel.org/r/1543902228-23834-1-git-send-email-feng.tang@intel.…
Signed-off-by: Feng Tang <feng.tang(a)intel.com>
Cc: Thomas Gleixner <tglx(a)linutronix.de>
Cc: Kees Cook <keescook(a)chromium.org>
Cc: Borislav Petkov <bp(a)suse.de>
Cc: Petr Mladek <pmladek(a)suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky(a)gmail.com>
Cc: <stable(a)vger.kernel.org>
Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org>
---
--- a/kernel/panic.c~panic-avoid-the-extra-noise-dmesg
+++ a/kernel/panic.c
@@ -322,7 +322,6 @@ void panic(const char *fmt, ...)
}
#endif
pr_emerg("---[ end Kernel panic - not syncing: %s ]---\n", buf);
- local_irq_enable();
for (i = 0; ; i += PANIC_TIMER_STEP) {
touch_softlockup_watchdog();
if (i >= i_next) {
_
Patches currently in -mm which might be from feng.tang(a)intel.com are
panic-add-options-to-print-system-info-when-panic-happens.patch
kernel-sysctl-add-panic_print-into-sysctl.patch
panic-avoid-the-extra-noise-dmesg.patch
The double word returned by read_afu_info(OCXL_DVSEC_TEMPL_NAME) contains
four characters of the AFU name, read from the PCI config space, hence
with a little-endian ordering. When composing the string, a big-endian
system must swap the bytes so that the characters appear in the right
order.
Do this with le32_to_cpu().
Signed-off-by: Greg Kurz <groug(a)kaod.org>
---
drivers/misc/ocxl/config.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/ocxl/config.c b/drivers/misc/ocxl/config.c
index 57a6bb1fd3c9..b76198ba8630 100644
--- a/drivers/misc/ocxl/config.c
+++ b/drivers/misc/ocxl/config.c
@@ -318,7 +318,7 @@ static int read_afu_name(struct pci_dev *dev, struct ocxl_fn_config *fn,
if (rc)
return rc;
ptr = (u32 *) &afu->name[i];
- *ptr = val;
+ *ptr = le32_to_cpu(val);
}
afu->name[OCXL_AFU_NAME_SZ - 1] = '\0'; /* play safe */
return 0;
The old code always starts from fixed port for VMADDR_PORT_ANY. Sometimes
when VMM crashed, there is still orphaned vsock which is waiting for
close timer, then it could cause connection time out for new started VM
if they are trying to connect to same port with same guest cid since the
new packets could hit that orphaned vsock. We could also fix this by doing
more in vhost_vsock_reset_orphans, but any way, it should be better to start
from a random local port instead of a fixed one.
Signed-off-by: Lepton Wu <ytht.net(a)gmail.com>
---
net/vmw_vsock/af_vsock.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/net/vmw_vsock/af_vsock.c b/net/vmw_vsock/af_vsock.c
index ab27a2872935..73817e846a1f 100644
--- a/net/vmw_vsock/af_vsock.c
+++ b/net/vmw_vsock/af_vsock.c
@@ -107,6 +107,7 @@
#include <linux/mutex.h>
#include <linux/net.h>
#include <linux/poll.h>
+#include <linux/random.h>
#include <linux/skbuff.h>
#include <linux/smp.h>
#include <linux/socket.h>
@@ -504,9 +505,12 @@ static void vsock_pending_work(struct work_struct *work)
static int __vsock_bind_stream(struct vsock_sock *vsk,
struct sockaddr_vm *addr)
{
- static u32 port = LAST_RESERVED_PORT + 1;
+ static u32 port = 0;
struct sockaddr_vm new_addr;
+ if (!port)
+ port = prandom_u32();
+
vsock_addr_init(&new_addr, addr->svm_cid, addr->svm_port);
if (addr->svm_port == VMADDR_PORT_ANY) {
--
2.20.0.rc2.403.gdbc3b29805-goog
I ran into a link-time error with the atmel-quadspi driver on the
EBSA110 platform:
drivers/mtd/built-in.o: In function `atmel_qspi_run_command':
:(.text+0x1ee3c): undefined reference to `_memcpy_toio'
:(.text+0x1ee48): undefined reference to `_memcpy_fromio'
The problem is that _memcpy_toio/_memcpy_fromio are not available on
that platform, and we have to prevent building the driver there.
In case we want to backport this to older kernels: between linux-4.8
and linux-4.20, the Kconfig entry was in drivers/mtd/spi-nor/Kconfig
but had the same problem.
Link: https://lore.kernel.org/patchwork/patch/812860/
Fixes: 161aaab8a067 ("mtd: atmel-quadspi: add driver for Atmel QSPI controller")
Cc: stable(a)vger.kernel.org
Signed-off-by: Arnd Bergmann <arnd(a)arndb.de>
---
drivers/spi/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index 55d5ffb50750..9f89cb134549 100644
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -93,7 +93,7 @@ config SPI_AT91_USART
config SPI_ATMEL_QUADSPI
tristate "Atmel Quad SPI Controller"
- depends on ARCH_AT91 || (ARM && COMPILE_TEST)
+ depends on ARCH_AT91 || (ARM && COMPILE_TEST && !ARCH_EBSA110)
depends on OF && HAS_IOMEM
help
This enables support for the Quad SPI controller in master mode.
--
2.18.0
Hi Sasha,
On Tue, Dec 11, 2018 at 2:42 AM Sasha Levin <sashal(a)kernel.org> wrote:
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v4.19.8, v4.14.87, v4.9.144, v4.4.166, v3.18.128,
>
> v4.19.8: Build OK!
> v4.14.87: Failed to apply! Possible dependencies:
> 4fd0b46e8987 ("slab, slub, slob: convert slab_flags_t to 32-bit")
> a3ba07444782 ("mm/slab.c: only set __GFP_RECLAIMABLE once")
> d50112edde1d ("slab, slub, slob: add slab_flags_t")
>
> v4.9.144: Failed to apply! Possible dependencies:
> 04d348ae3f0a ("drm/i915/gvt: vGPU display virtualization")
> 12d14cc43b34 ("drm/i915/gvt: Introduce a framework for tracking HW registers.")
> 1b36595ffb35 ("drm/i915: Show RING registers through debugfs")
> 28a60dee2ce6 ("drm/i915/gvt: vGPU HW resource management")
> 3f728236c516 ("drm/i915/gvt: trace stub")
> 4fd0b46e8987 ("slab, slub, slob: convert slab_flags_t to 32-bit")
> 579cea5f30f2 ("drm/i915/gvt: golden virtual HW state management")
> 5f0d5a3ae7cf ("mm: Rename SLAB_DESTROY_BY_RCU to SLAB_TYPESAFE_BY_RCU")
> 73cb97010d4f ("drm/i915: Combine seqno + tracking into a global timeline struct")
> 82d375d1b568 ("drm/i915/gvt: Introduce basic vGPU life cycle management")
> 8453d674ae7e ("drm/i915/gvt: vGPU execlist virtualization")
> a933568eb61d ("drm/i915: Tidy slab cache allocations")
> c8fe6a6811a7 ("drm/i915/gvt: vGPU interrupt virtualization.")
> d50112edde1d ("slab, slub, slob: add slab_flags_t")
> e39c5add3221 ("drm/i915/gvt: vGPU MMIO virtualization")
> e473405783c0 ("drm/i915/gvt: vGPU workload scheduler")
> e95433c73a11 ("drm/i915: Rearrange i915_wait_request() accounting with callers")
>
> v4.4.166: Failed to apply! Possible dependencies:
> 10b2e9e8e808 ("mm/slab: factor out debugging initialization in cache_init_objs()")
> 40b44137971c ("mm/slab: clean up DEBUG_PAGEALLOC processing code")
> 4fd0b46e8987 ("slab, slub, slob: convert slab_flags_t to 32-bit")
> 505f5dcb1c41 ("mm, kasan: add GFP flags to KASAN API")
> 55834c59098d ("mm: kasan: initial memory quarantine implementation")
> 5d097056c9a0 ("kmemcg: account certain kmem allocations to memcg")
> 7ed2f9e66385 ("mm, kasan: SLAB support")
> 832a15d209cd ("mm/slab: align cache size first before determination of OFF_SLAB candidate")
> a307ebd468e0 ("mm/slab: activate debug_pagealloc in SLAB when it is actually enabled")
> d50112edde1d ("slab, slub, slob: add slab_flags_t")
>
> v3.18.128: Failed to apply! Possible dependencies:
> 081fa9dffcde ("staging/lustre/llite: remove llite proc root on init failure")
> 12cf89b550d1 ("livepatch: rename config to CONFIG_LIVEPATCH")
> 13d1cf7e7025 ("livepatch: samples: add sample live patching module")
> 31e7213ab21e ("drivers: staging: lustre: Fix "spaces required around that '='" errors")
> 32b7eb877165 ("livepatch: change ARCH_HAVE_LIVE_PATCHING to HAVE_LIVE_PATCHING")
> 4fd0b46e8987 ("slab, slub, slob: convert slab_flags_t to 32-bit")
> 5aaeb5c01c5b ("x86/fpu, sched: Introduce CONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT and use it on x86")
> 5d097056c9a0 ("kmemcg: account certain kmem allocations to memcg")
> 6471b825c41e ("x86/kconfig: Reorganize arch feature Kconfig select's")
> 6e0a0ea12962 ("ACPI / sleep: Introduce CONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT")
> 83ac237a950e ("livepatch: kconfig: use bool instead of boolean")
> 957e3facd147 ("gcov: enable GCOV_PROFILE_ALL from ARCH Kconfigs")
> b700e7f03df5 ("livepatch: kernel: add support for live patching")
> b9dfe0bed999 ("livepatch: handle ancient compilers with more grace")
> d50112edde1d ("slab, slub, slob: add slab_flags_t")
>
>
> How should we proceed with this patch?
I'm not sure how we need to handle this.
2/3 in this series (https://patchwork.kernel.org/patch/10720495/) is
the patch that matters, and has correct Fixes/Cc tag (this only needs
to apply >=4.15).
I added Cc: stable@ to this patch, as it is a dependency of 2/3.
Should I remove Cc: stable from this patch? Or add Fixes: line?
Thanks,
Nicolas
> --
> Thanks,
> Sasha
The following commit introduced a regression on my system.
124049decbb121ec32742c94fb5d9d6bed8f24d8
x86/e820: put !E820_TYPE_RAM regions into memblock.reserved
and it was backported to stable, stopping the kernel to boot on my system since around 4.17.4.
It was reverted on upstream a couple months ago.
commit 2a5bda5a624d6471d25e953b9adba5182ab1b51f upstream
There are some other modifications to the file after that. However, at the very least, can
the revert be backported?
I think the original patch tries to fix a previous bug, so probably the latest commits fixed that
one correctly and need to be backported as well.
The patch titled
Subject: lib/test_debug_virtual.c: fix build failure
has been added to the -mm tree. Its filename is
lib-fix-build-failure-in-config_debug_virtual-test.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/lib-fix-build-failure-in-config_de…
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/lib-fix-build-failure-in-config_de…
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Christophe Leroy <christophe.leroy(a)c-s.fr>
Subject: lib/test_debug_virtual.c: fix build failure
On several arches, virt_to_phys() is in io.h
Build fails without it:
CC lib/test_debug_virtual.o
lib/test_debug_virtual.c: In function 'test_debug_virtual_init':
lib/test_debug_virtual.c:26:7: error: implicit declaration of function 'virt_to_phys' [-Werror=implicit-function-declaration]
pa = virt_to_phys(va);
^
Link: http://lkml.kernel.org/r/40d63adb6058b1fbb4082ca6f15225cb6e76bd62.154442917…
Fixes: e4dace361552 ("lib: add test module for CONFIG_DEBUG_VIRTUAL")
Signed-off-by: Christophe Leroy <christophe.leroy(a)c-s.fr>
Reviewed-by: Kees Cook <keescook(a)chromium.org>
Cc: Colin King <colin.king(a)canonical.com>
Cc: <stable(a)vger.kernel.org>
Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org>
---
--- a/lib/test_debug_virtual.c~lib-fix-build-failure-in-config_debug_virtual-test
+++ a/lib/test_debug_virtual.c
@@ -5,6 +5,7 @@
#include <linux/vmalloc.h>
#include <linux/slab.h>
#include <linux/sizes.h>
+#include <linux/io.h>
#include <asm/page.h>
#ifdef CONFIG_MIPS
_
Patches currently in -mm which might be from christophe.leroy(a)c-s.fr are
lib-fix-build-failure-in-config_debug_virtual-test.patch
The patch below does not apply to the 4.19-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From 13682e524167cbd7e2a26c5e91bec765f0f96273 Mon Sep 17 00:00:00 2001
From: Daniel Lezcano <daniel.lezcano(a)linaro.org>
Date: Wed, 17 Oct 2018 11:18:30 +0200
Subject: [PATCH] arm64: dts: rockchip: remove vdd_log from rock960 to fix a
stability issues
When the performance governor is set as default, the rock960 hangs
around one minute after booting, whatever the activity is (idle, key
pressed, loaded, ...).
Based on the commit log found at https://patchwork.kernel.org/patch/10092377/
"vdd_log has no consumer and therefore will not be set to a specific
voltage. Still the PWM output pin gets configured and thence the vdd_log
output voltage will changed from it's default. Depending on the idle
state of the PWM this will slightly over or undervoltage the logic supply
of the RK3399 and cause instability with GbE (undervoltage) and PCIe
(overvoltage). Since the default value set by a voltage divider is the
correct supply voltage and we don't need to change it during runtime we
remove the rail from the devicetree completely so the PWM pin will not
be configured."
After removing the vdd-log from the rock960's specific DT, the board
does no longer hang and shows a stable behavior.
Apply the same change for the rock960 by removing the vdd-log from the
DT.
Fixes: 874846f1fccd ("arm64: dts: rockchip: add 96boards RK3399 Ficus board")
Cc: stable(a)vger.kernel.org
Tested-by: Manivannan Sadhasivam <manivannan.sadhasivam(a)linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org>
Signed-off-by: Heiko Stuebner <heiko(a)sntech.de>
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rock960.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-rock960.dtsi
index 6c8c4ab044aa..56abbb08c133 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-rock960.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-rock960.dtsi
@@ -57,18 +57,6 @@
regulator-always-on;
vin-supply = <&vcc_sys>;
};
-
- vdd_log: vdd-log {
- compatible = "pwm-regulator";
- pwms = <&pwm2 0 25000 0>;
- regulator-name = "vdd_log";
- regulator-min-microvolt = <800000>;
- regulator-max-microvolt = <1400000>;
- regulator-always-on;
- regulator-boot-on;
- vin-supply = <&vcc_sys>;
- };
-
};
&cpu_l0 {
The patch below does not apply to the 4.9-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From 834e772c8db0c6a275d75315d90aba4ebbb1e249 Mon Sep 17 00:00:00 2001
From: Stefan Hajnoczi <stefanha(a)redhat.com>
Date: Mon, 5 Nov 2018 10:35:47 +0000
Subject: [PATCH] vhost/vsock: fix use-after-free in network stack callers
If the network stack calls .send_pkt()/.cancel_pkt() during .release(),
a struct vhost_vsock use-after-free is possible. This occurs because
.release() does not wait for other CPUs to stop using struct
vhost_vsock.
Switch to an RCU-enabled hashtable (indexed by guest CID) so that
.release() can wait for other CPUs by calling synchronize_rcu(). This
also eliminates vhost_vsock_lock acquisition in the data path so it
could have a positive effect on performance.
This is CVE-2018-14625 "kernel: use-after-free Read in vhost_transport_send_pkt".
Cc: stable(a)vger.kernel.org
Reported-and-tested-by: syzbot+bd391451452fb0b93039(a)syzkaller.appspotmail.com
Reported-by: syzbot+e3e074963495f92a89ed(a)syzkaller.appspotmail.com
Reported-by: syzbot+d5a0a170c5069658b141(a)syzkaller.appspotmail.com
Signed-off-by: Stefan Hajnoczi <stefanha(a)redhat.com>
Signed-off-by: Michael S. Tsirkin <mst(a)redhat.com>
Acked-by: Jason Wang <jasowang(a)redhat.com>
diff --git a/drivers/vhost/vsock.c b/drivers/vhost/vsock.c
index 731e2ea2aeca..98ed5be132c6 100644
--- a/drivers/vhost/vsock.c
+++ b/drivers/vhost/vsock.c
@@ -15,6 +15,7 @@
#include <net/sock.h>
#include <linux/virtio_vsock.h>
#include <linux/vhost.h>
+#include <linux/hashtable.h>
#include <net/af_vsock.h>
#include "vhost.h"
@@ -27,14 +28,14 @@ enum {
/* Used to track all the vhost_vsock instances on the system. */
static DEFINE_SPINLOCK(vhost_vsock_lock);
-static LIST_HEAD(vhost_vsock_list);
+static DEFINE_READ_MOSTLY_HASHTABLE(vhost_vsock_hash, 8);
struct vhost_vsock {
struct vhost_dev dev;
struct vhost_virtqueue vqs[2];
- /* Link to global vhost_vsock_list, protected by vhost_vsock_lock */
- struct list_head list;
+ /* Link to global vhost_vsock_hash, writes use vhost_vsock_lock */
+ struct hlist_node hash;
struct vhost_work send_pkt_work;
spinlock_t send_pkt_list_lock;
@@ -50,11 +51,14 @@ static u32 vhost_transport_get_local_cid(void)
return VHOST_VSOCK_DEFAULT_HOST_CID;
}
-static struct vhost_vsock *__vhost_vsock_get(u32 guest_cid)
+/* Callers that dereference the return value must hold vhost_vsock_lock or the
+ * RCU read lock.
+ */
+static struct vhost_vsock *vhost_vsock_get(u32 guest_cid)
{
struct vhost_vsock *vsock;
- list_for_each_entry(vsock, &vhost_vsock_list, list) {
+ hash_for_each_possible_rcu(vhost_vsock_hash, vsock, hash, guest_cid) {
u32 other_cid = vsock->guest_cid;
/* Skip instances that have no CID yet */
@@ -69,17 +73,6 @@ static struct vhost_vsock *__vhost_vsock_get(u32 guest_cid)
return NULL;
}
-static struct vhost_vsock *vhost_vsock_get(u32 guest_cid)
-{
- struct vhost_vsock *vsock;
-
- spin_lock_bh(&vhost_vsock_lock);
- vsock = __vhost_vsock_get(guest_cid);
- spin_unlock_bh(&vhost_vsock_lock);
-
- return vsock;
-}
-
static void
vhost_transport_do_send_pkt(struct vhost_vsock *vsock,
struct vhost_virtqueue *vq)
@@ -210,9 +203,12 @@ vhost_transport_send_pkt(struct virtio_vsock_pkt *pkt)
struct vhost_vsock *vsock;
int len = pkt->len;
+ rcu_read_lock();
+
/* Find the vhost_vsock according to guest context id */
vsock = vhost_vsock_get(le64_to_cpu(pkt->hdr.dst_cid));
if (!vsock) {
+ rcu_read_unlock();
virtio_transport_free_pkt(pkt);
return -ENODEV;
}
@@ -225,6 +221,8 @@ vhost_transport_send_pkt(struct virtio_vsock_pkt *pkt)
spin_unlock_bh(&vsock->send_pkt_list_lock);
vhost_work_queue(&vsock->dev, &vsock->send_pkt_work);
+
+ rcu_read_unlock();
return len;
}
@@ -234,12 +232,15 @@ vhost_transport_cancel_pkt(struct vsock_sock *vsk)
struct vhost_vsock *vsock;
struct virtio_vsock_pkt *pkt, *n;
int cnt = 0;
+ int ret = -ENODEV;
LIST_HEAD(freeme);
+ rcu_read_lock();
+
/* Find the vhost_vsock according to guest context id */
vsock = vhost_vsock_get(vsk->remote_addr.svm_cid);
if (!vsock)
- return -ENODEV;
+ goto out;
spin_lock_bh(&vsock->send_pkt_list_lock);
list_for_each_entry_safe(pkt, n, &vsock->send_pkt_list, list) {
@@ -265,7 +266,10 @@ vhost_transport_cancel_pkt(struct vsock_sock *vsk)
vhost_poll_queue(&tx_vq->poll);
}
- return 0;
+ ret = 0;
+out:
+ rcu_read_unlock();
+ return ret;
}
static struct virtio_vsock_pkt *
@@ -533,10 +537,6 @@ static int vhost_vsock_dev_open(struct inode *inode, struct file *file)
spin_lock_init(&vsock->send_pkt_list_lock);
INIT_LIST_HEAD(&vsock->send_pkt_list);
vhost_work_init(&vsock->send_pkt_work, vhost_transport_send_pkt_work);
-
- spin_lock_bh(&vhost_vsock_lock);
- list_add_tail(&vsock->list, &vhost_vsock_list);
- spin_unlock_bh(&vhost_vsock_lock);
return 0;
out:
@@ -585,9 +585,13 @@ static int vhost_vsock_dev_release(struct inode *inode, struct file *file)
struct vhost_vsock *vsock = file->private_data;
spin_lock_bh(&vhost_vsock_lock);
- list_del(&vsock->list);
+ if (vsock->guest_cid)
+ hash_del_rcu(&vsock->hash);
spin_unlock_bh(&vhost_vsock_lock);
+ /* Wait for other CPUs to finish using vsock */
+ synchronize_rcu();
+
/* Iterating over all connections for all CIDs to find orphans is
* inefficient. Room for improvement here. */
vsock_for_each_connected_socket(vhost_vsock_reset_orphans);
@@ -628,12 +632,17 @@ static int vhost_vsock_set_cid(struct vhost_vsock *vsock, u64 guest_cid)
/* Refuse if CID is already in use */
spin_lock_bh(&vhost_vsock_lock);
- other = __vhost_vsock_get(guest_cid);
+ other = vhost_vsock_get(guest_cid);
if (other && other != vsock) {
spin_unlock_bh(&vhost_vsock_lock);
return -EADDRINUSE;
}
+
+ if (vsock->guest_cid)
+ hash_del_rcu(&vsock->hash);
+
vsock->guest_cid = guest_cid;
+ hash_add_rcu(vhost_vsock_hash, &vsock->hash, guest_cid);
spin_unlock_bh(&vhost_vsock_lock);
return 0;
On Mon, 10 Dec 2018 21:09:20 +0000
Sasha Levin <sashal(a)kernel.org> wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: .
>
> The bot has tested the following trees: v4.19.8, v4.14.87, v4.9.144, v4.4.166, v3.18.128,
>
> v4.19.8: Build OK!
> v4.14.87: Failed to apply! Possible dependencies:
> 37db96bb4962 ("tools lib traceevent: Handle new pointer processing of bprint strings")
Bah, I cut and pasted incorrectly the sha1. I had:
7db96bb49629 (chopped off the 3)
-- Steve
>
> v4.9.144: Failed to apply! Possible dependencies:
> 37db96bb4962 ("tools lib traceevent: Handle new pointer processing of bprint strings")
>
> v4.4.166: Failed to apply! Possible dependencies:
> 37db96bb4962 ("tools lib traceevent: Handle new pointer processing of bprint strings")
>
> v3.18.128: Failed to apply! Possible dependencies:
> 37db96bb4962 ("tools lib traceevent: Handle new pointer processing of bprint strings")
> 38d70b7ca176 ("tools lib traceevent: Simplify pointer print logic and fix %pF")
> 3d199b5be533 ("tools lib traceevent: Add support for IP address formats")
> b6bd9c7d543a ("tools lib traceevent: Support %ps/%pS")
>
>
> How should we proceed with this patch?
>
> --
> Thanks,
> Sasha
From: Jens Axboe <axboe(a)kernel.dk>
commit f7068114d45ec55996b9040e98111afa56e010fe upstream.
We're casting the CDROM layer request_sense to the SCSI sense
buffer, but the former is 64 bytes and the latter is 96 bytes.
As we generally allocate these on the stack, we end up blowing
up the stack.
Fix this by wrapping the scsi_execute() call with a properly
sized sense buffer, and copying back the bits for the CDROM
layer.
Reported-by: Piotr Gabriel Kosinski <pg.kosinski(a)gmail.com>
Reported-by: Daniel Shapira <daniel(a)twistlock.com>
Tested-by: Kees Cook <keescook(a)chromium.org>
Fixes: 82ed4db499b8 ("block: split scsi_request out of struct request")
Signed-off-by: Jens Axboe <axboe(a)kernel.dk>
[bwh: Despite what the "Fixes" field says, a buffer overrun was already
possible if the sense data was really > 64 bytes long.
Backported to 4.9:
- We always need to allocate a sense buffer in order to call
scsi_normalize_sense()
- Remove the existing conditional heap-allocation of the sense buffer]
Signed-off-by: Ben Hutchings <ben.hutchings(a)codethink.co.uk>
---
drivers/scsi/sr_ioctl.c | 21 +++++++--------------
1 file changed, 7 insertions(+), 14 deletions(-)
diff --git a/drivers/scsi/sr_ioctl.c b/drivers/scsi/sr_ioctl.c
index 03054c0e7689..3c3e8115f73d 100644
--- a/drivers/scsi/sr_ioctl.c
+++ b/drivers/scsi/sr_ioctl.c
@@ -187,30 +187,25 @@ int sr_do_ioctl(Scsi_CD *cd, struct packet_command *cgc)
struct scsi_device *SDev;
struct scsi_sense_hdr sshdr;
int result, err = 0, retries = 0;
- struct request_sense *sense = cgc->sense;
+ unsigned char sense_buffer[SCSI_SENSE_BUFFERSIZE];
SDev = cd->device;
- if (!sense) {
- sense = kmalloc(SCSI_SENSE_BUFFERSIZE, GFP_KERNEL);
- if (!sense) {
- err = -ENOMEM;
- goto out;
- }
- }
-
retry:
if (!scsi_block_when_processing_errors(SDev)) {
err = -ENODEV;
goto out;
}
- memset(sense, 0, sizeof(*sense));
+ memset(sense_buffer, 0, sizeof(sense_buffer));
result = scsi_execute(SDev, cgc->cmd, cgc->data_direction,
- cgc->buffer, cgc->buflen, (char *)sense,
+ cgc->buffer, cgc->buflen, sense_buffer,
cgc->timeout, IOCTL_RETRIES, 0, NULL);
- scsi_normalize_sense((char *)sense, sizeof(*sense), &sshdr);
+ scsi_normalize_sense(sense_buffer, sizeof(sense_buffer), &sshdr);
+
+ if (cgc->sense)
+ memcpy(cgc->sense, sense_buffer, sizeof(*cgc->sense));
/* Minimal error checking. Ignore cases we know about, and report the rest. */
if (driver_byte(result) != 0) {
@@ -261,8 +256,6 @@ int sr_do_ioctl(Scsi_CD *cd, struct packet_command *cgc)
/* Wake up a process waiting for device */
out:
- if (!cgc->sense)
- kfree(sense);
cgc->stat = err;
return err;
}
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
The user triggers the creation of a pseudo-locked region when writing
the requested schemata to the schemata resctrl file. The pseudo-locking
of a region is required to be done on a CPU that is associated with the
cache on which the pseudo-locked region will reside. In order to run the
locking code on a specific CPU the needed CPU has to be selected and
ensured to remain online during the entire locking sequence.
At this time the cpu_hotplug_lock is not taken during the pseudo-lock
region creation and it is thus possible for a CPU to be selected to run
the pseudo-locking code and then that CPU to go offline before the
thread is able to run on it.
Fix this by ensuring that the cpu_hotplug_lock is taken while the CPU on
which code has to run needs to be controlled. Since the cpu_hotplug_lock
is always taken before rdtgroup_mutex the lock order is maintained.
Fixes: e0bdfe8e36f3 ("x86/intel_rdt: Support creation/removal of pseudo-locked region")
Signed-off-by: Reinette Chatre <reinette.chatre(a)intel.com>
Cc: stable(a)vger.kernel.org
---
arch/x86/kernel/cpu/resctrl/ctrlmondata.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/x86/kernel/cpu/resctrl/ctrlmondata.c b/arch/x86/kernel/cpu/resctrl/ctrlmondata.c
index 03ee13235a45..6f7adb3be01e 100644
--- a/arch/x86/kernel/cpu/resctrl/ctrlmondata.c
+++ b/arch/x86/kernel/cpu/resctrl/ctrlmondata.c
@@ -23,6 +23,7 @@
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
+#include <linux/cpu.h>
#include <linux/kernfs.h>
#include <linux/seq_file.h>
#include <linux/slab.h>
@@ -381,9 +382,11 @@ ssize_t rdtgroup_schemata_write(struct kernfs_open_file *of,
return -EINVAL;
buf[nbytes - 1] = '\0';
+ cpus_read_lock();
rdtgrp = rdtgroup_kn_lock_live(of->kn);
if (!rdtgrp) {
rdtgroup_kn_unlock(of->kn);
+ cpus_read_unlock();
return -ENOENT;
}
rdt_last_cmd_clear();
@@ -438,6 +441,7 @@ ssize_t rdtgroup_schemata_write(struct kernfs_open_file *of,
out:
rdtgroup_kn_unlock(of->kn);
+ cpus_read_unlock();
return ret ?: nbytes;
}
--
2.17.0
From: "Steven Rostedt (VMware)" <rostedt(a)goodmis.org>
When create_event_filter() fails in set_trigger_filter(), the filter may
still be allocated and needs to be freed. The caller expects the
data->filter to be updated with the new filter, even if the new filter
failed (we could add an error message by setting set_str parameter of
create_event_filter(), but that's another update).
But because the error would just exit, filter was left hanging and
nothing could free it.
Found by kmemleak detector.
Cc: Tom Zanussi <tom.zanussi(a)linux.intel.com>
Cc: stable(a)vger.kernel.org
Fixes: bac5fb97a173a ("tracing: Add and use generic set_trigger_filter() implementation")
Signed-off-by: Steven Rostedt (VMware) <rostedt(a)goodmis.org>
---
kernel/trace/trace_events_trigger.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
index 2152d1e530cb..cd12ecb66eb9 100644
--- a/kernel/trace/trace_events_trigger.c
+++ b/kernel/trace/trace_events_trigger.c
@@ -732,8 +732,10 @@ int set_trigger_filter(char *filter_str,
/* The filter is for the 'trigger' event, not the triggered event */
ret = create_event_filter(file->event_call, filter_str, false, &filter);
- if (ret)
- goto out;
+ /*
+ * If create_event_filter() fails, filter still needs to be freed.
+ * Which the calling code will do with data->filter.
+ */
assign:
tmp = rcu_access_pointer(data->filter);
--
2.19.1
Disable power_down by setting the parameter to
DWC2_POWER_DOWN_PARAM_NONE. This fixes a problem on various Amlogic
Meson SoCs where USB devices are only recognized when plugged in before
booting Linux. A hot-plugged USB device was not detected even though the
device got power (my USB thumb drive for example has an LED which lit
up).
A similar fix was implemented for Rockchip SoCs in commit c216765d3a1def
("usb: dwc2: disable power_down on rockchip devices"). That commit
suggests that a change in the dwc2 driver is the cause because the
default value for the "hibernate" parameter (which then got renamed to
"power_down" to support other modes) was changed in the v4.17 merge
window with:
commit 6d23ee9caa6790 ("Merge tag 'usb-for-v4.17' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-testing").
Cc: <stable(a)vger.kernel.org> # 4.19
Suggested-by: Christian Hewitt <christianshewitt(a)gmail.com>
Signed-off-by: Martin Blumenstingl <martin.blumenstingl(a)googlemail.com>
---
drivers/usb/dwc2/params.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/dwc2/params.c b/drivers/usb/dwc2/params.c
index 7c1b6938f212..38c813b1d203 100644
--- a/drivers/usb/dwc2/params.c
+++ b/drivers/usb/dwc2/params.c
@@ -111,6 +111,7 @@ static void dwc2_set_amlogic_params(struct dwc2_hsotg *hsotg)
p->phy_type = DWC2_PHY_TYPE_PARAM_UTMI;
p->ahbcfg = GAHBCFG_HBSTLEN_INCR8 <<
GAHBCFG_HBSTLEN_SHIFT;
+ p->power_down = DWC2_POWER_DOWN_PARAM_NONE;
}
static void dwc2_set_amcc_params(struct dwc2_hsotg *hsotg)
--
2.19.2
Zebu boards were added in v4.9 and then renamed to "haps" in v4.10.
Thus backporting
commit 64234961c145 (ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from defconfigs)
we missed "zebu" defconfigs in v4.9.
Note this is only applicable to "linux-4.9.y"!
Spotted by KerneCI, see [1].
[1] https://storage.kernelci.org/stable/linux-4.9.y/v4.9.144/arc/zebu_hs_smp_de…
Signed-off-by: Alexey Brodkin <abrodkin(a)synopsys.com>
Cc: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
Cc: Kevin Hilman <khilman(a)baylibre.com>
---
arch/arc/configs/zebu_hs_defconfig | 1 -
arch/arc/configs/zebu_hs_smp_defconfig | 1 -
2 files changed, 2 deletions(-)
diff --git a/arch/arc/configs/zebu_hs_defconfig b/arch/arc/configs/zebu_hs_defconfig
index 9f6166be7145..3346829b02bb 100644
--- a/arch/arc/configs/zebu_hs_defconfig
+++ b/arch/arc/configs/zebu_hs_defconfig
@@ -11,7 +11,6 @@ CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_PID_NS is not set
CONFIG_BLK_DEV_INITRD=y
-CONFIG_INITRAMFS_SOURCE="../../arc_initramfs_hs/"
CONFIG_EXPERT=y
CONFIG_PERF_EVENTS=y
# CONFIG_COMPAT_BRK is not set
diff --git a/arch/arc/configs/zebu_hs_smp_defconfig b/arch/arc/configs/zebu_hs_smp_defconfig
index 44e9693f4257..4471f9c37d7e 100644
--- a/arch/arc/configs/zebu_hs_smp_defconfig
+++ b/arch/arc/configs/zebu_hs_smp_defconfig
@@ -11,7 +11,6 @@ CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_PID_NS is not set
CONFIG_BLK_DEV_INITRD=y
-CONFIG_INITRAMFS_SOURCE="../../arc_initramfs_hs/"
CONFIG_EMBEDDED=y
CONFIG_PERF_EVENTS=y
# CONFIG_VM_EVENT_COUNTERS is not set
--
2.16.2
On Sun, Dec 09, 2018 at 11:44:19AM -0500, Theodore Y. Ts'o wrote:
> On Sun, Dec 09, 2018 at 12:30:39PM +0100, Greg KH wrote:
> > > P.P.P.S. If I were king, I'd be asking for a huge number of kunit
> > > tests for block-mq to be developed, and then running them under a
> > > Thread Sanitizer.
> >
> > Isn't that what xfs and fio is? Aren't we running this all the time and
> > reporting those issues? How did this bug not show up on those tests, is
> > it just because they didn't run long enough?
> >
> > Because of those test suites, I was thinking that the block and
> > filesystem paths were one of the more well-tested things we had at the
> > moment, is this not true?
>
> I'm pretty confident about the file system paths, and the "happy
> paths" for the block layer.
>
> But with Kernel Bugzilla #201685, despite huge amounts both before and
> after 4.19-rc1, nothing picked it up. It turned out to be very
> configuration specific, *and* only happened when you were under heavy
> memory pressure and/or I/O pressure.
>
> I'm starting to try to use blktests, but it's not as mature as
> xfstests. It has portability issues, as it assumes a much newer
> userspace. So I can't even run it under some environments at all.
> The test coverage just isn't as broad. Compare:
>
> ext4/4k: 441 tests, 1 failures, 42 skipped, 4387 seconds
> Failures: generic/388
>
> Versus:
>
> Run: block/001 block/002 block/003 block/004 block/005 block/006
> block/009 block/010 block/012 block/013 block/014 block/015
> block/016 block/017 block/018 block/020 block/021 block/023
> block/024 loop/001 loop/002 loop/003 loop/004 loop/005 loop/006
> nvme/002 nvme/003 nvme/004 nvme/006 nvme/007 nvme/008 nvme/009
> nvme/010 nvme/011 nvme/012 nvme/013 nvme/014 nvme/015 nvme/016
> nvme/017 nvme/019 nvme/020 nvme/021 nvme/022 nvme/023 nvme/024
> nvme/025 nvme/026 nvme/027 nvme/028 scsi/001 scsi/002 scsi/003
> scsi/004 scsi/005 scsi/006 srp/001 srp/002 srp/003 srp/004
> srp/005 srp/006 srp/007 srp/008 srp/009 srp/010 srp/011 srp/012 srp/013
> Failures: block/017 block/024 nvme/002 nvme/003 nvme/008 nvme/009
> nvme/010 nvme/011 nvme/012 nvme/013 nvme/014 nvme/015 nvme/016
> nvme/019 nvme/020 nvme/021 nvme/022 nvme/023 nvme/024 nvme/025
> nvme/026 nvme/027 nvme/028 scsi/006 srp/001 srp/002 srp/003 srp/004
> srp/005 srp/006 srp/007 srp/008 srp/009 srp/010 srp/011 srp/012 srp/013
> Failed 37 of 69 tests
>
> (Most of the failures are test portability issues that I still need to
> work through, not real failures. But just look at the number of
> tests....)
So you are saying quantity rules over quantity? :)
It's really hard to judge this, given that xfstests are testing a whole
range of other things (POSIX compliance and stressing the vfs api),
while blktests are there to stress the block i/o api/interface.
So both would be best to run as we know xfstests also hits the block
layer...
thanks,
greg k-h
The latest file system corruption issue (Nominally fixed by
ffe81d45322c ("blk-mq: fix corruption with direct issue") later
fixed by c616cbee97ae ("blk-mq: punt failed direct issue to dispatch
list")) brought a lot of rightfully concerned users asking about
release schedules. 4.18 went EOL on Nov 21 and Fedora rebased to
4.19.3 on Nov 23. When the issue started getting visibility,
users were left with the option of running known EOL 4.18.x
kernels or running a 4.19 series that could corrupt their
data. Admittedly, the risk of running the EOL kernel was pretty
low given how recent it was, but it's still not a great look
to tell people to run something marked EOL.
I'm wondering if there's anything we can do to make things easier
on kernel consumers. Bugs will certainly happen but it really
makes it hard to push the "always run the latest stable" narrative
if there isn't a good fallback when things go seriously wrong. I
don't actually have a great proposal for a solution here other than
retroactively bringing back 4.18 (which I don't think Greg would
like) but I figured I should at least bring it up.
Thanks,
Laura
stable-rc/linux-3.18.y build: 185 builds: 2 failed, 183 passed, 4 errors, 1590 warnings (v3.18.128-41-g5c19427b8dec)
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.128-4…
Tree: stable-rc
Branch: linux-3.18.y
Git Describe: v3.18.128-41-g5c19427b8dec
Git Commit: 5c19427b8dec43f611737e157ffe5266e799d9a7
Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Built: 6 unique architectures
Build Failures Detected:
arc: gcc version 7.1.1 20170710 (ARCv2 ISA Linux uClibc toolchain 2017.09)
allnoconfig: FAIL
tinyconfig: FAIL
Errors and Warnings Detected:
arc: gcc version 7.1.1 20170710 (ARCv2 ISA Linux uClibc toolchain 2017.09)
allnoconfig: 2 errors, 666 warnings
tinyconfig: 2 errors, 664 warnings
arm64: gcc version 7.3.0 (Debian 7.3.0-28)
allnoconfig: 2 warnings
defconfig: 2 warnings
tinyconfig: 2 warnings
arm: gcc version 7.3.0 (Debian 7.3.0-28)
acs5k_defconfig: 2 warnings
acs5k_tiny_defconfig: 2 warnings
allnoconfig: 2 warnings
am200epdkit_defconfig: 2 warnings
ape6evm_defconfig: 2 warnings
armadillo800eva_defconfig: 2 warnings
assabet_defconfig: 2 warnings
at91_dt_defconfig: 2 warnings
at91rm9200_defconfig: 2 warnings
at91sam9260_9g20_defconfig: 2 warnings
at91sam9261_9g10_defconfig: 2 warnings
at91sam9263_defconfig: 2 warnings
at91sam9g45_defconfig: 2 warnings
at91sam9rl_defconfig: 2 warnings
at91x40_defconfig: 2 warnings
axm55xx_defconfig: 2 warnings
badge4_defconfig: 2 warnings
bcm2835_defconfig: 2 warnings
bcm_defconfig: 2 warnings
bockw_defconfig: 2 warnings
cerfcube_defconfig: 2 warnings
clps711x_defconfig: 2 warnings
cm_x2xx_defconfig: 2 warnings
cm_x300_defconfig: 2 warnings
cns3420vb_defconfig: 2 warnings
colibri_pxa270_defconfig: 2 warnings
colibri_pxa300_defconfig: 2 warnings
collie_defconfig: 2 warnings
corgi_defconfig: 2 warnings
davinci_all_defconfig: 2 warnings
dove_defconfig: 2 warnings
ebsa110_defconfig: 2 warnings
efm32_defconfig: 2 warnings
em_x270_defconfig: 2 warnings
ep93xx_defconfig: 2 warnings
eseries_pxa_defconfig: 2 warnings
exynos_defconfig: 2 warnings
ezx_defconfig: 2 warnings
footbridge_defconfig: 2 warnings
h3600_defconfig: 2 warnings
h5000_defconfig: 2 warnings
hackkit_defconfig: 2 warnings
hisi_defconfig: 2 warnings
imote2_defconfig: 2 warnings
imx_v4_v5_defconfig: 2 warnings
imx_v6_v7_defconfig: 2 warnings
integrator_defconfig: 2 warnings
iop13xx_defconfig: 2 warnings
iop32x_defconfig: 2 warnings
iop33x_defconfig: 2 warnings
ixp4xx_defconfig: 2 warnings
jornada720_defconfig: 2 warnings
keystone_defconfig: 2 warnings
koelsch_defconfig: 2 warnings
ks8695_defconfig: 2 warnings
kzm9g_defconfig: 2 warnings
lager_defconfig: 2 warnings
lart_defconfig: 2 warnings
lpc32xx_defconfig: 2 warnings
lpd270_defconfig: 2 warnings
lubbock_defconfig: 2 warnings
mackerel_defconfig: 2 warnings
magician_defconfig: 2 warnings
mainstone_defconfig: 2 warnings
marzen_defconfig: 2 warnings
mini2440_defconfig: 2 warnings
mmp2_defconfig: 2 warnings
moxart_defconfig: 2 warnings
msm_defconfig: 2 warnings
multi_v5_defconfig: 2 warnings
multi_v7_defconfig: 2 warnings
mv78xx0_defconfig: 2 warnings
mvebu_v5_defconfig: 2 warnings
mvebu_v7_defconfig: 2 warnings
mxs_defconfig: 2 warnings
neponset_defconfig: 2 warnings
netwinder_defconfig: 2 warnings
netx_defconfig: 2 warnings
nhk8815_defconfig: 2 warnings
nuc910_defconfig: 2 warnings
nuc950_defconfig: 2 warnings
nuc960_defconfig: 2 warnings
omap1_defconfig: 2 warnings
omap2plus_defconfig: 2 warnings
orion5x_defconfig: 2 warnings
palmz72_defconfig: 2 warnings
pcm027_defconfig: 2 warnings
pleb_defconfig: 2 warnings
prima2_defconfig: 2 warnings
pxa168_defconfig: 2 warnings
pxa255-idp_defconfig: 2 warnings
pxa3xx_defconfig: 2 warnings
pxa910_defconfig: 2 warnings
qcom_defconfig: 2 warnings
raumfeld_defconfig: 2 warnings
realview-smp_defconfig: 2 warnings
realview_defconfig: 2 warnings
rpc_defconfig: 2 warnings
s3c2410_defconfig: 2 warnings
s3c6400_defconfig: 2 warnings
s5pv210_defconfig: 2 warnings
sama5_defconfig: 2 warnings
shannon_defconfig: 2 warnings
shmobile_defconfig: 2 warnings
simpad_defconfig: 2 warnings
socfpga_defconfig: 2 warnings
spear13xx_defconfig: 2 warnings
spear3xx_defconfig: 2 warnings
spear6xx_defconfig: 2 warnings
spitz_defconfig: 2 warnings
sunxi_defconfig: 2 warnings
tct_hammer_defconfig: 2 warnings
tegra_defconfig: 2 warnings
tinyconfig: 2 warnings
trizeps4_defconfig: 2 warnings
u300_defconfig: 2 warnings
u8500_defconfig: 2 warnings
versatile_defconfig: 2 warnings
vexpress_defconfig: 2 warnings
viper_defconfig: 2 warnings
vt8500_v6_v7_defconfig: 2 warnings
xcep_defconfig: 2 warnings
zeus_defconfig: 2 warnings
i386: gcc version 7.3.0 (Debian 7.3.0-30)
allnoconfig: 3 warnings
tinyconfig: 3 warnings
x86_64: gcc version 7.3.0 (Debian 7.3.0-30)
allnoconfig: 1 warning
tinyconfig: 1 warning
Errors summary:
2 arch/arc/mm/tlbex.S:348: Error: unknown opcode 'lsl'
2 arch/arc/mm/tlbex.S:291: Error: unknown opcode 'lsl'
Warnings summary:
663 arc-linux-gcc: warning: '-mno-mpy' is deprecated
654 cc1: warning: '-mno-mpy' is deprecated
128 scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
128 scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
2 mm/memory.c:581:7: warning: assignment makes integer from pointer without a cast [-Wint-conversion]
2 lib/string_helpers.c:64:33: warning: '%03lld' directive output may be truncated writing between 3 and 13 bytes into a region of size 7 [-Wformat-truncation=]
2 kernel/sched/core.c:2766:1: warning: control reaches end of non-void function [-Wreturn-type]
2 include/linux/kernel.h:707:17: warning: comparison of distinct pointer types lacks a cast
2 arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
2 arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
2 arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
1 mm/mmap.c:684:2: warning: 'rb_parent' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 mm/mmap.c:684:2: warning: 'rb_link' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 mm/mmap.c:683:2: warning: 'prev' may be used uninitialized in this function [-Wmaybe-uninitialized]
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
acs5k_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
acs5k_tiny_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
allnoconfig (arm64) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
allnoconfig (i386) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
--------------------------------------------------------------------------------
allnoconfig (x86_64) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
lib/string_helpers.c:64:33: warning: '%03lld' directive output may be truncated writing between 3 and 13 bytes into a region of size 7 [-Wformat-truncation=]
--------------------------------------------------------------------------------
allnoconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
allnoconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
allnoconfig (arc) — FAIL, 2 errors, 666 warnings, 0 section mismatches
Errors:
arch/arc/mm/tlbex.S:291: Error: unknown opcode 'lsl'
arch/arc/mm/tlbex.S:348: Error: unknown opcode 'lsl'
Warnings:
arc-linux-gcc: warning: '-mno-mpy' is deprecated
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
kernel/sched/core.c:2766:1: warning: control reaches end of non-void function [-Wreturn-type]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
mm/memory.c:581:7: warning: assignment makes integer from pointer without a cast [-Wint-conversion]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
mm/mmap.c:684:2: warning: 'rb_link' may be used uninitialized in this function [-Wmaybe-uninitialized]
mm/mmap.c:684:2: warning: 'rb_parent' may be used uninitialized in this function [-Wmaybe-uninitialized]
mm/mmap.c:683:2: warning: 'prev' may be used uninitialized in this function [-Wmaybe-uninitialized]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
include/linux/kernel.h:707:17: warning: comparison of distinct pointer types lacks a cast
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
--------------------------------------------------------------------------------
am200epdkit_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ape6evm_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ar7_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
armadillo800eva_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
assabet_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91_dt_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91rm9200_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9260_9g20_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9261_9g10_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9263_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9g45_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9rl_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91x40_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ath79_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
axm55xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
badge4_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
bcm2835_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
bcm47xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
bcm63xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
bcm_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
bigsur_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
bockw_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
capcella_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cavium_octeon_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cerfcube_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
clps711x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cm_x2xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cm_x300_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cns3420vb_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cobalt_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
colibri_pxa270_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
colibri_pxa300_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
collie_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
corgi_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
davinci_all_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
db1xxx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
decstation_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig (arm64) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
dove_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
e55_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ebsa110_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
efm32_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
em_x270_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ep93xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
eseries_pxa_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
exynos_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ezx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
footbridge_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
fuloong2e_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
gpr_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
h3600_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
h5000_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
hackkit_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
hisi_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
imote2_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
imx_v4_v5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
imx_v6_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
integrator_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
iop13xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
iop32x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
iop33x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ip22_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ip27_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ip28_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ip32_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ixp4xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
jazz_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
jmr3927_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
jornada720_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
keystone_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
koelsch_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ks8695_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
kzm9g_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lager_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lart_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lasat_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
lemote2f_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
loongson3_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
lpc32xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lpd270_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ls1b_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
lubbock_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mackerel_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
magician_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mainstone_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
malta_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
malta_kvm_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
malta_kvm_guest_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltaaprp_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltasmvp_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltasmvp_eva_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltaup_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
markeins_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
marzen_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mini2440_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mips_paravirt_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
mmp2_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
moxart_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mpc30x_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
msm_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
msp71xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
mtx1_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
multi_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mv78xx0_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mvebu_v5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mvebu_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mxs_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
neponset_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
netwinder_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
netx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nhk8815_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nlm_xlp_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nlm_xlr_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nuc910_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nuc950_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nuc960_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
omap1_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
omap2plus_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
orion5x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
palmz72_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pcm027_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pleb_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pnx8335_stb225_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
prima2_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa168_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa255-idp_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa3xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa910_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
qcom_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
qi_lb60_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
raumfeld_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
rb532_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
rbtx49xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
realview-smp_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
realview_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
rm200_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
rpc_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
rt305x_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
s3c2410_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
s3c6400_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
s5pv210_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
sama5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
sb1250_swarm_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
sead3_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
sead3micro_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
shannon_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
shmobile_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
simpad_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
socfpga_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spear13xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spear3xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spear6xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spitz_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
sunxi_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tb0219_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tb0226_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tb0287_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tct_hammer_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tegra_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tinyconfig (i386) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
--------------------------------------------------------------------------------
tinyconfig (arm64) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tinyconfig (x86_64) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings:
lib/string_helpers.c:64:33: warning: '%03lld' directive output may be truncated writing between 3 and 13 bytes into a region of size 7 [-Wformat-truncation=]
--------------------------------------------------------------------------------
tinyconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tinyconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tinyconfig (arc) — FAIL, 2 errors, 664 warnings, 0 section mismatches
Errors:
arch/arc/mm/tlbex.S:291: Error: unknown opcode 'lsl'
arch/arc/mm/tlbex.S:348: Error: unknown opcode 'lsl'
Warnings:
arc-linux-gcc: warning: '-mno-mpy' is deprecated
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
mm/memory.c:581:7: warning: assignment makes integer from pointer without a cast [-Wint-conversion]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
include/linux/kernel.h:707:17: warning: comparison of distinct pointer types lacks a cast
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
kernel/sched/core.c:2766:1: warning: control reaches end of non-void function [-Wreturn-type]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
--------------------------------------------------------------------------------
trizeps4_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
u300_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
u8500_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
versatile_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
vexpress_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
viper_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
vt8500_v6_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
workpad_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
xcep_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
xway_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
zeus_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
---
For more info write to <info(a)kernelci.org>
In an initial commit, 'SYNC_STATUS' register is referred to get
clock configuration, however this is wrong, according to my local
note at hand for reverse-engineering about packet dump. It should
be 'CLOCK_CONFIG' register. Actually, ff400_dump_clock_config()
is correctly programmed.
This commit fixes the bug.
Cc: <stable(a)vger.kernel.org> # v4.12+
Fixes: 76fdb3a9e13a ('ALSA: fireface: add support for Fireface 400')
Signed-off-by: Takashi Sakamoto <o-takashi(a)sakamocchi.jp>
---
sound/firewire/fireface/ff-protocol-ff400.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/firewire/fireface/ff-protocol-ff400.c b/sound/firewire/fireface/ff-protocol-ff400.c
index 64c3cb0fb926..654a50319198 100644
--- a/sound/firewire/fireface/ff-protocol-ff400.c
+++ b/sound/firewire/fireface/ff-protocol-ff400.c
@@ -30,7 +30,7 @@ static int ff400_get_clock(struct snd_ff *ff, unsigned int *rate,
int err;
err = snd_fw_transaction(ff->unit, TCODE_READ_QUADLET_REQUEST,
- FF400_SYNC_STATUS, ®, sizeof(reg), 0);
+ FF400_CLOCK_CONFIG, ®, sizeof(reg), 0);
if (err < 0)
return err;
data = le32_to_cpu(reg);
--
2.19.1
Hi folks,
I sometimes see stable release candidates move backwards in time.
For example, in the last few days, for v4.4.y.queue:
Dec 08 06:55 v4.4.166
Dec 06 23:36 v4.4.166-57-g4e21c8c946b3
Dec 04 03:31 v4.4.166-21-g9caf29c799ac
Dec 04 00:36 v4.4.166-17-g14d854102e8c
Dec 03 04:35 v4.4.166-19-gb8c2abe84488
Dec 02 01:07 v4.4.166
How comes?
Normally I would not notice (or comment). However, after
v4.4.166 the default configuration for arc had changed,
requiring different compilers for defconfig/allnoconfig.
I had fixed this up, but now my builds are broken again
due to the reverted changes.
Thanks,
Guenter
Hi Greg,
I am trying to get rid of antique compiler versions when building older
kernels. To assist that effort, it would help if you could apply commit
5045ea37377c ("powerpc/vdso64: Use double word compare on pointers")
to v3.18.y.
Thanks,
Guenter
Hello Greg,
Please apply commit 400e22499dd92613821374c8c6c88c7225359980 "mm: don't warn
about allocations which stall for too long" to the 4.14 stable tree. It applies
cleanly.
I'm sending the 4.9 backport separately.
Thanks,
Amit
First problem: I cannot compile the kernel with my version of compiler
~~~~
$ make defconfig
*** Default configuration is based on 'i386_defconfig'
\#
\# configuration written to .config
\#
$ grep CONFIG_RETPOLINE .config
CONFIG_RETPOLINE=y
$ make
arch/x86/Makefile:224: *** You are building kernel with non-retpoline
compiler, please update your compiler.. Stop.
~~~~
Second problem: when I disable the feature - it cannot take effect,
because the parse-time error happens before `syncconfig`
~~~~
$ scripts/config -d RETPOLINE
$ grep CONFIG_RETPOLINE .config
\# CONFIG_RETPOLINE is not set
$ make
arch/x86/Makefile:224: *** You are building kernel with non-retpoline
compiler, please update your compiler.. Stop.
~~~~
Fixes: 4cd24de3a098 ("x86/retpoline: Make CONFIG_RETPOLINE depend on compiler support")
Signed-off-by: Kirill Marinushkin <k.marinushkin(a)gmail.com>
Cc: Thomas Gleixner <tglx(a)linutronix.de>
Cc: Ingo Molnar <mingo(a)redhat.com>
Cc: Borislav Petkov <bp(a)alien8.de>
Cc: Zhenzhong Duan <zhenzhong.duan(a)oracle.com>
Cc: H. Peter Anvin <hpa(a)zytor.com>
Cc: x86(a)kernel.org
Cc: linux-kernel(a)vger.kernel.org
Cc: stable(a)vger.kernel.org
---
arch/x86/Makefile | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index f5d7f4134524..26a2198c59b3 100644
--- a/arch/x86/Makefile
+++ b/arch/x86/Makefile
@@ -220,9 +220,6 @@ KBUILD_CFLAGS += -fno-asynchronous-unwind-tables
# Avoid indirect branches in kernel to deal with Spectre
ifdef CONFIG_RETPOLINE
-ifeq ($(RETPOLINE_CFLAGS),)
- $(error You are building kernel with non-retpoline compiler, please update your compiler.)
-endif
KBUILD_CFLAGS += $(RETPOLINE_CFLAGS)
endif
--
2.13.6
This is the start of the stable review cycle for the 4.19.8 release.
There are 41 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sat Dec 8 14:29:30 UTC 2018.
Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.8-rc1…
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
Linux 4.19.8-rc1
Guoqing Jiang <gqjiang(a)suse.com>
tipc: use destination length for copy string
Alexey Brodkin <abrodkin(a)synopsys.com>
arc: [devboards] Add support of NFSv3 ACL
Kevin Hilman <khilman(a)baylibre.com>
ARC: change defconfig defaults to ARCv2
Qu Wenruo <wqu(a)suse.com>
btrfs: tree-checker: Don't check max block group size as current max chunk size limit is unreliable
Adam Wong <adam(a)adamwong.me>
Input: elan_i2c - add support for ELAN0621 touchpad
Noah Westervelt <nwestervelt(a)outlook.com>
Input: elan_i2c - add ACPI ID for Lenovo IdeaPad 330-15ARR
Patrick Gaskin <patrick(a)pgaskin.net>
Input: elan_i2c - add ELAN0620 to the ACPI table
Brian Norris <briannorris(a)chromium.org>
Input: cros_ec_keyb - fix button/switch capability reports
Christian Hoff <christian_hoff(a)gmx.net>
Input: matrix_keypad - check for errors from of_get_named_gpio()
Lyude Paul <lyude(a)redhat.com>
Input: synaptics - add PNP ID for ThinkPad P50 to SMBus
Cameron Gutman <aicommander(a)gmail.com>
Input: xpad - quirk all PDP Xbox One gamepads
Martin Wilck <mwilck(a)suse.com>
scsi: lpfc: fix block guard enablement on SLI3 adapters
Lihong Yang <lihong.yang(a)intel.com>
i40e: Fix deletion of MAC filters
Paul Moore <paul(a)paul-moore.com>
selinux: add support for RTM_NEWCHAIN, RTM_DELCHAIN, and RTM_GETCHAIN
Wei Wang <wawei(a)amazon.de>
svm: Add mutex_lock to protect apic_access_page_done on AMD systems
Laura Abbott <labbott(a)redhat.com>
kgdboc: Fix warning with module build
Laura Abbott <labbott(a)redhat.com>
kgdboc: Fix restrict error
Andrea Arcangeli <aarcange(a)redhat.com>
userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set
Andrea Arcangeli <aarcange(a)redhat.com>
userfaultfd: shmem: add i_size checks
Andrea Arcangeli <aarcange(a)redhat.com>
userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem
Andrea Arcangeli <aarcange(a)redhat.com>
userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails
Lyude Paul <lyude(a)redhat.com>
drm/meson: Fix OOB memory accesses in meson_viu_set_osd_lut()
Lyude Paul <lyude(a)redhat.com>
drm/meson: Enable fast_io in meson_dw_hdmi_regmap_config
Neil Armstrong <narmstrong(a)baylibre.com>
drm/meson: Fixes for drm_crtc_vblank_on/off support
Sergio Correia <sergio(a)correia.cc>
drm: set is_master to 0 upon drm_new_set_master() failure
Lyude Paul <lyude(a)redhat.com>
drm/amd/dm: Understand why attaching path/tile properties are needed
Lyude Paul <lyude(a)redhat.com>
drm/amd/dm: Don't forget to attach MST encoders
Sam Bobroff <sbobroff(a)linux.ibm.com>
drm/ast: Fix incorrect free on ioregs
Steven Rostedt (VMware) <rostedt(a)goodmis.org>
tracing/fgraph: Fix set_graph_function from showing interrupts
Michael Guralnik <michaelgur(a)mellanox.com>
IB/mlx5: Avoid load failure due to unknown link width
Dmitry V. Levin <ldv(a)altlinux.org>
mips: fix mips_get_syscall_arg o32 check
Mathias Kresin <dev(a)kresin.me>
MIPS: ralink: Fix mt7620 nd_sd pinmux
Zenghui Yu <yuzenghui(a)huawei.com>
tracepoint: Use __idx instead of idx in DO_TRACE macro to make it unique
Pavankumar Kondeti <pkondeti(a)codeaurora.org>
sched, trace: Fix prev_state output in sched_switch tracepoint
Masami Hiramatsu <mhiramat(a)kernel.org>
arm64: ftrace: Fix to enable syscall events on arm64
Frieder Schrempf <frieder.schrempf(a)kontron.de>
mtd: nand: Fix memory allocation in nanddev_bbt_init()
Andrea Parri <andrea.parri(a)amarulasolutions.com>
uprobes: Fix handle_swbp() vs. unregister() + register() race once more
Sagi Grimberg <sagi(a)grimberg.me>
iser: set sector for ambiguous mr status errors
Linus Torvalds <torvalds(a)linux-foundation.org>
unifdef: use memcpy instead of strncpy
Linus Torvalds <torvalds(a)linux-foundation.org>
test_hexdump: use memcpy instead of strncpy
Jens Axboe <axboe(a)kernel.dk>
blk-mq: fix corruption with direct issue
-------------
Diffstat:
Makefile | 4 +-
arch/arc/Kconfig | 2 +-
arch/arc/Makefile | 2 +-
arch/arc/configs/axs101_defconfig | 2 +
arch/arc/configs/axs103_defconfig | 1 +
arch/arc/configs/axs103_smp_defconfig | 1 +
arch/arc/configs/hsdk_defconfig | 1 +
arch/arc/configs/nps_defconfig | 2 +
arch/arc/configs/nsim_700_defconfig | 1 +
arch/arc/configs/nsimosci_defconfig | 2 +
arch/arc/configs/nsimosci_hs_defconfig | 1 +
arch/arc/configs/nsimosci_hs_smp_defconfig | 1 +
arch/arc/configs/tb10x_defconfig | 1 +
arch/arc/configs/vdk_hs38_defconfig | 1 +
arch/arc/configs/vdk_hs38_smp_defconfig | 1 +
arch/arm64/include/asm/ftrace.h | 13 +++++
arch/mips/include/asm/syscall.h | 2 +-
arch/mips/ralink/mt7620.c | 2 +-
arch/x86/kvm/svm.c | 19 +++++---
block/blk-mq.c | 26 +++++++++-
.../amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 5 +-
drivers/gpu/drm/ast/ast_main.c | 3 +-
drivers/gpu/drm/drm_auth.c | 2 +
drivers/gpu/drm/meson/meson_crtc.c | 27 +++++++++-
drivers/gpu/drm/meson/meson_dw_hdmi.c | 1 +
drivers/gpu/drm/meson/meson_venc.c | 3 ++
drivers/gpu/drm/meson/meson_viu.c | 12 ++---
drivers/infiniband/hw/mlx5/main.c | 29 +++++------
drivers/infiniband/ulp/iser/iser_verbs.c | 7 ++-
drivers/input/joystick/xpad.c | 16 +++---
drivers/input/keyboard/cros_ec_keyb.c | 3 +-
drivers/input/keyboard/matrix_keypad.c | 23 +++++----
drivers/input/mouse/elan_i2c_core.c | 3 ++
drivers/input/mouse/synaptics.c | 1 +
drivers/mtd/nand/bbt.c | 3 +-
drivers/net/ethernet/intel/i40e/i40e_main.c | 2 +-
drivers/scsi/lpfc/lpfc_init.c | 6 ++-
drivers/scsi/lpfc/lpfc_sli.c | 1 -
drivers/tty/serial/kgdboc.c | 43 ++++++++--------
fs/btrfs/tree-checker.c | 8 ++-
include/linux/tracepoint.h | 6 +--
include/trace/events/sched.h | 12 ++++-
kernel/events/uprobes.c | 12 ++++-
kernel/trace/trace.h | 57 ++++++++++++++++++++--
kernel/trace/trace_functions_graph.c | 4 ++
kernel/trace/trace_irqsoff.c | 2 +
kernel/trace/trace_sched_wakeup.c | 2 +
lib/test_hexdump.c | 2 +-
mm/hugetlb.c | 2 +-
mm/shmem.c | 31 ++++++++++--
mm/userfaultfd.c | 47 +++++++++++++++---
net/tipc/topsrv.c | 2 +-
scripts/unifdef.c | 4 +-
security/selinux/nlmsgtab.c | 13 ++++-
54 files changed, 354 insertions(+), 125 deletions(-)
Commit 07115449919383548d094ff83cc27bd08639a8a1 is on Linux-Next and
this fixes an issue on 4.19.y which fixes an issue where changing for
image size fails.
Can you please apply this patch to 4.19.y?
Thank you
adam
Currently, xattrs values must match the xmatch DFA to match a profile.
This lets users construct profiles to match a file with a specific key
and value with a basic regex.
profile test xattrs(security.apparmor=/usr/bin/*) {}
The xmatch DFA doesn't handle null characters in the xattrs value, since
this is the special character used to indicate that the DFA is transitioning
from matching the profile path to matching the xattr value.
However, both IMA and EVM xattr values hold signatures which potentially
have a null character. It's currently impossible to write a profile that
requires a the presence of an EVM signature without checking the value.
profile test xattrs(security.evm security.apparmor=/usr/bin/*) {}
Add an additional "xattr_keys" array to the profile that only checks the
presence of extended attributes, and not their values.
A modified apparmor_parser that was used to test these changes can be found at:
https://gitlab.com/ericchiang/apparmor/commits/parser-xattrs-keys
To test, build the parser and run the following command:
$ echo '/usr/bin/* xattrs=(user.foo user.bar=bar) {}' | \
./apparmor_parser -r
$ setfattr -n "user.foo" -v "foo" /usr/bin/whoami
$ setfattr -n "user.bar" -v "bar" /usr/bin/whoami
$ whoami # command fails
Signed-off-by: Eric Chiang <ericchiang(a)google.com>
CC: stable(a)vger.kernel.org
---
security/apparmor/domain.c | 22 +++++++++++++++++++---
security/apparmor/include/policy.h | 6 ++++++
security/apparmor/policy.c | 3 +++
security/apparmor/policy_unpack.c | 18 ++++++++++++++++++
4 files changed, 46 insertions(+), 3 deletions(-)
diff --git a/security/apparmor/domain.c b/security/apparmor/domain.c
index 08c88de0ffda..53c46e3e01f0 100644
--- a/security/apparmor/domain.c
+++ b/security/apparmor/domain.c
@@ -319,14 +319,30 @@ static int aa_xattrs_match(const struct linux_binprm *bprm,
char *value = NULL;
int value_size = 0, ret = profile->xattr_count;
- if (!bprm || !profile->xattr_count)
+ if (!bprm)
return 0;
+ d = bprm->file->f_path.dentry;
+
+ if (profile->xattr_keys_count) {
+ /* validate that these attributes are present, ignore values */
+ for (i = 0; i < profile->xattr_keys_count; i++) {
+ size = vfs_getxattr_alloc(d, profile->xattr_keys[i],
+ &value, value_size,
+ GFP_KERNEL);
+ if (size < 0) {
+ ret = -EINVAL;
+ goto out;
+ }
+ }
+ }
+
+ if (!profile->xattr_count)
+ goto out;
+
/* transition from exec match to xattr set */
state = aa_dfa_null_transition(profile->xmatch, state);
- d = bprm->file->f_path.dentry;
-
for (i = 0; i < profile->xattr_count; i++) {
size = vfs_getxattr_alloc(d, profile->xattrs[i], &value,
value_size, GFP_KERNEL);
diff --git a/security/apparmor/include/policy.h b/security/apparmor/include/policy.h
index 8e6707c837be..8ed1d30de7ce 100644
--- a/security/apparmor/include/policy.h
+++ b/security/apparmor/include/policy.h
@@ -112,6 +112,10 @@ struct aa_data {
* @policy: general match rules governing policy
* @file: The set of rules governing basic file access and domain transitions
* @caps: capabilities for the profile
+ * @xattr_count: number of xattrs values
+ * @xattrs: extended attributes whose values must match the xmatch
+ * @xattr_keys_count: number of xattr keys values
+ * @xattr_keys: extended attributes that must be present to match the profile
* @rlimits: rlimits for the profile
*
* @dents: dentries for the profiles file entries in apparmorfs
@@ -152,6 +156,8 @@ struct aa_profile {
int xattr_count;
char **xattrs;
+ int xattr_keys_count;
+ char **xattr_keys;
struct aa_rlimit rlimits;
diff --git a/security/apparmor/policy.c b/security/apparmor/policy.c
index df9c5890a878..e0f9cf8b8318 100644
--- a/security/apparmor/policy.c
+++ b/security/apparmor/policy.c
@@ -231,6 +231,9 @@ void aa_free_profile(struct aa_profile *profile)
for (i = 0; i < profile->xattr_count; i++)
kzfree(profile->xattrs[i]);
kzfree(profile->xattrs);
+ for (i = 0; i < profile->xattr_keys_count; i++)
+ kzfree(profile->xattr_keys[i]);
+ kzfree(profile->xattr_keys);
for (i = 0; i < profile->secmark_count; i++)
kzfree(profile->secmark[i].label);
kzfree(profile->secmark);
diff --git a/security/apparmor/policy_unpack.c b/security/apparmor/policy_unpack.c
index 379682e2a8d5..d1fd75093260 100644
--- a/security/apparmor/policy_unpack.c
+++ b/security/apparmor/policy_unpack.c
@@ -535,6 +535,24 @@ static bool unpack_xattrs(struct aa_ext *e, struct aa_profile *profile)
goto fail;
}
+ if (unpack_nameX(e, AA_STRUCT, "xattr_keys")) {
+ int i, size;
+
+ size = unpack_array(e, NULL);
+ profile->xattr_keys_count = size;
+ profile->xattr_keys = kcalloc(size, sizeof(char *), GFP_KERNEL);
+ if (!profile->xattr_keys)
+ goto fail;
+ for (i = 0; i < size; i++) {
+ if (!unpack_strdup(e, &profile->xattr_keys[i], NULL))
+ goto fail;
+ }
+ if (!unpack_nameX(e, AA_ARRAYEND, NULL))
+ goto fail;
+ if (!unpack_nameX(e, AA_STRUCTEND, NULL))
+ goto fail;
+ }
+
return 1;
fail:
--
2.20.0.rc2.403.gdbc3b29805-goog
The patch titled
Subject: hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined
has been added to the -mm tree. Its filename is
hwpoison-memory_hotplug-allow-hwpoisoned-pages-to-be-offlined.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/hwpoison-memory_hotplug-allow-hwpo…
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/hwpoison-memory_hotplug-allow-hwpo…
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Michal Hocko <mhocko(a)suse.com>
Subject: hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined
We have received a bug report that an injected MCE about faulty memory
prevents memory offline to succeed on 4.4 base kernel. The underlying
reason was that the HWPoison page has an elevated reference count and the
migration keeps failing. There are two problems with that. First of all
it is dubious to migrate the poisoned page because we know that accessing
that memory is possible to fail. Secondly it doesn't make any sense to
migrate a potentially broken content and preserve the memory corruption
over to a new location.
Oscar has found out that 4.4 and the current upstream kernels behave
slightly differently with his simply testcase
===
int main(void)
{
int ret;
int i;
int fd;
char *array = malloc(4096);
char *array_locked = malloc(4096);
fd = open("/tmp/data", O_RDONLY);
read(fd, array, 4095);
for (i = 0; i < 4096; i++)
array_locked[i] = 'd';
ret = mlock((void *)PAGE_ALIGN((unsigned long)array_locked), sizeof(array_locked));
if (ret)
perror("mlock");
sleep (20);
ret = madvise((void *)PAGE_ALIGN((unsigned long)array_locked), 4096, MADV_HWPOISON);
if (ret)
perror("madvise");
for (i = 0; i < 4096; i++)
array_locked[i] = 'd';
return 0;
}
===
+ offline this memory.
In 4.4 kernels he saw the hwpoisoned page to be returned back to the LRU
list
kernel: [<ffffffff81019ac9>] dump_trace+0x59/0x340
kernel: [<ffffffff81019e9a>] show_stack_log_lvl+0xea/0x170
kernel: [<ffffffff8101ac71>] show_stack+0x21/0x40
kernel: [<ffffffff8132bb90>] dump_stack+0x5c/0x7c
kernel: [<ffffffff810815a1>] warn_slowpath_common+0x81/0xb0
kernel: [<ffffffff811a275c>] __pagevec_lru_add_fn+0x14c/0x160
kernel: [<ffffffff811a2eed>] pagevec_lru_move_fn+0xad/0x100
kernel: [<ffffffff811a334c>] __lru_cache_add+0x6c/0xb0
kernel: [<ffffffff81195236>] add_to_page_cache_lru+0x46/0x70
kernel: [<ffffffffa02b4373>] extent_readpages+0xc3/0x1a0 [btrfs]
kernel: [<ffffffff811a16d7>] __do_page_cache_readahead+0x177/0x200
kernel: [<ffffffff811a18c8>] ondemand_readahead+0x168/0x2a0
kernel: [<ffffffff8119673f>] generic_file_read_iter+0x41f/0x660
kernel: [<ffffffff8120e50d>] __vfs_read+0xcd/0x140
kernel: [<ffffffff8120e9ea>] vfs_read+0x7a/0x120
kernel: [<ffffffff8121404b>] kernel_read+0x3b/0x50
kernel: [<ffffffff81215c80>] do_execveat_common.isra.29+0x490/0x6f0
kernel: [<ffffffff81215f08>] do_execve+0x28/0x30
kernel: [<ffffffff81095ddb>] call_usermodehelper_exec_async+0xfb/0x130
kernel: [<ffffffff8161c045>] ret_from_fork+0x55/0x80
And that latter confuses the hotremove path because an LRU page is
attempted to be migrated and that fails due to an elevated reference
count. It is quite possible that the reuse of the HWPoisoned page is some
kind of fixed race condition but I am not really sure about that.
With the upstream kernel the failure is slightly different. The page
doesn't seem to have LRU bit set but isolate_movable_page simply fails and
do_migrate_range simply puts all the isolated pages back to LRU and
therefore no progress is made and scan_movable_pages finds same set of
pages over and over again.
Fix both cases by explicitly checking HWPoisoned pages before we even try
to get reference on the page, try to unmap it if it is still mapped. As
explained by Naoya:
: Hwpoison code never unmapped those for no big reason because
: Ksm pages never dominate memory, so we simply didn't have strong
: motivation to save the pages.
Also put WARN_ON(PageLRU) in case there is a race and we can hit LRU
HWPoison pages which shouldn't happen but I couldn't convince myself about
that. Naoya has noted the following:
: Theoretically no such gurantee, because try_to_unmap() doesn't have a
: guarantee of success and then memory_failure() returns immediately
: when hwpoison_user_mappings fails.
: Or the following code (comes after hwpoison_user_mappings block) also impli=
: es
: that the target page can still have PageLRU flag.
:
: /*
: * Torn down by someone else?
: */
: if (PageLRU(p) && !PageSwapCache(p) && p->mapping =3D=3D NULL) {
: action_result(pfn, MF_MSG_TRUNCATED_LRU, MF_IGNORED);
: res =3D -EBUSY;
: goto out;
: }
:
: So I think it's OK to keep "if (WARN_ON(PageLRU(page)))" block in
: current version of your patch.
Link: http://lkml.kernel.org/r/20181206120135.14079-1-mhocko@kernel.org
Signed-off-by: Michal Hocko <mhocko(a)suse.com>
Reviewed-by: Oscar Salvador <osalvador(a)suse.com>
Debugged-by: Oscar Salvador <osalvador(a)suse.com>
Tested-by: Oscar Salvador <osalvador(a)suse.com>
Acked-by: David Hildenbrand <david(a)redhat.com>
Acked-by: Naoya Horiguchi <n-horiguchi(a)ah.jp.nec.com>
Cc: <stable(a)vger.kernel.org>
Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org>
---
mm/memory_hotplug.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
--- a/mm/memory_hotplug.c~hwpoison-memory_hotplug-allow-hwpoisoned-pages-to-be-offlined
+++ a/mm/memory_hotplug.c
@@ -34,6 +34,7 @@
#include <linux/hugetlb.h>
#include <linux/memblock.h>
#include <linux/compaction.h>
+#include <linux/rmap.h>
#include <asm/tlbflush.h>
@@ -1343,6 +1344,21 @@ do_migrate_range(unsigned long start_pfn
pfn = page_to_pfn(compound_head(page))
+ hpage_nr_pages(page) - 1;
+ /*
+ * HWPoison pages have elevated reference counts so the migration would
+ * fail on them. It also doesn't make any sense to migrate them in the
+ * first place. Still try to unmap such a page in case it is still mapped
+ * (e.g. current hwpoison implementation doesn't unmap KSM pages but keep
+ * the unmap as the catch all safety net).
+ */
+ if (PageHWPoison(page)) {
+ if (WARN_ON(PageLRU(page)))
+ isolate_lru_page(page);
+ if (page_mapped(page))
+ try_to_unmap(page, TTU_IGNORE_MLOCK | TTU_IGNORE_ACCESS);
+ continue;
+ }
+
if (!get_page_unless_zero(page))
continue;
/*
_
Patches currently in -mm which might be from mhocko(a)suse.com are
mm-print-more-information-about-mapping-in-__dump_page.patch
mm-lower-the-printk-loglevel-for-__dump_page-messages.patch
mm-memory_hotplug-drop-pointless-block-alignment-checks-from-__offline_pages.patch
mm-memory_hotplug-print-reason-for-the-offlining-failure.patch
mm-memory_hotplug-be-more-verbose-for-memory-offline-failures.patch
mm-memory_hotplug-be-more-verbose-for-memory-offline-failures-update.patch
mm-memory_hotplug-do-not-clear-numa_node-association-after-hot_remove.patch
hwpoison-memory_hotplug-allow-hwpoisoned-pages-to-be-offlined.patch
From: Tetsuo Handa <penguin-kernel(a)I-love.SAKURA.ne.jp>
commit 400e22499dd92613821374c8c6c88c7225359980 upstream.
Commit 63f53dea0c98 ("mm: warn about allocations which stall for too
long") was a great step for reducing possibility of silent hang up
problem caused by memory allocation stalls. But this commit reverts it,
for it is possible to trigger OOM lockup and/or soft lockups when many
threads concurrently called warn_alloc() (in order to warn about memory
allocation stalls) due to current implementation of printk(), and it is
difficult to obtain useful information due to limitation of synchronous
warning approach.
Current printk() implementation flushes all pending logs using the
context of a thread which called console_unlock(). printk() should be
able to flush all pending logs eventually unless somebody continues
appending to printk() buffer.
Since warn_alloc() started appending to printk() buffer while waiting
for oom_kill_process() to make forward progress when oom_kill_process()
is processing pending logs, it became possible for warn_alloc() to force
oom_kill_process() loop inside printk(). As a result, warn_alloc()
significantly increased possibility of preventing oom_kill_process()
from making forward progress.
---------- Pseudo code start ----------
Before warn_alloc() was introduced:
retry:
if (mutex_trylock(&oom_lock)) {
while (atomic_read(&printk_pending_logs) > 0) {
atomic_dec(&printk_pending_logs);
print_one_log();
}
// Send SIGKILL here.
mutex_unlock(&oom_lock)
}
goto retry;
After warn_alloc() was introduced:
retry:
if (mutex_trylock(&oom_lock)) {
while (atomic_read(&printk_pending_logs) > 0) {
atomic_dec(&printk_pending_logs);
print_one_log();
}
// Send SIGKILL here.
mutex_unlock(&oom_lock)
} else if (waited_for_10seconds()) {
atomic_inc(&printk_pending_logs);
}
goto retry;
---------- Pseudo code end ----------
Although waited_for_10seconds() becomes true once per 10 seconds,
unbounded number of threads can call waited_for_10seconds() at the same
time. Also, since threads doing waited_for_10seconds() keep doing
almost busy loop, the thread doing print_one_log() can use little CPU
resource. Therefore, this situation can be simplified like
---------- Pseudo code start ----------
retry:
if (mutex_trylock(&oom_lock)) {
while (atomic_read(&printk_pending_logs) > 0) {
atomic_dec(&printk_pending_logs);
print_one_log();
}
// Send SIGKILL here.
mutex_unlock(&oom_lock)
} else {
atomic_inc(&printk_pending_logs);
}
goto retry;
---------- Pseudo code end ----------
when printk() is called faster than print_one_log() can process a log.
One of possible mitigation would be to introduce a new lock in order to
make sure that no other series of printk() (either oom_kill_process() or
warn_alloc()) can append to printk() buffer when one series of printk()
(either oom_kill_process() or warn_alloc()) is already in progress.
Such serialization will also help obtaining kernel messages in readable
form.
---------- Pseudo code start ----------
retry:
if (mutex_trylock(&oom_lock)) {
mutex_lock(&oom_printk_lock);
while (atomic_read(&printk_pending_logs) > 0) {
atomic_dec(&printk_pending_logs);
print_one_log();
}
// Send SIGKILL here.
mutex_unlock(&oom_printk_lock);
mutex_unlock(&oom_lock)
} else {
if (mutex_trylock(&oom_printk_lock)) {
atomic_inc(&printk_pending_logs);
mutex_unlock(&oom_printk_lock);
}
}
goto retry;
---------- Pseudo code end ----------
But this commit does not go that direction, for we don't want to
introduce a new lock dependency, and we unlikely be able to obtain
useful information even if we serialized oom_kill_process() and
warn_alloc().
Synchronous approach is prone to unexpected results (e.g. too late [1],
too frequent [2], overlooked [3]). As far as I know, warn_alloc() never
helped with providing information other than "something is going wrong".
I want to consider asynchronous approach which can obtain information
during stalls with possibly relevant threads (e.g. the owner of
oom_lock and kswapd-like threads) and serve as a trigger for actions
(e.g. turn on/off tracepoints, ask libvirt daemon to take a memory dump
of stalling KVM guest for diagnostic purpose).
This commit temporarily loses ability to report e.g. OOM lockup due to
unable to invoke the OOM killer due to !__GFP_FS allocation request.
But asynchronous approach will be able to detect such situation and emit
warning. Thus, let's remove warn_alloc().
[1] https://bugzilla.kernel.org/show_bug.cgi?id=192981
[2] http://lkml.kernel.org/r/CAM_iQpWuPVGc2ky8M-9yukECtS+zKjiDasNymX7rMcBjBFyM_…
[3] commit db73ee0d46379922 ("mm, vmscan: do not loop on too_many_isolated for ever"))
Link: http://lkml.kernel.org/r/1509017339-4802-1-git-send-email-penguin-kernel@I-…
Signed-off-by: Tetsuo Handa <penguin-kernel(a)I-love.SAKURA.ne.jp>
Reported-by: Cong Wang <xiyou.wangcong(a)gmail.com>
Reported-by: yuwang.yuwang <yuwang.yuwang(a)alibaba-inc.com>
Reported-by: Johannes Weiner <hannes(a)cmpxchg.org>
Acked-by: Michal Hocko <mhocko(a)suse.com>
Acked-by: Johannes Weiner <hannes(a)cmpxchg.org>
Cc: Vlastimil Babka <vbabka(a)suse.cz>
Cc: Mel Gorman <mgorman(a)suse.de>
Cc: Dave Hansen <dave.hansen(a)intel.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky(a)gmail.com>
Cc: Petr Mladek <pmladek(a)suse.com>
Cc: Steven Rostedt <rostedt(a)goodmis.org>
Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds(a)linux-foundation.org>
[Resolved backport conflict due to missing 8225196, a8e9925, 9e80c71 and
9a67f64 in 4.9 -- all of which modified this hunk being removed.]
Signed-off-by: Amit Shah <amit(a)kernel.org>
---
mm/page_alloc.c | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 28240ce475d6..3af727d95c17 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -3530,8 +3530,6 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
enum compact_result compact_result;
int compaction_retries;
int no_progress_loops;
- unsigned long alloc_start = jiffies;
- unsigned int stall_timeout = 10 * HZ;
unsigned int cpuset_mems_cookie;
/*
@@ -3704,14 +3702,6 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int order,
if (order > PAGE_ALLOC_COSTLY_ORDER && !(gfp_mask & __GFP_REPEAT))
goto nopage;
- /* Make sure we know about allocations which stall for too long */
- if (time_after(jiffies, alloc_start + stall_timeout)) {
- warn_alloc(gfp_mask,
- "page allocation stalls for %ums, order:%u",
- jiffies_to_msecs(jiffies-alloc_start), order);
- stall_timeout += 10 * HZ;
- }
-
if (should_reclaim_retry(gfp_mask, order, ac, alloc_flags,
did_some_progress > 0, &no_progress_loops))
goto retry;
--
2.15.3.AMZN
On Wed, 2018-08-22 at 09:19 +0200, gregkh(a)linuxfoundation.org wrote:
> This is a note to let you know that I've just added the patch titled
>
> x86/entry/64: Remove %ebx handling from error_entry/exit
>
> to the 4.9-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=sum…
>
> The filename of the patch is:
> x86-entry-64-remove-ebx-handling-from-error_entry-exit.patch
> and it can be found in the queue-4.9 subdirectory.
Can we have it for 4.4 too, please?
> [ Note to stable maintainers: this should probably get applied to all
> kernels. If you're nervous about that, a more conservative fix to
> add xorl %ebx,%ebx; incl %ebx before the jump to error_exit should
> also fix the problem. ]
Can we assume it's always from kernel? The Xen code definitely seems to
handle invoking this from both kernel and userspace contexts.
Shouldn't %ebx get set to !(regs->rsp & 3) ?
Either way, let's just do it in the stable tree exactly the same way
it's done upstream.
> - * On entry, EBX is a "return to kernel mode" flag:
Re-introduce the typo 'EBS' here, to make the patch apply cleanly to
4.4. It's only removing that line anyway.
Or just cherry-pick upstream commit 75ca5b22260ef7 first.
Since commit 3b8c9f1cdfc50 ("arm64: IPI each CPU after invalidating the
I-cache for kernel mappings"), a call to flush_icache_range() will use
an IPI to cross-call other online CPUs so that any stale instructions
are flushed from their pipelines. This triggers a WARN during the
hibernation resume path, where flush_icache_range() is called with
interrupts disabled and is therefore prone to deadlock:
| Disabling non-boot CPUs ...
| CPU1: shutdown
| psci: CPU1 killed.
| CPU2: shutdown
| psci: CPU2 killed.
| CPU3: shutdown
| psci: CPU3 killed.
| WARNING: CPU: 0 PID: 1 at ../kernel/smp.c:416 smp_call_function_many+0xd4/0x350
| Modules linked in:
| CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.20.0-rc4 #1
Since all secondary CPUs have been taken offline prior to invalidating
the I-cache, there's actually no need for an IPI and we can simply call
__flush_icache_range() instead.
Cc: <stable(a)vger.kernel.org>
Fixes: 3b8c9f1cdfc50 ("arm64: IPI each CPU after invalidating the I-cache for kernel mappings")
Reported-by: Kunihiko Hayashi <hayashi.kunihiko(a)socionext.com>
Tested-by: Kunihiko Hayashi <hayashi.kunihiko(a)socionext.com>
Tested-by: James Morse <james.morse(a)arm.com>
Signed-off-by: Will Deacon <will.deacon(a)arm.com>
---
arch/arm64/kernel/hibernate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/kernel/hibernate.c b/arch/arm64/kernel/hibernate.c
index 6b2686d54411..29cdc99688f3 100644
--- a/arch/arm64/kernel/hibernate.c
+++ b/arch/arm64/kernel/hibernate.c
@@ -214,7 +214,7 @@ static int create_safe_exec_page(void *src_start, size_t length,
}
memcpy((void *)dst, src_start, length);
- flush_icache_range(dst, dst + length);
+ __flush_icache_range(dst, dst + length);
pgdp = pgd_offset_raw(allocator(mask), dst_addr);
if (pgd_none(READ_ONCE(*pgdp))) {
--
2.1.4
There is a TM Bad Thing bug that can be caused when you return from a
signal context in a suspended transaction but with ucontext MSR[TS] unset.
This forces regs->msr[TS] to be set at syscall entrance (since the CPU
state is transactional). It also calls treclaim() to flush the transaction
state, which is done based on the live (mfmsr) MSR state.
Since user context MSR[TS] is not set, then restore_tm_sigcontexts() is not
called, thus, not executing recheckpoint, keeping the CPU state as not
transactional. When calling rfid, SRR1 will have MSR[TS] set, but the CPU
state is non transactional, causing the TM Bad Thing with the following
stack:
[ 33.862316] Bad kernel stack pointer 3fffd9dce3e0 at c00000000000c47c
cpu 0x8: Vector: 700 (Program Check) at [c00000003ff7fd40]
pc: c00000000000c47c: fast_exception_return+0xac/0xb4
lr: 00003fff865f442c
sp: 3fffd9dce3e0
msr: 8000000102a03031
current = 0xc00000041f68b700
paca = 0xc00000000fb84800 softe: 0 irq_happened: 0x01
pid = 1721, comm = tm-signal-sigre
Linux version 4.9.0-3-powerpc64le (debian-kernel(a)lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26)
WARNING: exception is not recoverable, can't continue
The same problem happens on 32-bits signal handler, and the fix is very
similar, if tm_recheckpoint() is not executed, then regs->msr[TS] should be
zeroed.
This patch also fixes a sparse warning related to lack of indentation when
CONFIG_PPC_TRANSACTIONAL_MEM is set.
Fixes: 2b0a576d15e0e ("powerpc: Add new transactional memory state to the signal context")
CC: Stable <stable(a)vger.kernel.org> # 3.10+
Signed-off-by: Breno Leitao <leitao(a)debian.org>
---
arch/powerpc/kernel/signal_32.c | 18 +++++++++++++-----
arch/powerpc/kernel/signal_64.c | 20 ++++++++++++++++----
2 files changed, 29 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/kernel/signal_32.c b/arch/powerpc/kernel/signal_32.c
index e6474a45cef5..6327fd79b0fb 100644
--- a/arch/powerpc/kernel/signal_32.c
+++ b/arch/powerpc/kernel/signal_32.c
@@ -1140,11 +1140,11 @@ SYSCALL_DEFINE0(rt_sigreturn)
{
struct rt_sigframe __user *rt_sf;
struct pt_regs *regs = current_pt_regs();
+ int tm_restore = 0;
#ifdef CONFIG_PPC_TRANSACTIONAL_MEM
struct ucontext __user *uc_transact;
unsigned long msr_hi;
unsigned long tmp;
- int tm_restore = 0;
#endif
/* Always make any pending restarted system calls return -EINTR */
current->restart_block.fn = do_no_restart_syscall;
@@ -1192,11 +1192,19 @@ SYSCALL_DEFINE0(rt_sigreturn)
goto bad;
}
}
- if (!tm_restore)
- /* Fall through, for non-TM restore */
+ if (!tm_restore) {
+ /*
+ * Unset regs->msr because ucontext MSR TS is not
+ * set, and recheckpoint was not called. This avoid
+ * hitting a TM Bad thing at RFID
+ */
+ regs->msr &= ~MSR_TS_MASK;
+ }
+ /* Fall through, for non-TM restore */
#endif
- if (do_setcontext(&rt_sf->uc, regs, 1))
- goto bad;
+ if (!tm_restore)
+ if (do_setcontext(&rt_sf->uc, regs, 1))
+ goto bad;
/*
* It's not clear whether or why it is desirable to save the
diff --git a/arch/powerpc/kernel/signal_64.c b/arch/powerpc/kernel/signal_64.c
index 83d51bf586c7..daa28cb72272 100644
--- a/arch/powerpc/kernel/signal_64.c
+++ b/arch/powerpc/kernel/signal_64.c
@@ -740,11 +740,23 @@ SYSCALL_DEFINE0(rt_sigreturn)
&uc_transact->uc_mcontext))
goto badframe;
}
- else
- /* Fall through, for non-TM restore */
#endif
- if (restore_sigcontext(current, NULL, 1, &uc->uc_mcontext))
- goto badframe;
+ /* Fall through, for non-TM restore */
+ if (!MSR_TM_ACTIVE(msr)) {
+ /*
+ * Unset MSR[TS] on the thread regs since MSR from user
+ * context does not have MSR active, and recheckpoint was
+ * not called since restore_tm_sigcontexts() was not called
+ * also.
+ *
+ * If not unsetting it, the code can RFID to userspace with
+ * MSR[TS] set, but without CPU in the proper state,
+ * causing a TM bad thing.
+ */
+ current->thread.regs->msr &= ~MSR_TS_MASK;
+ if (restore_sigcontext(current, NULL, 1, &uc->uc_mcontext))
+ goto badframe;
+ }
if (restore_altstack(&uc->uc_stack))
goto badframe;
--
2.19.0
This addresses a bug in the irqchip core that was triggered
by new code assuming a strict semantic order of the irqchip
calls:
.irq_request_resources()
.irq_enable()
.irq_disable()
.irq_release_resources()
Mostly this is working fine when handled inside manage.c,
the calls are strictly happening in the above assumed order.
However on a Qualcomm platform I get the following in dmesg:
WARNING: CPU: 0 PID: 1 at ../drivers/gpio/gpiolib.c:3513
gpiochip_irq_enable+0x18/0x44
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0
Not tainted 4.20.0-rc4-00002-g1b8a75b25c6e-dirty #9
Hardware name: Generic DT based system
[<c03124ac>] (unwind_backtrace) from [<c030d994>] (show_stack+0x10/0x14)
[<c030d994>] (show_stack) from [<c0b48aec>] (dump_stack+0x78/0x8c)
[<c0b48aec>] (dump_stack) from [<c03213e4>] (__warn+0xe0/0xf8)
[<c03213e4>] (__warn) from [<c0321514>] (warn_slowpath_null+0x40/0x48)
[<c0321514>] (warn_slowpath_null) from [<c06ad5d0>]
(gpiochip_irq_enable+0x18/0x44)
[<c06ad5d0>] (gpiochip_irq_enable) from [<c0371198>] (irq_enable+0x44/0x64)
[<c0371198>] (irq_enable) from [<c0371258>] (__irq_startup+0xa0/0xa8)
[<c0371258>] (__irq_startup) from [<c03712ac>] (irq_startup+0x4c/0x130)
[<c03712ac>] (irq_startup) from [<c03716d0>]
(irq_set_chained_handler_and_data+0x4c/0x78)
[<c03716d0>] (irq_set_chained_handler_and_data) from [<c081c17c>]
(pm8xxx_probe+0x160/0x22c)
[<c081c17c>] (pm8xxx_probe) from [<c07f439c>] (platform_drv_probe+0x48/0x98)
What happens is that when the pm8xxx driver tries to register
a chained IRQ irq_set_chained_handler_and_data() will eventually
set the type and call irq_startup() and thus the .irq_enable()
callback on the irqchip.
This irqchip is in drivers/pinctrl/qcom/pinctrl-msm.c and known
as TLMM.
However, the irqchip core helpers in GPIO assumes that
the .irq_request_resources() callback is always called before
.irq_enable(), and the latter is where module refcount and
also gpiochip_lock_as_irq() is normally called.
When .irq_enable() is called without .irq_request_resources()
having been called first, it seems like we are enabling
an IRQ on a GPIO line that has not first been locked to be
used as IRQ and we get the above warning. This happens since
as of
commit 461c1a7d4733d ("gpiolib: override irq_enable/disable")
this is strictly assumed for all GPIO-based IRQs.
As it seems reasonable to assume that .irq_request_resources()
is always strictly called before .irq_enable(), we add the
irq_[request|release]_resources() functions to the internal
API and call them also when adding a chained irqchip to
an IRQ.
I am a bit uncertain about the call site for
irq_released_resources() inside chip.c, but it appears this
path is for uninstalling a chained handler.
Cc: stable(a)vger.kernel.org
Cc: Bjorn Andersson <bjorn.andersson(a)linaro.org>
Cc: Hans Verkuil <hverkuil(a)xs4all.nl>
Fixes: 461c1a7d4733d ("gpiolib: override irq_enable/disable")
Signed-off-by: Linus Walleij <linus.walleij(a)linaro.org>
---
kernel/irq/chip.c | 2 ++
kernel/irq/internals.h | 3 +++
kernel/irq/manage.c | 4 ++--
3 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c
index a2b3d9de999c..eef67a0b1889 100644
--- a/kernel/irq/chip.c
+++ b/kernel/irq/chip.c
@@ -947,6 +947,7 @@ __irq_do_set_handler(struct irq_desc *desc, irq_flow_handler_t handle,
if (desc->irq_data.chip != &no_irq_chip)
mask_ack_irq(desc);
irq_state_set_disabled(desc);
+ irq_release_resources(desc);
if (is_chained)
desc->action = NULL;
desc->depth = 1;
@@ -974,6 +975,7 @@ __irq_do_set_handler(struct irq_desc *desc, irq_flow_handler_t handle,
irq_settings_set_norequest(desc);
irq_settings_set_nothread(desc);
desc->action = &chained_action;
+ irq_request_resources(desc);
irq_activate_and_startup(desc, IRQ_RESEND);
}
}
diff --git a/kernel/irq/internals.h b/kernel/irq/internals.h
index ca6afa267070..f408a7544c6a 100644
--- a/kernel/irq/internals.h
+++ b/kernel/irq/internals.h
@@ -75,6 +75,9 @@ extern void __enable_irq(struct irq_desc *desc);
#define IRQ_START_FORCE true
#define IRQ_START_COND false
+extern int irq_request_resources(struct irq_desc *desc);
+extern void irq_release_resources(struct irq_desc *desc);
+
extern int irq_activate(struct irq_desc *desc);
extern int irq_activate_and_startup(struct irq_desc *desc, bool resend);
extern int irq_startup(struct irq_desc *desc, bool resend, bool force);
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index 9dbdccab3b6a..38bb0ec07180 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1108,7 +1108,7 @@ static int irq_setup_forced_threading(struct irqaction *new)
return 0;
}
-static int irq_request_resources(struct irq_desc *desc)
+int irq_request_resources(struct irq_desc *desc)
{
struct irq_data *d = &desc->irq_data;
struct irq_chip *c = d->chip;
@@ -1116,7 +1116,7 @@ static int irq_request_resources(struct irq_desc *desc)
return c->irq_request_resources ? c->irq_request_resources(d) : 0;
}
-static void irq_release_resources(struct irq_desc *desc)
+void irq_release_resources(struct irq_desc *desc)
{
struct irq_data *d = &desc->irq_data;
struct irq_chip *c = d->chip;
--
2.19.1
Hi Linus,
As per Greg's instructions, this is part 1 of the set of 2 patches.
This patch switches inode bitmap allocation to static. The whole set
differs from what went into Andrew Morton's trees only by the trivial
cleanup (whitespace etc) which is, according to the rules, not
appropriate for the stable Linux kernel, hence not included in the
set.
The second part will follow in a minute as a separate email.
Kind regards,
Tigran
This is a note to let you know that I've just added the patch titled
gnss: sirf: fix activation retry handling
to my char-misc git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
in the char-misc-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From 06fd9ab12b804451b14d538adbf98a57c2d6846b Mon Sep 17 00:00:00 2001
From: Johan Hovold <johan(a)kernel.org>
Date: Wed, 5 Dec 2018 11:21:49 +0100
Subject: gnss: sirf: fix activation retry handling
Fix activation helper which would return -ETIMEDOUT even if the last
retry attempt was successful.
Also change the semantics of the retries variable so that it actually
holds the number of retries (rather than tries).
Fixes: d2efbbd18b1e ("gnss: add driver for sirfstar-based receivers")
Cc: stable <stable(a)vger.kernel.org> # 4.19
Signed-off-by: Johan Hovold <johan(a)kernel.org>
---
drivers/gnss/sirf.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gnss/sirf.c b/drivers/gnss/sirf.c
index 71d014edd167..2c22836d3ffd 100644
--- a/drivers/gnss/sirf.c
+++ b/drivers/gnss/sirf.c
@@ -168,7 +168,7 @@ static int sirf_set_active(struct sirf_data *data, bool active)
else
timeout = SIRF_HIBERNATE_TIMEOUT;
- while (retries-- > 0) {
+ do {
sirf_pulse_on_off(data);
ret = sirf_wait_for_power_state(data, active, timeout);
if (ret < 0) {
@@ -179,9 +179,9 @@ static int sirf_set_active(struct sirf_data *data, bool active)
}
break;
- }
+ } while (retries--);
- if (retries == 0)
+ if (retries < 0)
return -ETIMEDOUT;
return 0;
--
2.19.2
Commit 78d3a92edbfb ("gpiolib-acpi: Register GpioInt ACPI event handlers
from a late_initcall") deferred the entire acpi_gpiochip_request_interrupt
call for each event resource.
This means it also delays the gpiochip_request_own_desc(..., "ACPI:Event")
call. This is a problem if some AML code reads the GPIO pin before we
run the deferred acpi_gpiochip_request_interrupt, because in that case
acpi_gpio_adr_space_handler() will already have called
gpiochip_request_own_desc(..., "ACPI:OpRegion") causing the call from
acpi_gpiochip_request_interrupt to fail with -EBUSY and we will fail to
register an event handler.
acpi_gpio_adr_space_handler is prepared for acpi_gpiochip_request_interrupt
already having claimed the pin, but the other way around does not work.
One example of a problem this causes, is the event handler for the OTG
ID pin on a Prowise PT301 tablet not registering, keeping the port stuck
in whatever mode it was in during boot and e.g. only allowing charging
after a reboot.
This commit fixes this by only deferring the request_irq call and the
initial run of edge-triggered IRQs instead of deferring all of
acpi_gpiochip_request_interrupt.
Cc: stable(a)vger.kernel.org
Fixes: 78d3a92edbfb ("gpiolib-acpi: Register GpioInt ACPI event ...")
Signed-off-by: Hans de Goede <hdegoede(a)redhat.com>
---
Changes in v2:
-add kernel-doc describing struct acpi_gpio_event members (requested by Mika)
-s/acpi_gpiochip_request_interrupt_desc/acpi_gpiochip_alloc_event/ (req Mika)
-minor style fixups (requested by Andy)
---
drivers/gpio/gpiolib-acpi.c | 144 +++++++++++++++++++++---------------
1 file changed, 84 insertions(+), 60 deletions(-)
diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
index 55b72fbe1631..7f93954c58ea 100644
--- a/drivers/gpio/gpiolib-acpi.c
+++ b/drivers/gpio/gpiolib-acpi.c
@@ -19,11 +19,28 @@
#include "gpiolib.h"
+/**
+ * struct acpi_gpio_event - ACPI GPIO event handler data
+ *
+ * @node: list-entry of the events list of the struct acpi_gpio_chip
+ * @handle: handle of ACPI method to execute when the IRQ triggers
+ * @handler: irq_handler to pass to request_irq when requesting the IRQ
+ * @pin: GPIO pin number on the gpio_chip
+ * @irq: Linux IRQ number for the event, for request_ / free_irq
+ * @irqflags: flags to pass to request_irq when requesting the IRQ
+ * @irq_is_wake: If the ACPI flags indicate the IRQ is a wakeup source
+ * @is_requested: True if request_irq has been done
+ * @desc: gpio_desc for the GPIO pin for this event
+ */
struct acpi_gpio_event {
struct list_head node;
acpi_handle handle;
+ irq_handler_t handler;
unsigned int pin;
unsigned int irq;
+ unsigned long irqflags;
+ bool irq_is_wake;
+ bool irq_requested;
struct gpio_desc *desc;
};
@@ -49,10 +66,10 @@ struct acpi_gpio_chip {
/*
* For gpiochips which call acpi_gpiochip_request_interrupts() before late_init
- * (so builtin drivers) we register the ACPI GpioInt event handlers from a
+ * (so builtin drivers) we register the ACPI GpioInt IRQ handlers from a
* late_initcall_sync handler, so that other builtin drivers can register their
* OpRegions before the event handlers can run. This list contains gpiochips
- * for which the acpi_gpiochip_request_interrupts() has been deferred.
+ * for which the acpi_gpiochip_request_irqs() call has been deferred.
*/
static DEFINE_MUTEX(acpi_gpio_deferred_req_irqs_lock);
static LIST_HEAD(acpi_gpio_deferred_req_irqs_list);
@@ -133,8 +150,42 @@ bool acpi_gpio_get_irq_resource(struct acpi_resource *ares,
}
EXPORT_SYMBOL_GPL(acpi_gpio_get_irq_resource);
-static acpi_status acpi_gpiochip_request_interrupt(struct acpi_resource *ares,
- void *context)
+static void acpi_gpiochip_request_irq(struct acpi_gpio_chip *acpi_gpio,
+ struct acpi_gpio_event *event)
+{
+ int ret, value;
+
+ ret = request_threaded_irq(event->irq, NULL, event->handler,
+ event->irqflags, "ACPI:Event", event);
+ if (ret) {
+ dev_err(acpi_gpio->chip->parent,
+ "Failed to setup interrupt handler for %d\n",
+ event->irq);
+ return;
+ }
+
+ if (event->irq_is_wake)
+ enable_irq_wake(event->irq);
+
+ event->irq_requested = true;
+
+ /* Make sure we trigger the initial state of edge-triggered IRQs */
+ value = gpiod_get_raw_value_cansleep(event->desc);
+ if (((event->irqflags & IRQF_TRIGGER_RISING) && value == 1) ||
+ ((event->irqflags & IRQF_TRIGGER_FALLING) && value == 0))
+ event->handler(event->irq, event);
+}
+
+static void acpi_gpiochip_request_irqs(struct acpi_gpio_chip *acpi_gpio)
+{
+ struct acpi_gpio_event *event;
+
+ list_for_each_entry(event, &acpi_gpio->events, node)
+ acpi_gpiochip_request_irq(acpi_gpio, event);
+}
+
+static acpi_status acpi_gpiochip_alloc_event(struct acpi_resource *ares,
+ void *context)
{
struct acpi_gpio_chip *acpi_gpio = context;
struct gpio_chip *chip = acpi_gpio->chip;
@@ -143,8 +194,7 @@ static acpi_status acpi_gpiochip_request_interrupt(struct acpi_resource *ares,
struct acpi_gpio_event *event;
irq_handler_t handler = NULL;
struct gpio_desc *desc;
- unsigned long irqflags;
- int ret, pin, irq, value;
+ int ret, pin, irq;
if (!acpi_gpio_get_irq_resource(ares, &agpio))
return AE_OK;
@@ -175,8 +225,6 @@ static acpi_status acpi_gpiochip_request_interrupt(struct acpi_resource *ares,
gpiod_direction_input(desc);
- value = gpiod_get_value_cansleep(desc);
-
ret = gpiochip_lock_as_irq(chip, pin);
if (ret) {
dev_err(chip->parent, "Failed to lock GPIO as interrupt\n");
@@ -189,64 +237,42 @@ static acpi_status acpi_gpiochip_request_interrupt(struct acpi_resource *ares,
goto fail_unlock_irq;
}
- irqflags = IRQF_ONESHOT;
+ event = kzalloc(sizeof(*event), GFP_KERNEL);
+ if (!event)
+ goto fail_unlock_irq;
+
+ event->irqflags = IRQF_ONESHOT;
if (agpio->triggering == ACPI_LEVEL_SENSITIVE) {
if (agpio->polarity == ACPI_ACTIVE_HIGH)
- irqflags |= IRQF_TRIGGER_HIGH;
+ event->irqflags |= IRQF_TRIGGER_HIGH;
else
- irqflags |= IRQF_TRIGGER_LOW;
+ event->irqflags |= IRQF_TRIGGER_LOW;
} else {
switch (agpio->polarity) {
case ACPI_ACTIVE_HIGH:
- irqflags |= IRQF_TRIGGER_RISING;
+ event->irqflags |= IRQF_TRIGGER_RISING;
break;
case ACPI_ACTIVE_LOW:
- irqflags |= IRQF_TRIGGER_FALLING;
+ event->irqflags |= IRQF_TRIGGER_FALLING;
break;
default:
- irqflags |= IRQF_TRIGGER_RISING |
- IRQF_TRIGGER_FALLING;
+ event->irqflags |= IRQF_TRIGGER_RISING |
+ IRQF_TRIGGER_FALLING;
break;
}
}
- event = kzalloc(sizeof(*event), GFP_KERNEL);
- if (!event)
- goto fail_unlock_irq;
-
event->handle = evt_handle;
+ event->handler = handler;
event->irq = irq;
+ event->irq_is_wake = agpio->wake_capable == ACPI_WAKE_CAPABLE;
event->pin = pin;
event->desc = desc;
- ret = request_threaded_irq(event->irq, NULL, handler, irqflags,
- "ACPI:Event", event);
- if (ret) {
- dev_err(chip->parent,
- "Failed to setup interrupt handler for %d\n",
- event->irq);
- goto fail_free_event;
- }
-
- if (agpio->wake_capable == ACPI_WAKE_CAPABLE)
- enable_irq_wake(irq);
-
list_add_tail(&event->node, &acpi_gpio->events);
- /*
- * Make sure we trigger the initial state of the IRQ when using RISING
- * or FALLING. Note we run the handlers on late_init, the AML code
- * may refer to OperationRegions from other (builtin) drivers which
- * may be probed after us.
- */
- if (((irqflags & IRQF_TRIGGER_RISING) && value == 1) ||
- ((irqflags & IRQF_TRIGGER_FALLING) && value == 0))
- handler(event->irq, event);
-
return AE_OK;
-fail_free_event:
- kfree(event);
fail_unlock_irq:
gpiochip_unlock_as_irq(chip, pin);
fail_free_desc:
@@ -283,6 +309,9 @@ void acpi_gpiochip_request_interrupts(struct gpio_chip *chip)
if (ACPI_FAILURE(status))
return;
+ acpi_walk_resources(handle, "_AEI",
+ acpi_gpiochip_alloc_event, acpi_gpio);
+
mutex_lock(&acpi_gpio_deferred_req_irqs_lock);
defer = !acpi_gpio_deferred_req_irqs_done;
if (defer)
@@ -293,8 +322,7 @@ void acpi_gpiochip_request_interrupts(struct gpio_chip *chip)
if (defer)
return;
- acpi_walk_resources(handle, "_AEI",
- acpi_gpiochip_request_interrupt, acpi_gpio);
+ acpi_gpiochip_request_irqs(acpi_gpio);
}
EXPORT_SYMBOL_GPL(acpi_gpiochip_request_interrupts);
@@ -331,10 +359,13 @@ void acpi_gpiochip_free_interrupts(struct gpio_chip *chip)
list_for_each_entry_safe_reverse(event, ep, &acpi_gpio->events, node) {
struct gpio_desc *desc;
- if (irqd_is_wakeup_set(irq_get_irq_data(event->irq)))
- disable_irq_wake(event->irq);
+ if (event->irq_requested) {
+ if (event->irq_is_wake)
+ disable_irq_wake(event->irq);
+
+ free_irq(event->irq, event);
+ }
- free_irq(event->irq, event);
desc = event->desc;
if (WARN_ON(IS_ERR(desc)))
continue;
@@ -1200,23 +1231,16 @@ bool acpi_can_fallback_to_crs(struct acpi_device *adev, const char *con_id)
return con_id == NULL;
}
-/* Run deferred acpi_gpiochip_request_interrupts() */
-static int acpi_gpio_handle_deferred_request_interrupts(void)
+/* Run deferred acpi_gpiochip_request_irqs() */
+static int acpi_gpio_handle_deferred_request_irqs(void)
{
struct acpi_gpio_chip *acpi_gpio, *tmp;
mutex_lock(&acpi_gpio_deferred_req_irqs_lock);
list_for_each_entry_safe(acpi_gpio, tmp,
&acpi_gpio_deferred_req_irqs_list,
- deferred_req_irqs_list_entry) {
- acpi_handle handle;
-
- handle = ACPI_HANDLE(acpi_gpio->chip->parent);
- acpi_walk_resources(handle, "_AEI",
- acpi_gpiochip_request_interrupt, acpi_gpio);
-
- list_del_init(&acpi_gpio->deferred_req_irqs_list_entry);
- }
+ deferred_req_irqs_list_entry)
+ acpi_gpiochip_request_irqs(acpi_gpio);
acpi_gpio_deferred_req_irqs_done = true;
mutex_unlock(&acpi_gpio_deferred_req_irqs_lock);
@@ -1224,4 +1248,4 @@ static int acpi_gpio_handle_deferred_request_interrupts(void)
return 0;
}
/* We must use _sync so that this runs after the first deferred_probe run */
-late_initcall_sync(acpi_gpio_handle_deferred_request_interrupts);
+late_initcall_sync(acpi_gpio_handle_deferred_request_irqs);
--
2.19.1
From: Adrian Hunter <adrian.hunter(a)intel.com>
thread__resolve() is used in the sample_addr_correlates_sym() cases
where 'addr' is a destination of a branch which does not necessarily
have the same cpumode as the 'ip'. Use the fallback function in that
case.
This patch depends on patch "perf tools: Add fallback functions for
cases where cpumode is insufficient".
Signed-off-by: Adrian Hunter <adrian.hunter(a)intel.com>
Cc: Andi Kleen <ak(a)linux.intel.com>
Cc: David S. Miller <davem(a)davemloft.net>
Cc: Jiri Olsa <jolsa(a)redhat.com>
Cc: Leo Yan <leo.yan(a)linaro.org>
Cc: Mathieu Poirier <mathieu.poirier(a)linaro.org>
Cc: stable(a)vger.kernel.org
Link: http://lkml.kernel.org/r/20181106210712.12098-3-adrian.hunter@intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme(a)redhat.com>
---
tools/perf/util/event.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/event.c b/tools/perf/util/event.c
index 9431b20c1337..24493200cf80 100644
--- a/tools/perf/util/event.c
+++ b/tools/perf/util/event.c
@@ -1706,7 +1706,7 @@ bool sample_addr_correlates_sym(struct perf_event_attr *attr)
void thread__resolve(struct thread *thread, struct addr_location *al,
struct perf_sample *sample)
{
- thread__find_map(thread, sample->cpumode, sample->addr, al);
+ thread__find_map_fb(thread, sample->cpumode, sample->addr, al);
al->cpu = sample->cpu;
al->sym = NULL;
--
2.19.2
From: Adrian Hunter <adrian.hunter(a)intel.com>
Some architectures have a single address space for kernel and user
addresses, which makes it possible to determine if an address is in
kernel space or user space. Some don't, e.g.: sparc.
Cache that info in perf_env so that, for instance, code needing to
fallback failed symbol lookups at the kernel space in single address
space arches can lookup at userspace.
Signed-off-by: Adrian Hunter <adrian.hunter(a)intel.com>
Cc: Andi Kleen <ak(a)linux.intel.com>
Cc: David S. Miller <davem(a)davemloft.net>
Cc: Jiri Olsa <jolsa(a)redhat.com>
Cc: Leo Yan <leo.yan(a)linaro.org>
Cc: Mathieu Poirier <mathieu.poirier(a)linaro.org>
Cc: stable(a)vger.kernel.org
Link: http://lkml.kernel.org/r/20181106210712.12098-2-adrian.hunter@intel.com
[ split from a larger patch ]
Signed-off-by: Arnaldo Carvalho de Melo <acme(a)redhat.com>
---
tools/perf/arch/common.c | 10 ++++++++++
tools/perf/arch/common.h | 1 +
tools/perf/util/machine.h | 1 +
tools/perf/util/session.c | 4 ++++
4 files changed, 16 insertions(+)
diff --git a/tools/perf/arch/common.c b/tools/perf/arch/common.c
index 82657c01a3b8..5f69fd0b745a 100644
--- a/tools/perf/arch/common.c
+++ b/tools/perf/arch/common.c
@@ -200,3 +200,13 @@ int perf_env__lookup_objdump(struct perf_env *env, const char **path)
return perf_env__lookup_binutils_path(env, "objdump", path);
}
+
+/*
+ * Some architectures have a single address space for kernel and user addresses,
+ * which makes it possible to determine if an address is in kernel space or user
+ * space.
+ */
+bool perf_env__single_address_space(struct perf_env *env)
+{
+ return strcmp(perf_env__arch(env), "sparc");
+}
diff --git a/tools/perf/arch/common.h b/tools/perf/arch/common.h
index 2167001b18c5..c298a446d1f6 100644
--- a/tools/perf/arch/common.h
+++ b/tools/perf/arch/common.h
@@ -5,5 +5,6 @@
#include "../util/env.h"
int perf_env__lookup_objdump(struct perf_env *env, const char **path);
+bool perf_env__single_address_space(struct perf_env *env);
#endif /* ARCH_PERF_COMMON_H */
diff --git a/tools/perf/util/machine.h b/tools/perf/util/machine.h
index d856b85862e2..ca897a73014c 100644
--- a/tools/perf/util/machine.h
+++ b/tools/perf/util/machine.h
@@ -42,6 +42,7 @@ struct machine {
u16 id_hdr_size;
bool comm_exec;
bool kptr_restrict_warned;
+ bool single_address_space;
char *root_dir;
char *mmap_name;
struct threads threads[THREADS__TABLE_SIZE];
diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
index 7d2c8ce6cfad..f8eab197f35c 100644
--- a/tools/perf/util/session.c
+++ b/tools/perf/util/session.c
@@ -24,6 +24,7 @@
#include "thread.h"
#include "thread-stack.h"
#include "stat.h"
+#include "arch/common.h"
static int perf_session__deliver_event(struct perf_session *session,
union perf_event *event,
@@ -150,6 +151,9 @@ struct perf_session *perf_session__new(struct perf_data *data,
session->machines.host.env = &perf_env;
}
+ session->machines.host.single_address_space =
+ perf_env__single_address_space(session->machines.host.env);
+
if (!data || perf_data__is_write(data)) {
/*
* In O_RDONLY mode this will be performed when reading the
--
2.19.2
From: Arnaldo Carvalho de Melo <acme(a)redhat.com>
We'll set a new machine field based on env->arch, which for live mode,
like with 'perf top' means we need to use uname() to figure the name of
the arch, fix perf_env__arch() to consider both (env == NULL) and
(env->arch == NULL) as local operation.
Cc: Adrian Hunter <adrian.hunter(a)intel.com>
Cc: Andi Kleen <ak(a)linux.intel.com>
Cc: David Ahern <dsahern(a)gmail.com>
Cc: David S. Miller <davem(a)davemloft.net>
Cc: Jiri Olsa <jolsa(a)redhat.com>
Cc: Leo Yan <leo.yan(a)linaro.org>
Cc: Mathieu Poirier <mathieu.poirier(a)linaro.org>
Cc: Namhyung Kim <namhyung(a)kernel.org>
Cc: Wang Nan <wangnan0(a)huawei.com>
Cc: stable(a)vger.kernel.org
Link: https://lkml.kernel.org/n/tip-vcz4ufzdon7cwy8dm2ua53xk@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo <acme(a)redhat.com>
---
tools/perf/util/env.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/env.c b/tools/perf/util/env.c
index 59f38c7693f8..4c23779e271a 100644
--- a/tools/perf/util/env.c
+++ b/tools/perf/util/env.c
@@ -166,7 +166,7 @@ const char *perf_env__arch(struct perf_env *env)
struct utsname uts;
char *arch_name;
- if (!env) { /* Assume local operation */
+ if (!env || !env->arch) { /* Assume local operation */
if (uname(&uts) < 0)
return NULL;
arch_name = uts.machine;
--
2.19.2
Braswell is really picky about having our writes posted to memory before
we execute or else the GPU may see stale values. A wmb() is insufficient
as it only ensures the writes are visible to other cores, we need a full
mb() to ensure the writes are in memory and visible to the GPU.
The most frequent failure in flushing before execution is that we see
stale PTE values and execute the wrong pages.
References: 987abd5c62f9 ("drm/i915/execlists: Force write serialisation into context image vs execution")
Signed-off-by: Chris Wilson <chris(a)chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala(a)linux.intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin(a)intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen(a)linux.intel.com>
Cc: stable(a)vger.kernel.org
---
drivers/gpu/drm/i915/intel_lrc.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
index de1e9dc6aec0..e6a86fa4502d 100644
--- a/drivers/gpu/drm/i915/intel_lrc.c
+++ b/drivers/gpu/drm/i915/intel_lrc.c
@@ -379,8 +379,13 @@ static u64 execlists_update_context(struct i915_request *rq)
* may not be visible to the HW prior to the completion of the UC
* register write and that we may begin execution from the context
* before its image is complete leading to invalid PD chasing.
+ *
+ * Furthermore, Braswell, at least, wants a full mb to be sure that
+ * the writes are coherent in memory (visible to the GPU) prior to
+ * execution, and not just visible to other CPUs (as is the result of
+ * wmb).
*/
- wmb();
+ mb();
return ce->lrc_desc;
}
--
2.20.0.rc2
The Gnawty model Chromebook uses pmc_plt_clk_0 instead of pmc_plt_clk_3
for the mclk, just like the Clapper and Swanky models.
This commit adds a DMI based quirk for this.
This fixing audio no longer working on these devices after
commit 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL")
that commit fixes us unnecessary keeping unused clocks on, but in case of
the Gnawty that was breaking audio support since we were not using the
right clock in the cht_bsw_max98090_ti machine driver.
BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=201787
Cc: stable(a)vger.kernel.org
Fixes: 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL")
Reported-and-tested-by: Jaime Pérez <19.jaime.91(a)gmail.com>
Signed-off-by: Hans de Goede <hdegoede(a)redhat.com>
---
sound/soc/intel/boards/cht_bsw_max98090_ti.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/sound/soc/intel/boards/cht_bsw_max98090_ti.c b/sound/soc/intel/boards/cht_bsw_max98090_ti.c
index ad0c98383853..08a5152e635a 100644
--- a/sound/soc/intel/boards/cht_bsw_max98090_ti.c
+++ b/sound/soc/intel/boards/cht_bsw_max98090_ti.c
@@ -396,6 +396,13 @@ static const struct dmi_system_id cht_max98090_quirk_table[] = {
},
.driver_data = (void *)QUIRK_PMC_PLT_CLK_0,
},
+ {
+ /* Gnawty model Chromebook (Acer Chromebook CB3-111) */
+ .matches = {
+ DMI_MATCH(DMI_PRODUCT_NAME, "Gnawty"),
+ },
+ .driver_data = (void *)QUIRK_PMC_PLT_CLK_0,
+ },
{
/* Swanky model Chromebook (Toshiba Chromebook 2) */
.matches = {
--
2.19.2
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Commit: 62b84b3cf313 Linux 4.19.8-rc1
The results of these automated tests are provided below.
Overall result: PASSED
Patch merge: OK
Compile: OK
Kernel tests: OK
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 2 architectures:
aarch64:
make options: make INSTALL_MOD_STRIP=1 -j56 targz-pkg
configuration: https://artifacts.cki-project.org/builds/aarch64/62b84b3cf313e064c6ad249e95…
x86_64:
make options: make INSTALL_MOD_STRIP=1 -j56 targz-pkg
configuration: https://artifacts.cki-project.org/builds/x86_64/62b84b3cf313e064c6ad249e95a…
Hardware testing
----------------
We booted each kernel and ran the following tests:
arm64:
/distribution/kpkginstall (boot test)
LTP lite - release 20180515
xfstests: ext4
xfstests: xfs
/kernel/misc/amtu
x86_64:
/distribution/kpkginstall (boot test)
LTP lite - release 20180515
xfstests: ext4
xfstests: xfs
/kernel/misc/amtu
From: Josef Bacik <jbacik(a)fb.com>
With my delayed refs patches in place we started seeing a large amount
of aborts in __btrfs_free_extent
BTRFS error (device sdb1): unable to find ref byte nr 91947008 parent 0 root 35964 owner 1 offset 0
Call Trace:
? btrfs_merge_delayed_refs+0xaf/0x340
__btrfs_run_delayed_refs+0x6ea/0xfc0
? btrfs_set_path_blocking+0x31/0x60
btrfs_run_delayed_refs+0xeb/0x180
btrfs_commit_transaction+0x179/0x7f0
? btrfs_check_space_for_delayed_refs+0x30/0x50
? should_end_transaction.isra.19+0xe/0x40
btrfs_drop_snapshot+0x41c/0x7c0
btrfs_clean_one_deleted_snapshot+0xb5/0xd0
cleaner_kthread+0xf6/0x120
kthread+0xf8/0x130
? btree_invalidatepage+0x90/0x90
? kthread_bind+0x10/0x10
ret_from_fork+0x35/0x40
This was because btrfs_drop_snapshot depends on the root not being modified
while it's dropping the snapshot. It will unlock the root node (and really
every node) as it walks down the tree, only to re-lock it when it needs to do
something. This is a problem because if we modify the tree we could cow a block
in our path, which free's our reference to that block. Then once we get back to
that shared block we'll free our reference to it again, and get ENOENT when
trying to lookup our extent reference to that block in __btrfs_free_extent.
This is ultimately happening because we have delayed items left to be processed
for our deleted snapshot _after_ all of the inodes are closed for the snapshot.
We only run the delayed inode item if we're deleting the inode, and even then we
do not run the delayed insertions or delayed removals. These can be run at any
point after our final inode does it's last iput, which is what triggers the
snapshot deletion. We can end up with the snapshot deletion happening and then
have the delayed items run on that file system, resulting in the above problem.
This problem has existed forever, however my patches made it much easier to hit
as I wake up the cleaner much more often to deal with delayed iputs, which made
us more likely to start the snapshot dropping work before the transaction
commits, which is when the delayed items would generally be run. Before,
generally speaking, we would run the delayed items, commit the transaction, and
wakeup the cleaner thread to start deleting snapshots, which means we were less
likely to hit this problem. You could still hit it if you had multiple
snapshots to be deleted and ended up with lots of delayed items, but it was
definitely harder.
Fix for now by simply running all the delayed items before starting to drop the
snapshot. We could make this smarter in the future by making the delayed items
per-root, and then simply drop any delayed items for roots that we are going to
delete. But for now just a quick and easy solution is the safest.
Cc: stable(a)vger.kernel.org
Signed-off-by: Josef Bacik <josef(a)toxicpanda.com>
---
v1->v2:
- check for errors from btrfs_run_delayed_items.
- Dave I can reroll the series, but the second version of patch 1 is the same,
let me know what you want.
fs/btrfs/extent-tree.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index dcb699dd57f3..473084eb7a2d 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -9330,6 +9330,10 @@ int btrfs_drop_snapshot(struct btrfs_root *root,
goto out_free;
}
+ err = btrfs_run_delayed_items(trans);
+ if (err)
+ goto out_end_trans;
+
if (block_rsv)
trans->block_rsv = block_rsv;
--
2.14.3
This is a note to let you know that I've just added the patch titled
USB: serial: console: fix reported terminal settings
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From f51ccf46217c28758b1f3b5bc0ccfc00eca658b2 Mon Sep 17 00:00:00 2001
From: Johan Hovold <johan(a)kernel.org>
Date: Tue, 4 Dec 2018 17:00:36 +0100
Subject: USB: serial: console: fix reported terminal settings
The USB-serial console implementation has never reported the actual
terminal settings used. Despite storing the corresponding cflags in its
struct console, these were never honoured on later tty open() where the
tty termios would be left initialised to the driver defaults.
Unlike the serial console implementation, the USB-serial code calls
subdriver open() already at console setup. While calling set_termios()
and write() before open() looks like it could work for some USB-serial
drivers, others definitely do not expect this, so modelling this after
serial core is going to be intrusive, if at all possible.
Instead, use a (renamed) tty helper to save the termios data used at
console setup so that the tty termios reflects the actual terminal
settings after a subsequent tty open().
Note that the calls to tty_init_termios() (tty_driver_install()) and
tty_save_termios() are serialised using the disconnect mutex.
This specifically fixes a regression that was triggered by a recent
change adding software flow control to the pl2303 driver: a getty trying
to disable flow control while leaving the baud rate unchanged would now
also set the baud rate to the driver default (prior to the flow-control
change this had been a noop).
Fixes: 7041d9c3f01b ("USB: serial: pl2303: add support for tx xon/xoff flow control")
Cc: stable <stable(a)vger.kernel.org> # 4.18
Cc: Florian Zumbiehl <florz(a)florz.de>
Reported-by: Jarkko Nikula <jarkko.nikula(a)linux.intel.com>
Tested-by: Jarkko Nikula <jarkko.nikula(a)linux.intel.com>
Acked-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
Signed-off-by: Johan Hovold <johan(a)kernel.org>
---
drivers/tty/tty_io.c | 11 +++++++++--
drivers/usb/serial/console.c | 2 +-
include/linux/tty.h | 1 +
3 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index ee80dfbd5442..687250ec8032 100644
--- a/drivers/tty/tty_io.c
+++ b/drivers/tty/tty_io.c
@@ -1373,7 +1373,13 @@ struct tty_struct *tty_init_dev(struct tty_driver *driver, int idx)
return ERR_PTR(retval);
}
-static void tty_free_termios(struct tty_struct *tty)
+/**
+ * tty_save_termios() - save tty termios data in driver table
+ * @tty: tty whose termios data to save
+ *
+ * Locking: Caller guarantees serialisation with tty_init_termios().
+ */
+void tty_save_termios(struct tty_struct *tty)
{
struct ktermios *tp;
int idx = tty->index;
@@ -1392,6 +1398,7 @@ static void tty_free_termios(struct tty_struct *tty)
}
*tp = tty->termios;
}
+EXPORT_SYMBOL_GPL(tty_save_termios);
/**
* tty_flush_works - flush all works of a tty/pty pair
@@ -1491,7 +1498,7 @@ static void release_tty(struct tty_struct *tty, int idx)
WARN_ON(!mutex_is_locked(&tty_mutex));
if (tty->ops->shutdown)
tty->ops->shutdown(tty);
- tty_free_termios(tty);
+ tty_save_termios(tty);
tty_driver_remove_tty(tty->driver, tty);
tty->port->itty = NULL;
if (tty->link)
diff --git a/drivers/usb/serial/console.c b/drivers/usb/serial/console.c
index 17940589c647..7d289302ff6c 100644
--- a/drivers/usb/serial/console.c
+++ b/drivers/usb/serial/console.c
@@ -101,7 +101,6 @@ static int usb_console_setup(struct console *co, char *options)
cflag |= PARENB;
break;
}
- co->cflag = cflag;
/*
* no need to check the index here: if the index is wrong, console
@@ -164,6 +163,7 @@ static int usb_console_setup(struct console *co, char *options)
serial->type->set_termios(tty, port, &dummy);
tty_port_tty_set(&port->port, NULL);
+ tty_save_termios(tty);
tty_kref_put(tty);
}
tty_port_set_initialized(&port->port, 1);
diff --git a/include/linux/tty.h b/include/linux/tty.h
index 414db2bce715..392138fe59b6 100644
--- a/include/linux/tty.h
+++ b/include/linux/tty.h
@@ -556,6 +556,7 @@ extern struct tty_struct *tty_init_dev(struct tty_driver *driver, int idx);
extern void tty_release_struct(struct tty_struct *tty, int idx);
extern int tty_release(struct inode *inode, struct file *filp);
extern void tty_init_termios(struct tty_struct *tty);
+extern void tty_save_termios(struct tty_struct *tty);
extern int tty_standard_install(struct tty_driver *driver,
struct tty_struct *tty);
--
2.19.2
Suppose adapter (open) recovery is between opened QDIO queues and before
(the end of) initial posting of status read buffers (SRBs). This time
window can be seconds long due to FSF_PROT_HOST_CONNECTION_INITIALIZING
causing by design looping with exponential increase sleeps in the function
performing exchange config data during recovery
[zfcp_erp_adapter_strat_fsf_xconf()]. Recovery triggered by local link up.
Suppose an event occurs for which the FCP channel would send an
unsolicited notification to zfcp by means of a previously posted SRB.
We saw it with local cable pull (link down) in multi-initiator zoning
with multiple NPIV-enabled subchannels of the same shared FCP channel.
As soon as zfcp_erp_adapter_strategy_open_fsf() starts posting the
initial status read buffers from within the adapter's ERP thread,
the channel does send an unsolicited notification.
Since v2.6.27 commit d26ab06ede83 ("[SCSI] zfcp: receiving an unsolicted
status can lead to I/O stall"), zfcp_fsf_status_read_handler() schedules
adapter->stat_work to re-fill the just consumed SRB from a work item.
Now the ERP thread and the work item post SRBs in parallel.
Both contexts call the helper function zfcp_status_read_refill().
The tracking of missing (to be posted / re-filled) SRBs is not thread-safe
due to separate atomic_read() and atomic_dec(), in order to depend on
posting success. Hence, both contexts can see
atomic_read(&adapter->stat_miss) == 1. One of the two contexts posts
one too many SRB. Zfcp gets QDIO_ERROR_SLSB_STATE on the output queue
(trace tag "qdireq1") leading to zfcp_erp_adapter_shutdown() in
zfcp_qdio_handler_error().
An obvious and seemingly clean fix would be to schedule stat_work
from the ERP thread and wait for it to finish. This would serialize
all SRB re-fills. However, we already have another work item wait on the
ERP thread: adapter->scan_work runs zfcp_fc_scan_ports() which calls
zfcp_fc_eval_gpn_ft(). The latter calls zfcp_erp_wait() to wait for all
the open port recoveries during zfcp auto port scan, but in fact it waits
for any pending recovery including an adapter recovery. This approach
leads to a deadlock.
[see also v3.19 commit 18f87a67e6d6 ("zfcp: auto port scan resiliency");
v2.6.37 commit d3e1088d6873
("[SCSI] zfcp: No ERP escalation on gpn_ft eval");
v2.6.28 commit fca55b6fb587
("[SCSI] zfcp: fix deadlock between wq triggered port scan and ERP")
fixing v2.6.27 commit c57a39a45a76
("[SCSI] zfcp: wait until adapter is finished with ERP during auto-port");
v2.6.27 commit cc8c282963bd
("[SCSI] zfcp: Automatically attach remote ports")]
Instead make the accounting of missing SRBs atomic for parallel
execution in both the ERP thread and adapter->stat_work.
Signed-off-by: Steffen Maier <maier(a)linux.ibm.com>
Fixes: d26ab06ede83 ("[SCSI] zfcp: receiving an unsolicted status can lead to I/O stall")
Cc: <stable(a)vger.kernel.org> #2.6.27+
Reviewed-by: Jens Remus <jremus(a)linux.ibm.com>
---
drivers/s390/scsi/zfcp_aux.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/s390/scsi/zfcp_aux.c b/drivers/s390/scsi/zfcp_aux.c
index df10f4e07a4a..882789fff574 100644
--- a/drivers/s390/scsi/zfcp_aux.c
+++ b/drivers/s390/scsi/zfcp_aux.c
@@ -271,16 +271,16 @@ static void zfcp_free_low_mem_buffers(struct zfcp_adapter *adapter)
*/
int zfcp_status_read_refill(struct zfcp_adapter *adapter)
{
- while (atomic_read(&adapter->stat_miss) > 0)
+ while (atomic_add_unless(&adapter->stat_miss, -1, 0))
if (zfcp_fsf_status_read(adapter->qdio)) {
+ atomic_inc(&adapter->stat_miss); /* undo add -1 */
if (atomic_read(&adapter->stat_miss) >=
adapter->stat_read_buf_num) {
zfcp_erp_adapter_reopen(adapter, 0, "axsref1");
return 1;
}
break;
- } else
- atomic_dec(&adapter->stat_miss);
+ }
return 0;
}
--
2.16.4
stable-rc/linux-3.18.y build: 185 builds: 2 failed, 183 passed, 4 errors, 1621 warnings (v3.18.128-34-g7642a7c148f7)
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.128-3…
Tree: stable-rc
Branch: linux-3.18.y
Git Describe: v3.18.128-34-g7642a7c148f7
Git Commit: 7642a7c148f75bee48d892128d79b0f7676114fe
Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Built: 5 unique architectures
Build Failures Detected:
arc: gcc version 7.1.1 20170710 (ARCv2 ISA Linux uClibc toolchain 2017.09)
allnoconfig: FAIL
tinyconfig: FAIL
Errors and Warnings Detected:
arc: gcc version 7.1.1 20170710 (ARCv2 ISA Linux uClibc toolchain 2017.09)
allnoconfig: 2 errors, 666 warnings
tinyconfig: 2 errors, 664 warnings
arm64: gcc version 7.3.0 (Debian 7.3.0-28)
allnoconfig: 2 warnings
defconfig: 2 warnings
tinyconfig: 2 warnings
arm: gcc version 7.3.0 (Debian 7.3.0-28)
acs5k_defconfig: 2 warnings
acs5k_tiny_defconfig: 2 warnings
allnoconfig: 2 warnings
am200epdkit_defconfig: 2 warnings
ape6evm_defconfig: 2 warnings
armadillo800eva_defconfig: 2 warnings
assabet_defconfig: 2 warnings
at91_dt_defconfig: 2 warnings
at91rm9200_defconfig: 2 warnings
at91sam9260_9g20_defconfig: 2 warnings
at91sam9261_9g10_defconfig: 2 warnings
at91sam9263_defconfig: 2 warnings
at91sam9g45_defconfig: 2 warnings
at91sam9rl_defconfig: 2 warnings
at91x40_defconfig: 2 warnings
axm55xx_defconfig: 2 warnings
badge4_defconfig: 2 warnings
bcm2835_defconfig: 2 warnings
bcm_defconfig: 2 warnings
bockw_defconfig: 2 warnings
cerfcube_defconfig: 2 warnings
clps711x_defconfig: 2 warnings
cm_x2xx_defconfig: 2 warnings
cm_x300_defconfig: 2 warnings
cns3420vb_defconfig: 2 warnings
colibri_pxa270_defconfig: 2 warnings
colibri_pxa300_defconfig: 2 warnings
collie_defconfig: 2 warnings
corgi_defconfig: 2 warnings
davinci_all_defconfig: 2 warnings
dove_defconfig: 2 warnings
ebsa110_defconfig: 2 warnings
efm32_defconfig: 2 warnings
em_x270_defconfig: 2 warnings
ep93xx_defconfig: 2 warnings
eseries_pxa_defconfig: 2 warnings
exynos_defconfig: 2 warnings
ezx_defconfig: 2 warnings
footbridge_defconfig: 2 warnings
h3600_defconfig: 2 warnings
h5000_defconfig: 2 warnings
hackkit_defconfig: 2 warnings
hisi_defconfig: 2 warnings
imote2_defconfig: 2 warnings
imx_v4_v5_defconfig: 2 warnings
imx_v6_v7_defconfig: 2 warnings
integrator_defconfig: 2 warnings
iop13xx_defconfig: 2 warnings
iop32x_defconfig: 2 warnings
iop33x_defconfig: 2 warnings
ixp4xx_defconfig: 2 warnings
jornada720_defconfig: 2 warnings
keystone_defconfig: 2 warnings
koelsch_defconfig: 2 warnings
ks8695_defconfig: 2 warnings
kzm9g_defconfig: 2 warnings
lager_defconfig: 2 warnings
lart_defconfig: 2 warnings
lpc32xx_defconfig: 2 warnings
lpd270_defconfig: 2 warnings
lubbock_defconfig: 2 warnings
mackerel_defconfig: 2 warnings
magician_defconfig: 2 warnings
mainstone_defconfig: 2 warnings
marzen_defconfig: 2 warnings
mini2440_defconfig: 2 warnings
mmp2_defconfig: 2 warnings
moxart_defconfig: 2 warnings
msm_defconfig: 2 warnings
multi_v5_defconfig: 2 warnings
multi_v7_defconfig: 2 warnings
mv78xx0_defconfig: 2 warnings
mvebu_v5_defconfig: 2 warnings
mvebu_v7_defconfig: 2 warnings
mxs_defconfig: 2 warnings
neponset_defconfig: 2 warnings
netwinder_defconfig: 2 warnings
netx_defconfig: 2 warnings
nhk8815_defconfig: 2 warnings
nuc910_defconfig: 2 warnings
nuc950_defconfig: 2 warnings
nuc960_defconfig: 2 warnings
omap1_defconfig: 2 warnings
omap2plus_defconfig: 2 warnings
orion5x_defconfig: 2 warnings
palmz72_defconfig: 2 warnings
pcm027_defconfig: 2 warnings
pleb_defconfig: 2 warnings
prima2_defconfig: 2 warnings
pxa168_defconfig: 2 warnings
pxa255-idp_defconfig: 2 warnings
pxa3xx_defconfig: 2 warnings
pxa910_defconfig: 2 warnings
qcom_defconfig: 2 warnings
raumfeld_defconfig: 2 warnings
realview-smp_defconfig: 2 warnings
realview_defconfig: 2 warnings
rpc_defconfig: 2 warnings
s3c2410_defconfig: 2 warnings
s3c6400_defconfig: 2 warnings
s5pv210_defconfig: 2 warnings
sama5_defconfig: 2 warnings
shannon_defconfig: 2 warnings
shmobile_defconfig: 2 warnings
simpad_defconfig: 2 warnings
socfpga_defconfig: 2 warnings
spear13xx_defconfig: 2 warnings
spear3xx_defconfig: 2 warnings
spear6xx_defconfig: 2 warnings
spitz_defconfig: 2 warnings
sunxi_defconfig: 2 warnings
tct_hammer_defconfig: 2 warnings
tegra_defconfig: 2 warnings
tinyconfig: 2 warnings
trizeps4_defconfig: 2 warnings
u300_defconfig: 2 warnings
u8500_defconfig: 2 warnings
versatile_defconfig: 2 warnings
vexpress_defconfig: 2 warnings
viper_defconfig: 2 warnings
vt8500_v6_v7_defconfig: 2 warnings
xcep_defconfig: 2 warnings
zeus_defconfig: 2 warnings
x86: gcc version 7.3.0 (Debian 7.3.0-30)
allnoconfig: 3 warnings
i386_defconfig: 3 warnings
tinyconfig: 3 warnings
x86_64_defconfig: 30 warnings
Errors summary:
2 arch/arc/mm/tlbex.S:348: Error: unknown opcode 'lsl'
2 arch/arc/mm/tlbex.S:291: Error: unknown opcode 'lsl'
Warnings summary:
663 arc-linux-gcc: warning: '-mno-mpy' is deprecated
654 cc1: warning: '-mno-mpy' is deprecated
128 scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
128 scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
3 arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
3 arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
3 arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
2 mm/memory.c:581:7: warning: assignment makes integer from pointer without a cast [-Wint-conversion]
2 kernel/sched/core.c:2766:1: warning: control reaches end of non-void function [-Wreturn-type]
2 include/linux/kernel.h:707:17: warning: comparison of distinct pointer types lacks a cast
2 include/linux/ftrace.h:632:36: warning: calling '__builtin_return_address' with a nonzero argument is unsafe [-Wframe-address]
1 net/sunrpc/clnt.c:527:46: warning: '%s' directive output may be truncated writing up to 107 bytes into a region of size 48 [-Wformat-truncation=]
1 mm/mmap.c:684:2: warning: 'rb_parent' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 mm/mmap.c:684:2: warning: 'rb_link' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 mm/mmap.c:683:2: warning: 'prev' may be used uninitialized in this function [-Wmaybe-uninitialized]
1 lib/string_helpers.c:64:33: warning: '%03lld' directive output may be truncated writing between 3 and 13 bytes into a region of size 7 [-Wformat-truncation=]
1 kernel/relay.c:423:35: warning: 'snprintf' output may be truncated before the last format character [-Wformat-truncation=]
1 fs/nfs/client.c:1380:23: warning: '%u' directive output may be truncated writing between 1 and 7 bytes into a region of size between 3 and 6 [-Wformat-truncation=]
1 drivers/video/fbdev/core/../edid.h:74:72: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/usb/core/usb.c:471:9: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size between 0 and 15 [-Wformat-truncation=]
1 drivers/usb/core/hcd.c:450:34: warning: '%s' directive output may be truncated writing up to 64 bytes into a region of size between 35 and 99 [-Wformat-truncation=]
1 drivers/net/ethernet/broadcom/tg3.c:11184:10: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size between 0 and 15 [-Wformat-truncation=]
1 drivers/net/ethernet/broadcom/tg3.c:11181:9: warning: '-rx-' directive output may be truncated writing 4 bytes into a region of size between 1 and 16 [-Wformat-truncation=]
1 drivers/net/ethernet/broadcom/tg3.c:11178:9: warning: '-tx-' directive output may be truncated writing 4 bytes into a region of size between 1 and 16 [-Wformat-truncation=]
1 drivers/net/ethernet/broadcom/tg3.c:11175:9: warning: '-txrx-' directive output may be truncated writing 6 bytes into a region of size between 1 and 16 [-Wformat-truncation=]
1 drivers/input/mouse/psmouse-base.c:1466:52: warning: '/input0' directive output may be truncated writing 7 bytes into a region of size between 1 and 32 [-Wformat-truncation=]
1 drivers/input/mouse/lifebook.c:287:7: warning: '/input1' directive output may be truncated writing 7 bytes into a region of size between 1 and 32 [-Wformat-truncation=]
1 drivers/input/mouse/alps.c:2418:46: warning: '/input1' directive output may be truncated writing 7 bytes into a region of size between 1 and 32 [-Wformat-truncation=]
1 drivers/input/keyboard/atkbd.c:1069:7: warning: '/input0' directive output may be truncated writing 7 bytes into a region of size between 1 and 32 [-Wformat-truncation=]
1 drivers/ata/libata-core.c:2970:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/ata/libata-core.c:2969:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/ata/libata-core.c:2968:35: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/ata/libata-core.c:2967:32: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/ata/libata-core.c:2966:31: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/ata/libata-core.c:2965:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/ata/libata-core.c:2964:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/ata/libata-core.c:2963:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/ata/libata-core.c:2962:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
1 drivers/ata/libata-core.c:2141:42: warning: '%d' directive output may be truncated writing between 1 and 2 bytes into a region of size between 1 and 11 [-Wformat-truncation=]
1 block/partition-generic.c:41:37: warning: 'snprintf' output may be truncated before the last format character [-Wformat-truncation=]
1 block/partition-generic.c:39:36: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size between 0 and 31 [-Wformat-truncation=]
1 block/elevator.c:841:14: warning: 'snprintf' output may be truncated before the last format character [-Wformat-truncation=]
================================================================================
Detailed per-defconfig build reports:
--------------------------------------------------------------------------------
acs5k_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
acs5k_tiny_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
allnoconfig (arm64) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
allnoconfig (x86) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
--------------------------------------------------------------------------------
allnoconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
allnoconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
allnoconfig (arc) — FAIL, 2 errors, 666 warnings, 0 section mismatches
Errors:
arch/arc/mm/tlbex.S:291: Error: unknown opcode 'lsl'
arch/arc/mm/tlbex.S:348: Error: unknown opcode 'lsl'
Warnings:
arc-linux-gcc: warning: '-mno-mpy' is deprecated
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
mm/memory.c:581:7: warning: assignment makes integer from pointer without a cast [-Wint-conversion]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
mm/mmap.c:684:2: warning: 'rb_link' may be used uninitialized in this function [-Wmaybe-uninitialized]
mm/mmap.c:684:2: warning: 'rb_parent' may be used uninitialized in this function [-Wmaybe-uninitialized]
mm/mmap.c:683:2: warning: 'prev' may be used uninitialized in this function [-Wmaybe-uninitialized]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
kernel/sched/core.c:2766:1: warning: control reaches end of non-void function [-Wreturn-type]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
include/linux/kernel.h:707:17: warning: comparison of distinct pointer types lacks a cast
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
--------------------------------------------------------------------------------
am200epdkit_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ape6evm_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ar7_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
armadillo800eva_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
assabet_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91_dt_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91rm9200_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9260_9g20_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9261_9g10_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9263_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9g45_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91sam9rl_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
at91x40_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ath79_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
axm55xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
badge4_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
bcm2835_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
bcm47xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
bcm63xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
bcm_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
bigsur_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
bockw_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
capcella_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cavium_octeon_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
cerfcube_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
clps711x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cm_x2xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cm_x300_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cns3420vb_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
cobalt_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
colibri_pxa270_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
colibri_pxa300_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
collie_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
corgi_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
davinci_all_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
db1xxx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
decstation_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
defconfig (arm64) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
dove_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
e55_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ebsa110_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
efm32_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
em_x270_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ep93xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
eseries_pxa_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
exynos_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ezx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
footbridge_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
fuloong2e_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
gpr_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
h3600_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
h5000_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
hackkit_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
hisi_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
i386_defconfig (x86) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
--------------------------------------------------------------------------------
imote2_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
imx_v4_v5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
imx_v6_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
integrator_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
iop13xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
iop32x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
iop33x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ip22_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ip27_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ip28_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ip32_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
ixp4xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
jazz_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
jmr3927_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
jornada720_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
keystone_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
koelsch_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ks8695_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
kzm9g_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lager_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lart_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lasat_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
lemote2f_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
loongson3_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
lpc32xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
lpd270_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
ls1b_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
lubbock_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mackerel_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
magician_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mainstone_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
malta_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
malta_kvm_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
malta_kvm_guest_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltaaprp_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltasmvp_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltasmvp_eva_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
maltaup_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
markeins_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
marzen_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mini2440_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mips_paravirt_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
mmp2_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
moxart_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mpc30x_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
msm_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
msp71xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
mtx1_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
multi_v5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
multi_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mv78xx0_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mvebu_v5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mvebu_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
mxs_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
neponset_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
netwinder_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
netx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nhk8815_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nlm_xlp_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nlm_xlr_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
nuc910_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nuc950_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
nuc960_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
omap1_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
omap2plus_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
orion5x_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
palmz72_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pcm027_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pleb_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pnx8335_stb225_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
prima2_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa168_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa255-idp_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa3xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
pxa910_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
qcom_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
qi_lb60_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
raumfeld_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
rb532_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
rbtx49xx_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
realview-smp_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
realview_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
rm200_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
rpc_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
rt305x_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
s3c2410_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
s3c6400_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
s5pv210_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
sama5_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
sb1250_swarm_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
sead3_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
sead3micro_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
shannon_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
shmobile_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
simpad_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
socfpga_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spear13xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spear3xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spear6xx_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
spitz_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
sunxi_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tb0219_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tb0226_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tb0287_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
tct_hammer_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tegra_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tinyconfig (x86) — PASS, 0 errors, 3 warnings, 0 section mismatches
Warnings:
arch/x86/kernel/head_32.S:672: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:677: Warning: ignoring fill value in section `.bss..page_aligned'
arch/x86/kernel/head_32.S:679: Warning: ignoring fill value in section `.bss..page_aligned'
--------------------------------------------------------------------------------
tinyconfig (arm64) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tinyconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
tinyconfig (arc) — FAIL, 2 errors, 664 warnings, 0 section mismatches
Errors:
arch/arc/mm/tlbex.S:291: Error: unknown opcode 'lsl'
arch/arc/mm/tlbex.S:348: Error: unknown opcode 'lsl'
Warnings:
arc-linux-gcc: warning: '-mno-mpy' is deprecated
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
mm/memory.c:581:7: warning: assignment makes integer from pointer without a cast [-Wint-conversion]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
include/linux/kernel.h:707:17: warning: comparison of distinct pointer types lacks a cast
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
kernel/sched/core.c:2766:1: warning: control reaches end of non-void function [-Wreturn-type]
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
arc-linux-gcc: warning: '-mno-mpy' is deprecated
cc1: warning: '-mno-mpy' is deprecated
--------------------------------------------------------------------------------
tinyconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
trizeps4_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
u300_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
u8500_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
versatile_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
vexpress_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
viper_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
vt8500_v6_v7_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
workpad_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
x86_64_defconfig (x86) — PASS, 0 errors, 30 warnings, 0 section mismatches
Warnings:
include/linux/ftrace.h:632:36: warning: calling '__builtin_return_address' with a nonzero argument is unsafe [-Wframe-address]
include/linux/ftrace.h:632:36: warning: calling '__builtin_return_address' with a nonzero argument is unsafe [-Wframe-address]
block/elevator.c:841:14: warning: 'snprintf' output may be truncated before the last format character [-Wformat-truncation=]
kernel/relay.c:423:35: warning: 'snprintf' output may be truncated before the last format character [-Wformat-truncation=]
block/partition-generic.c:39:36: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size between 0 and 31 [-Wformat-truncation=]
block/partition-generic.c:41:37: warning: 'snprintf' output may be truncated before the last format character [-Wformat-truncation=]
fs/nfs/client.c:1380:23: warning: '%u' directive output may be truncated writing between 1 and 7 bytes into a region of size between 3 and 6 [-Wformat-truncation=]
drivers/ata/libata-core.c:2962:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
drivers/ata/libata-core.c:2963:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
drivers/ata/libata-core.c:2964:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
drivers/ata/libata-core.c:2965:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
drivers/ata/libata-core.c:2966:31: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
drivers/ata/libata-core.c:2967:32: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
drivers/ata/libata-core.c:2968:35: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
drivers/ata/libata-core.c:2969:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
drivers/ata/libata-core.c:2970:30: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
drivers/ata/libata-core.c:2141:42: warning: '%d' directive output may be truncated writing between 1 and 2 bytes into a region of size between 1 and 11 [-Wformat-truncation=]
lib/string_helpers.c:64:33: warning: '%03lld' directive output may be truncated writing between 3 and 13 bytes into a region of size 7 [-Wformat-truncation=]
drivers/input/keyboard/atkbd.c:1069:7: warning: '/input0' directive output may be truncated writing 7 bytes into a region of size between 1 and 32 [-Wformat-truncation=]
drivers/input/mouse/psmouse-base.c:1466:52: warning: '/input0' directive output may be truncated writing 7 bytes into a region of size between 1 and 32 [-Wformat-truncation=]
drivers/input/mouse/alps.c:2418:46: warning: '/input1' directive output may be truncated writing 7 bytes into a region of size between 1 and 32 [-Wformat-truncation=]
drivers/input/mouse/lifebook.c:287:7: warning: '/input1' directive output may be truncated writing 7 bytes into a region of size between 1 and 32 [-Wformat-truncation=]
net/sunrpc/clnt.c:527:46: warning: '%s' directive output may be truncated writing up to 107 bytes into a region of size 48 [-Wformat-truncation=]
drivers/net/ethernet/broadcom/tg3.c:11175:9: warning: '-txrx-' directive output may be truncated writing 6 bytes into a region of size between 1 and 16 [-Wformat-truncation=]
drivers/net/ethernet/broadcom/tg3.c:11178:9: warning: '-tx-' directive output may be truncated writing 4 bytes into a region of size between 1 and 16 [-Wformat-truncation=]
drivers/net/ethernet/broadcom/tg3.c:11181:9: warning: '-rx-' directive output may be truncated writing 4 bytes into a region of size between 1 and 16 [-Wformat-truncation=]
drivers/net/ethernet/broadcom/tg3.c:11184:10: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size between 0 and 15 [-Wformat-truncation=]
drivers/usb/core/usb.c:471:9: warning: '%d' directive output may be truncated writing between 1 and 11 bytes into a region of size between 0 and 15 [-Wformat-truncation=]
drivers/usb/core/hcd.c:450:34: warning: '%s' directive output may be truncated writing up to 64 bytes into a region of size between 35 and 99 [-Wformat-truncation=]
drivers/video/fbdev/core/../edid.h:74:72: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
--------------------------------------------------------------------------------
xcep_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
--------------------------------------------------------------------------------
xway_defconfig (mips) — PASS, 0 errors, 0 warnings, 0 section mismatches
--------------------------------------------------------------------------------
zeus_defconfig (arm) — PASS, 0 errors, 2 warnings, 0 section mismatches
Warnings:
scripts/kconfig/confdata.c:767:19: warning: '%s' directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
scripts/kconfig/confdata.c:770:20: warning: '.tmpconfig.' directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
---
For more info write to <info(a)kernelci.org>
Hi Greg/Sasha:
Please apply this series to v4.9.y stable tree. The reason is that v4.9-stable
branch has this patch for stmmac ethernet driver:
"6f37f7b62baa net: stmmac: socfpga: add additional ocp reset line for
Stratix10"
This patch calls devm_reset_control_get_optional(). This call ultimately
fails without this reset patch, becuase the call to
devm_reset_control_get_optional() is returning an error code, which causes the
ethernet driver to fail to load. This patch fixes the call to *_get_optional_*
in that any call to the reset driver with *_optional_* will return 0 instead of
an error value.
Patches 2-6 are needed as well because those patches fix patch 1/6.
Thanks..
Dinh
Heiner Kallweit (1):
reset: core: fix reset_control_put
Masahiro Yamada (2):
reset: make device_reset_optional() really optional
reset: remove remaining WARN_ON() in <linux/reset.h>
Philipp Zabel (2):
reset: fix optional reset_control_get stubs to return NULL
reset: add exported __reset_control_get, return NULL if optional
Ramiro Oliveira (1):
reset: make optional functions really optional
drivers/reset/core.c | 79 +++++++++++++++++++++++++++----------
include/linux/reset.h | 92 +++++++++++++++++++++----------------------
2 files changed, 104 insertions(+), 67 deletions(-)
--
2.17.1
This is a note to let you know that I've just added the patch titled
kgdboc: fix KASAN global-out-of-bounds bug in param_set_kgdboc_var()
to my tty git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
in the tty-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From dada6a43b0402eba438a17ac86fdc64ac56a4607 Mon Sep 17 00:00:00 2001
From: Macpaul Lin <macpaul(a)gmail.com>
Date: Wed, 17 Oct 2018 23:08:38 +0800
Subject: kgdboc: fix KASAN global-out-of-bounds bug in param_set_kgdboc_var()
This patch is trying to fix KE issue due to
"BUG: KASAN: global-out-of-bounds in param_set_kgdboc_var+0x194/0x198"
reported by Syzkaller scan."
[26364:syz-executor0][name:report8t]BUG: KASAN: global-out-of-bounds in param_set_kgdboc_var+0x194/0x198
[26364:syz-executor0][name:report&]Read of size 1 at addr ffffff900e44f95f by task syz-executor0/26364
[26364:syz-executor0][name:report&]
[26364:syz-executor0]CPU: 7 PID: 26364 Comm: syz-executor0 Tainted: G W 0
[26364:syz-executor0]Call trace:
[26364:syz-executor0][<ffffff9008095cf8>] dump_bacIctrace+Ox0/0x470
[26364:syz-executor0][<ffffff9008096de0>] show_stack+0x20/0x30
[26364:syz-executor0][<ffffff90089cc9c8>] dump_stack+Oxd8/0x128
[26364:syz-executor0][<ffffff90084edb38>] print_address_description +0x80/0x4a8
[26364:syz-executor0][<ffffff90084ee270>] kasan_report+Ox178/0x390
[26364:syz-executor0][<ffffff90084ee4a0>] _asan_report_loadi_noabort+Ox18/0x20
[26364:syz-executor0][<ffffff9008b092ac>] param_set_kgdboc_var+Ox194/0x198
[26364:syz-executor0][<ffffff900813af64>] param_attr_store+Ox14c/0x270
[26364:syz-executor0][<ffffff90081394c8>] module_attr_store+0x60/0x90
[26364:syz-executor0][<ffffff90086690c0>] sysfs_kl_write+Ox100/0x158
[26364:syz-executor0][<ffffff9008666d84>] kernfs_fop_write+0x27c/0x3a8
[26364:syz-executor0][<ffffff9008508264>] do_loop_readv_writev+0x114/0x1b0
[26364:syz-executor0][<ffffff9008509ac8>] do_readv_writev+0x4f8/0x5e0
[26364:syz-executor0][<ffffff9008509ce4>] vfs_writev+0x7c/Oxb8
[26364:syz-executor0][<ffffff900850ba64>] SyS_writev+Oxcc/0x208
[26364:syz-executor0][<ffffff90080883f0>] elO_svc_naked +0x24/0x28
[26364:syz-executor0][name:report&]
[26364:syz-executor0][name:report&]The buggy address belongs to the variable:
[26364:syz-executor0][name:report&] kgdb_tty_line+Ox3f/0x40
[26364:syz-executor0][name:report&]
[26364:syz-executor0][name:report&]Memory state around the buggy address:
[26364:syz-executor0] ffffff900e44f800: 00 00 00 00 00 04 fa fa fa fa fa fa 00 fa fa fa
[26364:syz-executor0] ffffff900e44f880: fa fa fa fa 00 fa fa fa fa fa fa fa 00 fa fa fa
[26364:syz-executor0]> ffffff900e44f900: fa fa fa fa 04 fa fa fa fa fa fa fa 00 00 00 00
[26364:syz-executor0][name:report&] ^
[26364:syz-executor0] ffffff900e44f980: 00 fa fa fa fa fa fa fa 04 fa fa fa fa fa fa fa
[26364:syz-executor0] ffffff900e44fa00: 04 fa fa fa fa fa fa fa 00 fa fa fa fa fa fa fa
[26364:syz-executor0][name:report&]
[26364:syz-executor0][name:panic&]Disabling lock debugging due to kernel taint
[26364:syz-executor0]------------[cut here]------------
After checking the source code, we've found there might be an out-of-bounds
access to "config[len - 1]" array when the variable "len" is zero.
Signed-off-by: Macpaul Lin <macpaul(a)gmail.com>
Acked-by: Daniel Thompson <daniel.thompson(a)linaro.org>
Cc: stable <stable(a)vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/tty/serial/kgdboc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/kgdboc.c b/drivers/tty/serial/kgdboc.c
index baeeeaec3f03..6fb312e7af71 100644
--- a/drivers/tty/serial/kgdboc.c
+++ b/drivers/tty/serial/kgdboc.c
@@ -233,7 +233,7 @@ static void kgdboc_put_char(u8 chr)
static int param_set_kgdboc_var(const char *kmessage,
const struct kernel_param *kp)
{
- int len = strlen(kmessage);
+ size_t len = strlen(kmessage);
if (len >= MAX_CONFIG_LEN) {
pr_err("config string too long\n");
@@ -254,7 +254,7 @@ static int param_set_kgdboc_var(const char *kmessage,
strcpy(config, kmessage);
/* Chop out \n char as a result of echo */
- if (config[len - 1] == '\n')
+ if (len && config[len - 1] == '\n')
config[len - 1] = '\0';
if (configured == 1)
--
2.19.2
The driver defines three states for a cppi channel.
- idle: .chan_busy == 0 && not in .pending list
- pending: .chan_busy == 0 && in .pending list
- busy: .chan_busy == 1 && not in .pending list
There are cases in which the cppi channel could be in the pending state
when cppi41_dma_issue_pending() is called after cppi41_runtime_suspend()
is called.
cppi41_stop_chan() has a bug for these cases to set channels to idle state.
It only checks the .chan_busy flag, but not the .pending list, then later
when cppi41_runtime_resume() is called the channels in .pending list will
be transitioned to busy state.
Removing channels from the .pending list solves the problem.
Fixes: 975faaeb9985 ("dma: cppi41: start tear down only if channel is busy")
Cc: stable(a)vger.kernel.org # v3.15+
Signed-off-by: Bin Liu <b-liu(a)ti.com>
---
drivers/dma/ti/cppi41.c | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/ti/cppi41.c b/drivers/dma/ti/cppi41.c
index 1497da367710..e507ec36c0d3 100644
--- a/drivers/dma/ti/cppi41.c
+++ b/drivers/dma/ti/cppi41.c
@@ -723,8 +723,22 @@ static int cppi41_stop_chan(struct dma_chan *chan)
desc_phys = lower_32_bits(c->desc_phys);
desc_num = (desc_phys - cdd->descs_phys) / sizeof(struct cppi41_desc);
- if (!cdd->chan_busy[desc_num])
+ if (!cdd->chan_busy[desc_num]) {
+ struct cppi41_channel *cc, *_ct;
+
+ /*
+ * channels might still be in the pendling list if
+ * cppi41_dma_issue_pending() is called after
+ * cppi41_runtime_suspend() is called
+ */
+ list_for_each_entry_safe(cc, _ct, &cdd->pending, node) {
+ if (cc != c)
+ continue;
+ list_del(&cc->node);
+ break;
+ }
return 0;
+ }
ret = cppi41_tear_down_chan(c);
if (ret)
--
2.17.1
I've backported a number of fixes for security issues affecting 4.9-
stable. All of these are already fixed in 4.14-stable and 4.19-stable.
Most of the issues involve filesystem validation, and I tested with the
reproducers where available.
For the BPF fix, I verified that the self-tests (taken from 4.14)
didn't regress and temporarily added logging to check that the
mitigation is applied when needed.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
From: Michal Hocko <mhocko(a)suse.com>
We have received a bug report that an injected MCE about faulty memory
prevents memory offline to succeed. The underlying reason is that the
HWPoison page has an elevated reference count and the migration keeps
failing. There are two problems with that. First of all it is dubious
to migrate the poisoned page because we know that accessing that memory
is possible to fail. Secondly it doesn't make any sense to migrate a
potentially broken content and preserve the memory corruption over to a
new location.
Oscar has found out that it is the elevated reference count from
memory_failure that is confusing the offlining path. HWPoisoned pages
are isolated from the LRU list but __offline_pages might still try to
migrate them if there is any preceding migrateable pages in the pfn
range. Such a migration would fail due to the reference count but
the migration code would put it back on the LRU list. This is quite
wrong in itself but it would also make scan_movable_pages stumble over
it again without any way out.
This means that the hotremove with hwpoisoned pages has never really
worked (without a luck). HWPoisoning really needs a larger surgery
but an immediate and backportable fix is to skip over these pages during
offlining. Even if they are still mapped for some reason then
try_to_unmap should turn those mappings into hwpoison ptes and cause
SIGBUS on access. Nobody should be really touching the content of the
page so it should be safe to ignore them even when there is a pending
reference count.
Debugged-by: Oscar Salvador <osalvador(a)suse.com>
Cc: stable
Signed-off-by: Michal Hocko <mhocko(a)suse.com>
---
Hi,
I am sending this as an RFC now because I am not fully sure I see all
the consequences myself yet. This has passed a testing by Oscar but I
would highly appreciate a review from Naoya about my assumptions about
hwpoisoning. E.g. it is not entirely clear to me whether there is a
potential case where the page might be still mapped. I have put
try_to_unmap just to be sure. It would be really great if I could drop
that part because then it is not really great which of the TTU flags to
use to cover all potential cases.
I have marked the patch for stable but I have no idea how far back it
should go. Probably everything that already has hotremove and hwpoison
code.
Thanks in advance!
mm/memory_hotplug.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index c6c42a7425e5..08c576d5a633 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -34,6 +34,7 @@
#include <linux/hugetlb.h>
#include <linux/memblock.h>
#include <linux/compaction.h>
+#include <linux/rmap.h>
#include <asm/tlbflush.h>
@@ -1366,6 +1367,17 @@ do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
pfn = page_to_pfn(compound_head(page))
+ hpage_nr_pages(page) - 1;
+ /*
+ * HWPoison pages have elevated reference counts so the migration would
+ * fail on them. It also doesn't make any sense to migrate them in the
+ * first place. Still try to unmap such a page in case it is still mapped.
+ */
+ if (PageHWPoison(page)) {
+ if (page_mapped(page))
+ try_to_unmap(page, TTU_IGNORE_MLOCK | TTU_IGNORE_ACCESS);
+ continue;
+ }
+
if (!get_page_unless_zero(page))
continue;
/*
--
2.19.1
From: Michal Hocko <mhocko(a)suse.com>
We have received a bug report that an injected MCE about faulty memory
prevents memory offline to succeed on 4.4 base kernel. The underlying
reason was that the HWPoison page has an elevated reference count and
the migration keeps failing. There are two problems with that. First
of all it is dubious to migrate the poisoned page because we know that
accessing that memory is possible to fail. Secondly it doesn't make any
sense to migrate a potentially broken content and preserve the memory
corruption over to a new location.
Oscar has found out that 4.4 and the current upstream kernels behave
slightly differently with his simply testcase
===
int main(void)
{
int ret;
int i;
int fd;
char *array = malloc(4096);
char *array_locked = malloc(4096);
fd = open("/tmp/data", O_RDONLY);
read(fd, array, 4095);
for (i = 0; i < 4096; i++)
array_locked[i] = 'd';
ret = mlock((void *)PAGE_ALIGN((unsigned long)array_locked), sizeof(array_locked));
if (ret)
perror("mlock");
sleep (20);
ret = madvise((void *)PAGE_ALIGN((unsigned long)array_locked), 4096, MADV_HWPOISON);
if (ret)
perror("madvise");
for (i = 0; i < 4096; i++)
array_locked[i] = 'd';
return 0;
}
===
+ offline this memory.
In 4.4 kernels he saw the hwpoisoned page to be returned back to the LRU
list
kernel: [<ffffffff81019ac9>] dump_trace+0x59/0x340
kernel: [<ffffffff81019e9a>] show_stack_log_lvl+0xea/0x170
kernel: [<ffffffff8101ac71>] show_stack+0x21/0x40
kernel: [<ffffffff8132bb90>] dump_stack+0x5c/0x7c
kernel: [<ffffffff810815a1>] warn_slowpath_common+0x81/0xb0
kernel: [<ffffffff811a275c>] __pagevec_lru_add_fn+0x14c/0x160
kernel: [<ffffffff811a2eed>] pagevec_lru_move_fn+0xad/0x100
kernel: [<ffffffff811a334c>] __lru_cache_add+0x6c/0xb0
kernel: [<ffffffff81195236>] add_to_page_cache_lru+0x46/0x70
kernel: [<ffffffffa02b4373>] extent_readpages+0xc3/0x1a0 [btrfs]
kernel: [<ffffffff811a16d7>] __do_page_cache_readahead+0x177/0x200
kernel: [<ffffffff811a18c8>] ondemand_readahead+0x168/0x2a0
kernel: [<ffffffff8119673f>] generic_file_read_iter+0x41f/0x660
kernel: [<ffffffff8120e50d>] __vfs_read+0xcd/0x140
kernel: [<ffffffff8120e9ea>] vfs_read+0x7a/0x120
kernel: [<ffffffff8121404b>] kernel_read+0x3b/0x50
kernel: [<ffffffff81215c80>] do_execveat_common.isra.29+0x490/0x6f0
kernel: [<ffffffff81215f08>] do_execve+0x28/0x30
kernel: [<ffffffff81095ddb>] call_usermodehelper_exec_async+0xfb/0x130
kernel: [<ffffffff8161c045>] ret_from_fork+0x55/0x80
And that later confuses the hotremove path because an LRU page is
attempted to be migrated and that fails due to an elevated reference
count. It is quite possible that the reuse of the HWPoisoned page is
some kind of fixed race condition but I am not really sure about that.
With the upstream kernel the failure is slightly different. The page
doesn't seem to have LRU bit set but isolate_movable_page simply fails
and do_migrate_range simply puts all the isolated pages back to LRU and
therefore no progress is made and scan_movable_pages finds same set of
pages over and over again.
Fix both cases by explicitly checking HWPoisoned pages before we even
try to get a reference on the page, try to unmap it if it is still
mapped. As explained by Naoya
: Hwpoison code never unmapped those for no big reason because
: Ksm pages never dominate memory, so we simply didn't have strong
: motivation to save the pages.
Also put WARN_ON(PageLRU) in case there is a race and we can hit LRU
HWPoison pages which shouldn't happen but I couldn't convince myself
about that. Naoya has noted the following
: Theoretically no such gurantee, because try_to_unmap() doesn't have a
: guarantee of success and then memory_failure() returns immediately
: when hwpoison_user_mappings fails.
: Or the following code (comes after hwpoison_user_mappings block) also impli=
: es
: that the target page can still have PageLRU flag.
:
: /*
: * Torn down by someone else?
: */
: if (PageLRU(p) && !PageSwapCache(p) && p->mapping =3D=3D NULL) {
: action_result(pfn, MF_MSG_TRUNCATED_LRU, MF_IGNORED);
: res =3D -EBUSY;
: goto out;
: }
:
: So I think it's OK to keep "if (WARN_ON(PageLRU(page)))" block in
: current version of your patch.
Debugged-by: Oscar Salvador <osalvador(a)suse.com>
Cc: stable
Reviewed-by: Oscar Salvador <osalvador(a)suse.com>
Tested-by: Oscar Salvador <osalvador(a)suse.com>
Acked-by: David Hildenbrand <david(a)redhat.com>
Acked-by: Naoya Horiguchi <n-horiguchi(a)ah.jp.nec.com>
Signed-off-by: Michal Hocko <mhocko(a)suse.com>
---
Hi Andrew,
this has been posted as an RFC [1] previously. It took 2 versions to get
the patch right but it seems that this one should work reasonably well.
I guess we want to have it in linux-next for some time but I do not
expect many people do test MCEs + hotremove considering the breakage is
old and nobody has noticed so far.
[1] http://lkml.kernel.org/r/20181203100309.14784-1-mhocko@kernel.org
mm/memory_hotplug.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index c6c42a7425e5..cfa1a2736876 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -34,6 +34,7 @@
#include <linux/hugetlb.h>
#include <linux/memblock.h>
#include <linux/compaction.h>
+#include <linux/rmap.h>
#include <asm/tlbflush.h>
@@ -1366,6 +1367,21 @@ do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
pfn = page_to_pfn(compound_head(page))
+ hpage_nr_pages(page) - 1;
+ /*
+ * HWPoison pages have elevated reference counts so the migration would
+ * fail on them. It also doesn't make any sense to migrate them in the
+ * first place. Still try to unmap such a page in case it is still mapped
+ * (e.g. current hwpoison implementation doesn't unmap KSM pages but keep
+ * the unmap as the catch all safety net).
+ */
+ if (PageHWPoison(page)) {
+ if (WARN_ON(PageLRU(page)))
+ isolate_lru_page(page);
+ if (page_mapped(page))
+ try_to_unmap(page, TTU_IGNORE_MLOCK | TTU_IGNORE_ACCESS);
+ continue;
+ }
+
if (!get_page_unless_zero(page))
continue;
/*
--
2.19.2
This is a note to let you know that I've just added the patch titled
xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From a7d57abcc8a5bdeb53bbf8e87558e8e0a2c2a29d Mon Sep 17 00:00:00 2001
From: Sandeep Singh <sandeep.singh(a)amd.com>
Date: Wed, 5 Dec 2018 14:22:38 +0200
Subject: xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
Occasionally AMD SNPS 3.0 xHC does not respond to
CSS when set, also it does not flag anything on SRE and HCE
to point the internal xHC errors on USBSTS register. This stalls
the entire system wide suspend and there is no point in stalling
just because of xHC CSS is not responding.
To work around this problem, if the xHC does not flag
anything on SRE and HCE, we can skip the CSS
timeout and allow the system to continue the suspend. Once the
system resume happens we can internally reset the controller
using XHCI_RESET_ON_RESUME quirk
Signed-off-by: Shyam Sundar S K <Shyam-sundar.S-k(a)amd.com>
Signed-off-by: Sandeep Singh <Sandeep.Singh(a)amd.com>
cc: Nehal Shah <Nehal-bakulchandra.Shah(a)amd.com>
Cc: <stable(a)vger.kernel.org>
Tested-by: Kai-Heng Feng <kai.heng.feng(a)canonical.com>
Signed-off-by: Mathias Nyman <mathias.nyman(a)linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/usb/host/xhci-pci.c | 4 ++++
drivers/usb/host/xhci.c | 26 ++++++++++++++++++++++----
drivers/usb/host/xhci.h | 3 +++
3 files changed, 29 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index a9515265db4d..a9ec7051f286 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -139,6 +139,10 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)
pdev->device == 0x43bb))
xhci->quirks |= XHCI_SUSPEND_DELAY;
+ if (pdev->vendor == PCI_VENDOR_ID_AMD &&
+ (pdev->device == 0x15e0 || pdev->device == 0x15e1))
+ xhci->quirks |= XHCI_SNPS_BROKEN_SUSPEND;
+
if (pdev->vendor == PCI_VENDOR_ID_AMD)
xhci->quirks |= XHCI_TRUST_TX_LENGTH;
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index c928dbbff881..c20b85e28d81 100644
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -968,6 +968,7 @@ int xhci_suspend(struct xhci_hcd *xhci, bool do_wakeup)
unsigned int delay = XHCI_MAX_HALT_USEC;
struct usb_hcd *hcd = xhci_to_hcd(xhci);
u32 command;
+ u32 res;
if (!hcd->state)
return 0;
@@ -1021,11 +1022,28 @@ int xhci_suspend(struct xhci_hcd *xhci, bool do_wakeup)
command = readl(&xhci->op_regs->command);
command |= CMD_CSS;
writel(command, &xhci->op_regs->command);
+ xhci->broken_suspend = 0;
if (xhci_handshake(&xhci->op_regs->status,
STS_SAVE, 0, 10 * 1000)) {
- xhci_warn(xhci, "WARN: xHC save state timeout\n");
- spin_unlock_irq(&xhci->lock);
- return -ETIMEDOUT;
+ /*
+ * AMD SNPS xHC 3.0 occasionally does not clear the
+ * SSS bit of USBSTS and when driver tries to poll
+ * to see if the xHC clears BIT(8) which never happens
+ * and driver assumes that controller is not responding
+ * and times out. To workaround this, its good to check
+ * if SRE and HCE bits are not set (as per xhci
+ * Section 5.4.2) and bypass the timeout.
+ */
+ res = readl(&xhci->op_regs->status);
+ if ((xhci->quirks & XHCI_SNPS_BROKEN_SUSPEND) &&
+ (((res & STS_SRE) == 0) &&
+ ((res & STS_HCE) == 0))) {
+ xhci->broken_suspend = 1;
+ } else {
+ xhci_warn(xhci, "WARN: xHC save state timeout\n");
+ spin_unlock_irq(&xhci->lock);
+ return -ETIMEDOUT;
+ }
}
spin_unlock_irq(&xhci->lock);
@@ -1078,7 +1096,7 @@ int xhci_resume(struct xhci_hcd *xhci, bool hibernated)
set_bit(HCD_FLAG_HW_ACCESSIBLE, &xhci->shared_hcd->flags);
spin_lock_irq(&xhci->lock);
- if (xhci->quirks & XHCI_RESET_ON_RESUME)
+ if ((xhci->quirks & XHCI_RESET_ON_RESUME) || xhci->broken_suspend)
hibernated = true;
if (!hibernated) {
diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
index 260b259b72bc..c3515bad5dbb 100644
--- a/drivers/usb/host/xhci.h
+++ b/drivers/usb/host/xhci.h
@@ -1850,6 +1850,7 @@ struct xhci_hcd {
#define XHCI_ZERO_64B_REGS BIT_ULL(32)
#define XHCI_DEFAULT_PM_RUNTIME_ALLOW BIT_ULL(33)
#define XHCI_RESET_PLL_ON_DISCONNECT BIT_ULL(34)
+#define XHCI_SNPS_BROKEN_SUSPEND BIT_ULL(35)
unsigned int num_active_eps;
unsigned int limit_active_eps;
@@ -1879,6 +1880,8 @@ struct xhci_hcd {
void *dbc;
/* platform-specific data -- must come last */
unsigned long priv[0] __aligned(sizeof(s64));
+ /* Broken Suspend flag for SNPS Suspend resume issue */
+ u8 broken_suspend;
};
/* Platform specific overrides to generic XHCI hc_driver ops */
--
2.19.2
This is a note to let you know that I've just added the patch titled
xhci: Prevent U1/U2 link pm states if exit latency is too long
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From 0472bf06c6fd33c1a18aaead4c8f91e5a03d8d7b Mon Sep 17 00:00:00 2001
From: Mathias Nyman <mathias.nyman(a)linux.intel.com>
Date: Wed, 5 Dec 2018 14:22:39 +0200
Subject: xhci: Prevent U1/U2 link pm states if exit latency is too long
Don't allow USB3 U1 or U2 if the latency to wake up from the U-state
reaches the service interval for a periodic endpoint.
This is according to xhci 1.1 specification section 4.23.5.2 extra note:
"Software shall ensure that a device is prevented from entering a U-state
where its worst case exit latency approaches the ESIT."
Allowing too long exit latencies for periodic endpoint confuses xHC
internal scheduling, and new devices may fail to enumerate with a
"Not enough bandwidth for new device state" error from the host.
Cc: <stable(a)vger.kernel.org>
Signed-off-by: Mathias Nyman <mathias.nyman(a)linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/usb/host/xhci.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index c20b85e28d81..dae3be1b9c8f 100644
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -4514,6 +4514,14 @@ static u16 xhci_calculate_u1_timeout(struct xhci_hcd *xhci,
{
unsigned long long timeout_ns;
+ /* Prevent U1 if service interval is shorter than U1 exit latency */
+ if (usb_endpoint_xfer_int(desc) || usb_endpoint_xfer_isoc(desc)) {
+ if (xhci_service_interval_to_ns(desc) <= udev->u1_params.mel) {
+ dev_dbg(&udev->dev, "Disable U1, ESIT shorter than exit latency\n");
+ return USB3_LPM_DISABLED;
+ }
+ }
+
if (xhci->quirks & XHCI_INTEL_HOST)
timeout_ns = xhci_calculate_intel_u1_timeout(udev, desc);
else
@@ -4570,6 +4578,14 @@ static u16 xhci_calculate_u2_timeout(struct xhci_hcd *xhci,
{
unsigned long long timeout_ns;
+ /* Prevent U2 if service interval is shorter than U2 exit latency */
+ if (usb_endpoint_xfer_int(desc) || usb_endpoint_xfer_isoc(desc)) {
+ if (xhci_service_interval_to_ns(desc) <= udev->u2_params.mel) {
+ dev_dbg(&udev->dev, "Disable U2, ESIT shorter than exit latency\n");
+ return USB3_LPM_DISABLED;
+ }
+ }
+
if (xhci->quirks & XHCI_INTEL_HOST)
timeout_ns = xhci_calculate_intel_u2_timeout(udev, desc);
else
--
2.19.2
The patch below does not apply to the 4.19-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From 104f708fd1241b22f808bdf066ab67dc5a051de5 Mon Sep 17 00:00:00 2001
From: Harald Freudenberger <freude(a)linux.ibm.com>
Date: Fri, 9 Nov 2018 14:59:24 +0100
Subject: [PATCH] s390/zcrypt: reinit ap queue state machine during device
probe
Until the vfio-ap driver came into live there was a well known
agreement about the way how ap devices are initialized and their
states when the driver's probe function is called.
However, the vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for interrupts for
the ap device done by the ap bus core code. So when later the vfio
driver releases the device and one of the default zcrypt drivers takes
care of the device the interrupt registration needs to get
renewed. The current code does no renew and result is that requests
send into such a queue will never see a reply processed - the
application hangs.
This patch adds a function which resets the aq queue state machine for
the ap queue device and triggers the walk through the initial states
(which are reset and registration for interrupts). This function is
now called before the driver's probe function is invoked.
When the association between driver and device is released, the
driver's remove function is called. The current implementation calls a
ap queue function ap_queue_remove(). This invokation has been moved to
the ap bus function to make the probe / remove pair for ap bus and
drivers more symmetric.
Fixes: 7e0bdbe5c21c ("s390/zcrypt: AP bus support for alternate driver(s)")
Cc: stable(a)vger.kernel.org # 4.19+
Signed-off-by: Harald Freudenberger <freude(a)linux.ibm.com>
Reviewd-by: Tony Krowiak <akrowiak(a)linux.ibm.com>
Reviewd-by: Martin Schwidefsky <schwidefsky(a)de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky(a)de.ibm.com>
diff --git a/drivers/s390/crypto/ap_bus.c b/drivers/s390/crypto/ap_bus.c
index 048665e4f13d..9f5a201c4c87 100644
--- a/drivers/s390/crypto/ap_bus.c
+++ b/drivers/s390/crypto/ap_bus.c
@@ -775,6 +775,8 @@ static int ap_device_probe(struct device *dev)
drvres = ap_drv->flags & AP_DRIVER_FLAG_DEFAULT;
if (!!devres != !!drvres)
return -ENODEV;
+ /* (re-)init queue's state machine */
+ ap_queue_reinit_state(to_ap_queue(dev));
}
/* Add queue/card to list of active queues/cards */
@@ -807,6 +809,8 @@ static int ap_device_remove(struct device *dev)
struct ap_device *ap_dev = to_ap_dev(dev);
struct ap_driver *ap_drv = ap_dev->drv;
+ if (is_queue_dev(dev))
+ ap_queue_remove(to_ap_queue(dev));
if (ap_drv->remove)
ap_drv->remove(ap_dev);
@@ -1444,10 +1448,6 @@ static void ap_scan_bus(struct work_struct *unused)
aq->ap_dev.device.parent = &ac->ap_dev.device;
dev_set_name(&aq->ap_dev.device,
"%02x.%04x", id, dom);
- /* Start with a device reset */
- spin_lock_bh(&aq->lock);
- ap_wait(ap_sm_event(aq, AP_EVENT_POLL));
- spin_unlock_bh(&aq->lock);
/* Register device */
rc = device_register(&aq->ap_dev.device);
if (rc) {
diff --git a/drivers/s390/crypto/ap_bus.h b/drivers/s390/crypto/ap_bus.h
index 3eed1b36c876..bfc66e4a9de1 100644
--- a/drivers/s390/crypto/ap_bus.h
+++ b/drivers/s390/crypto/ap_bus.h
@@ -254,6 +254,7 @@ struct ap_queue *ap_queue_create(ap_qid_t qid, int device_type);
void ap_queue_remove(struct ap_queue *aq);
void ap_queue_suspend(struct ap_device *ap_dev);
void ap_queue_resume(struct ap_device *ap_dev);
+void ap_queue_reinit_state(struct ap_queue *aq);
struct ap_card *ap_card_create(int id, int queue_depth, int raw_device_type,
int comp_device_type, unsigned int functions);
diff --git a/drivers/s390/crypto/ap_queue.c b/drivers/s390/crypto/ap_queue.c
index 66f7334bcb03..0aa4b3ccc948 100644
--- a/drivers/s390/crypto/ap_queue.c
+++ b/drivers/s390/crypto/ap_queue.c
@@ -718,5 +718,20 @@ void ap_queue_remove(struct ap_queue *aq)
{
ap_flush_queue(aq);
del_timer_sync(&aq->timeout);
+
+ /* reset with zero, also clears irq registration */
+ spin_lock_bh(&aq->lock);
+ ap_zapq(aq->qid);
+ aq->state = AP_STATE_BORKED;
+ spin_unlock_bh(&aq->lock);
}
EXPORT_SYMBOL(ap_queue_remove);
+
+void ap_queue_reinit_state(struct ap_queue *aq)
+{
+ spin_lock_bh(&aq->lock);
+ aq->state = AP_STATE_RESET_START;
+ ap_wait(ap_sm_event(aq, AP_EVENT_POLL));
+ spin_unlock_bh(&aq->lock);
+}
+EXPORT_SYMBOL(ap_queue_reinit_state);
diff --git a/drivers/s390/crypto/zcrypt_cex2a.c b/drivers/s390/crypto/zcrypt_cex2a.c
index 146f54f5cbb8..c50f3e86cc74 100644
--- a/drivers/s390/crypto/zcrypt_cex2a.c
+++ b/drivers/s390/crypto/zcrypt_cex2a.c
@@ -196,7 +196,6 @@ static void zcrypt_cex2a_queue_remove(struct ap_device *ap_dev)
struct ap_queue *aq = to_ap_queue(&ap_dev->device);
struct zcrypt_queue *zq = aq->private;
- ap_queue_remove(aq);
if (zq)
zcrypt_queue_unregister(zq);
}
diff --git a/drivers/s390/crypto/zcrypt_cex2c.c b/drivers/s390/crypto/zcrypt_cex2c.c
index 546f67676734..35c7c6672713 100644
--- a/drivers/s390/crypto/zcrypt_cex2c.c
+++ b/drivers/s390/crypto/zcrypt_cex2c.c
@@ -251,7 +251,6 @@ static void zcrypt_cex2c_queue_remove(struct ap_device *ap_dev)
struct ap_queue *aq = to_ap_queue(&ap_dev->device);
struct zcrypt_queue *zq = aq->private;
- ap_queue_remove(aq);
if (zq)
zcrypt_queue_unregister(zq);
}
diff --git a/drivers/s390/crypto/zcrypt_cex4.c b/drivers/s390/crypto/zcrypt_cex4.c
index f9d4c6c7521d..582ffa7e0f18 100644
--- a/drivers/s390/crypto/zcrypt_cex4.c
+++ b/drivers/s390/crypto/zcrypt_cex4.c
@@ -275,7 +275,6 @@ static void zcrypt_cex4_queue_remove(struct ap_device *ap_dev)
struct ap_queue *aq = to_ap_queue(&ap_dev->device);
struct zcrypt_queue *zq = aq->private;
- ap_queue_remove(aq);
if (zq)
zcrypt_queue_unregister(zq);
}
Yongqin reported that /proc/zoneinfo format is broken in 4.14
due to commit 7aaf77272358 ("mm: don't show nr_indirectly_reclaimable
in /proc/vmstat")
Node 0, zone DMA
per-node stats
nr_inactive_anon 403
nr_active_anon 89123
nr_inactive_file 128887
nr_active_file 47377
nr_unevictable 2053
nr_slab_reclaimable 7510
nr_slab_unreclaimable 10775
nr_isolated_anon 0
nr_isolated_file 0
<...>
nr_vmscan_write 0
nr_vmscan_immediate_reclaim 0
nr_dirtied 6022
nr_written 5985
74240
^^^^^^^^^^
pages free 131656
The problem is caused by the nr_indirectly_reclaimable counter,
which is hidden from the /proc/vmstat, but not from the
/proc/zoneinfo. Let's fix this inconsistency and hide the
counter from /proc/zoneinfo exactly as from /proc/vmstat.
BTW, in 4.19+ the counter has been renamed and exported by
the commit b29940c1abd7 ("mm: rename and change semantics of
nr_indirectly_reclaimable_bytes"), so there is no such a problem
anymore.
Cc: <stable(a)vger.kernel.org> # 4.14.x-4.18.x
Fixes: 7aaf77272358 ("mm: don't show nr_indirectly_reclaimable in /proc/vmstat")
Reported-by: Yongqin Liu <yongqin.liu(a)linaro.org>
Signed-off-by: Roman Gushchin <guro(a)fb.com>
Cc: Vlastimil Babka <vbabka(a)suse.cz>
Cc: Andrew Morton <akpm(a)linux-foundation.org>
---
mm/vmstat.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/mm/vmstat.c b/mm/vmstat.c
index 527ae727d547..6389e876c7a7 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -1500,6 +1500,10 @@ static void zoneinfo_show_print(struct seq_file *m, pg_data_t *pgdat,
if (is_zone_first_populated(pgdat, zone)) {
seq_printf(m, "\n per-node stats");
for (i = 0; i < NR_VM_NODE_STAT_ITEMS; i++) {
+ /* Skip hidden vmstat items. */
+ if (*vmstat_text[i + NR_VM_ZONE_STAT_ITEMS +
+ NR_VM_NUMA_STAT_ITEMS] == '\0')
+ continue;
seq_printf(m, "\n %-12s %lu",
vmstat_text[i + NR_VM_ZONE_STAT_ITEMS +
NR_VM_NUMA_STAT_ITEMS],
--
2.17.2
Hello Greg,
Could you please consider backporting to v4.4 the following commit:
commit b5b5b6fe643391209b08528bef410e0cf299b826
Author: Simon Guo <wei.guo.simon(a)gmail.com>
Date: Fri Oct 7 20:59:40 2016
mm: mlock: avoid increase mm->locked_vm on mlock() when already
mlock2(,MLOCK_ONFAULT)
It seems to be a trivial fix for:
https://bugs.linaro.org/show_bug.cgi?id=4043
(mlock203.c LTP test failing on v4.4)
Thanks in advance,
--
Rafael D. Tinoco
Linaro Kernel Validation Team
Backported mainline commit 6ff38bd40230af35
("mm: cleancache: fix corruption on missed inode invalidation")
From: Pavel Tikhomirov <ptikhomirov(a)virtuozzo.com>
Date: Fri, 30 Nov 2018 14:09:00 -0800
Subject: [PATCH] mm: cleancache: fix corruption on missed inode invalidation
If all pages are deleted from the mapping by memory reclaim and also
moved to the cleancache:
__delete_from_page_cache
(no shadow case)
unaccount_page_cache_page
cleancache_put_page
page_cache_delete
mapping->nrpages -= nr
(nrpages becomes 0)
We don't clean the cleancache for an inode after final file truncation
(removal).
truncate_inode_pages_final
check (nrpages || nrexceptional) is false
no truncate_inode_pages
no cleancache_invalidate_inode(mapping)
These way when reading the new file created with same inode we may get
these trash leftover pages from cleancache and see wrong data instead of
the contents of the new file.
Fix it by always doing truncate_inode_pages which is already ready for
nrpages == 0 && nrexceptional == 0 case and just invalidates inode.
[akpm(a)linux-foundation.org: add comment, per Jan]
Link: http://lkml.kernel.org/r/20181112095734.17979-1-ptikhomirov@virtuozzo.com
Fixes: commit 91b0abe36a7b ("mm + fs: store shadow entries in page cache")
Signed-off-by: Pavel Tikhomirov <ptikhomirov(a)virtuozzo.com>
Reviewed-by: Vasily Averin <vvs(a)virtuozzo.com>
Reviewed-by: Andrey Ryabinin <aryabinin(a)virtuozzo.com>
Reviewed-by: Jan Kara <jack(a)suse.cz>
Cc: Johannes Weiner <hannes(a)cmpxchg.org>
Cc: Mel Gorman <mgorman(a)techsingularity.net>
Cc: Matthew Wilcox <willy(a)infradead.org>
Cc: Andi Kleen <ak(a)linux.intel.com>
Cc: <stable(a)vger.kernel.org>
Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds(a)linux-foundation.org>
Signed-off-by: Vasily Averin <vvs(a)virtuozzo.com>
---
mm/truncate.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/mm/truncate.c b/mm/truncate.c
index 2330223841fb..d3a2737cc188 100644
--- a/mm/truncate.c
+++ b/mm/truncate.c
@@ -471,9 +471,13 @@ void truncate_inode_pages_final(struct address_space *mapping)
*/
spin_lock_irq(&mapping->tree_lock);
spin_unlock_irq(&mapping->tree_lock);
-
- truncate_inode_pages(mapping, 0);
}
+
+ /*
+ * Cleancache needs notification even if there are no pages or shadow
+ * entries.
+ */
+ truncate_inode_pages(mapping, 0);
}
EXPORT_SYMBOL(truncate_inode_pages_final);
--
2.17.1
Hi Greg,
This has been applied to 4.19-stable, but should be needed in
4.14-stable also. I have attached the backported patch and have
also tested with one such DVD where the problem was seen.
--
Regards
Sudip
The patch below does not apply to the 4.9-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From f8397d69daef06d358430d3054662fb597e37c00 Mon Sep 17 00:00:00 2001
From: Nikolay Borisov <nborisov(a)suse.com>
Date: Tue, 6 Nov 2018 16:40:20 +0200
Subject: [PATCH] btrfs: Always try all copies when reading extent buffers
When a metadata read is served the endio routine btree_readpage_end_io_hook
is called which eventually runs the tree-checker. If tree-checker fails
to validate the read eb then it sets EXTENT_BUFFER_CORRUPT flag. This
leads to btree_read_extent_buffer_pages wrongly assuming that all
available copies of this extent buffer are wrong and failing prematurely.
Fix this modify btree_read_extent_buffer_pages to read all copies of
the data.
This failure was exhibitted in xfstests btrfs/124 which would
spuriously fail its balance operations. The reason was that when balance
was run following re-introduction of the missing raid1 disk
__btrfs_map_block would map the read request to stripe 0, which
corresponded to devid 2 (the disk which is being removed in the test):
item 2 key (FIRST_CHUNK_TREE CHUNK_ITEM 3553624064) itemoff 15975 itemsize 112
length 1073741824 owner 2 stripe_len 65536 type DATA|RAID1
io_align 65536 io_width 65536 sector_size 4096
num_stripes 2 sub_stripes 1
stripe 0 devid 2 offset 2156920832
dev_uuid 8466c350-ed0c-4c3b-b17d-6379b445d5c8
stripe 1 devid 1 offset 3553624064
dev_uuid 1265d8db-5596-477e-af03-df08eb38d2ca
This caused read requests for a checksum item that to be routed to the
stale disk which triggered the aforementioned logic involving
EXTENT_BUFFER_CORRUPT flag. This then triggered cascading failures of
the balance operation.
Fixes: a826d6dcb32d ("Btrfs: check items for correctness as we search")
CC: stable(a)vger.kernel.org # 4.4+
Suggested-by: Qu Wenruo <wqu(a)suse.com>
Reviewed-by: Qu Wenruo <wqu(a)suse.com>
Signed-off-by: Nikolay Borisov <nborisov(a)suse.com>
Signed-off-by: David Sterba <dsterba(a)suse.com>
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 3f0b6d1936e8..6d776717d8b3 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -477,9 +477,9 @@ static int btree_read_extent_buffer_pages(struct btrfs_fs_info *fs_info,
int mirror_num = 0;
int failed_mirror = 0;
- clear_bit(EXTENT_BUFFER_CORRUPT, &eb->bflags);
io_tree = &BTRFS_I(fs_info->btree_inode)->io_tree;
while (1) {
+ clear_bit(EXTENT_BUFFER_CORRUPT, &eb->bflags);
ret = read_extent_buffer_pages(io_tree, eb, WAIT_COMPLETE,
mirror_num);
if (!ret) {
@@ -493,15 +493,6 @@ static int btree_read_extent_buffer_pages(struct btrfs_fs_info *fs_info,
break;
}
- /*
- * This buffer's crc is fine, but its contents are corrupted, so
- * there is no reason to read the other copies, they won't be
- * any less wrong.
- */
- if (test_bit(EXTENT_BUFFER_CORRUPT, &eb->bflags) ||
- ret == -EUCLEAN)
- break;
-
num_copies = btrfs_num_copies(fs_info,
eb->start, eb->len);
if (num_copies == 1)
The patch below does not apply to the 4.4-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From f8397d69daef06d358430d3054662fb597e37c00 Mon Sep 17 00:00:00 2001
From: Nikolay Borisov <nborisov(a)suse.com>
Date: Tue, 6 Nov 2018 16:40:20 +0200
Subject: [PATCH] btrfs: Always try all copies when reading extent buffers
When a metadata read is served the endio routine btree_readpage_end_io_hook
is called which eventually runs the tree-checker. If tree-checker fails
to validate the read eb then it sets EXTENT_BUFFER_CORRUPT flag. This
leads to btree_read_extent_buffer_pages wrongly assuming that all
available copies of this extent buffer are wrong and failing prematurely.
Fix this modify btree_read_extent_buffer_pages to read all copies of
the data.
This failure was exhibitted in xfstests btrfs/124 which would
spuriously fail its balance operations. The reason was that when balance
was run following re-introduction of the missing raid1 disk
__btrfs_map_block would map the read request to stripe 0, which
corresponded to devid 2 (the disk which is being removed in the test):
item 2 key (FIRST_CHUNK_TREE CHUNK_ITEM 3553624064) itemoff 15975 itemsize 112
length 1073741824 owner 2 stripe_len 65536 type DATA|RAID1
io_align 65536 io_width 65536 sector_size 4096
num_stripes 2 sub_stripes 1
stripe 0 devid 2 offset 2156920832
dev_uuid 8466c350-ed0c-4c3b-b17d-6379b445d5c8
stripe 1 devid 1 offset 3553624064
dev_uuid 1265d8db-5596-477e-af03-df08eb38d2ca
This caused read requests for a checksum item that to be routed to the
stale disk which triggered the aforementioned logic involving
EXTENT_BUFFER_CORRUPT flag. This then triggered cascading failures of
the balance operation.
Fixes: a826d6dcb32d ("Btrfs: check items for correctness as we search")
CC: stable(a)vger.kernel.org # 4.4+
Suggested-by: Qu Wenruo <wqu(a)suse.com>
Reviewed-by: Qu Wenruo <wqu(a)suse.com>
Signed-off-by: Nikolay Borisov <nborisov(a)suse.com>
Signed-off-by: David Sterba <dsterba(a)suse.com>
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 3f0b6d1936e8..6d776717d8b3 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -477,9 +477,9 @@ static int btree_read_extent_buffer_pages(struct btrfs_fs_info *fs_info,
int mirror_num = 0;
int failed_mirror = 0;
- clear_bit(EXTENT_BUFFER_CORRUPT, &eb->bflags);
io_tree = &BTRFS_I(fs_info->btree_inode)->io_tree;
while (1) {
+ clear_bit(EXTENT_BUFFER_CORRUPT, &eb->bflags);
ret = read_extent_buffer_pages(io_tree, eb, WAIT_COMPLETE,
mirror_num);
if (!ret) {
@@ -493,15 +493,6 @@ static int btree_read_extent_buffer_pages(struct btrfs_fs_info *fs_info,
break;
}
- /*
- * This buffer's crc is fine, but its contents are corrupted, so
- * there is no reason to read the other copies, they won't be
- * any less wrong.
- */
- if (test_bit(EXTENT_BUFFER_CORRUPT, &eb->bflags) ||
- ret == -EUCLEAN)
- break;
-
num_copies = btrfs_num_copies(fs_info,
eb->start, eb->len);
if (num_copies == 1)
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From f8397d69daef06d358430d3054662fb597e37c00 Mon Sep 17 00:00:00 2001
From: Nikolay Borisov <nborisov(a)suse.com>
Date: Tue, 6 Nov 2018 16:40:20 +0200
Subject: [PATCH] btrfs: Always try all copies when reading extent buffers
When a metadata read is served the endio routine btree_readpage_end_io_hook
is called which eventually runs the tree-checker. If tree-checker fails
to validate the read eb then it sets EXTENT_BUFFER_CORRUPT flag. This
leads to btree_read_extent_buffer_pages wrongly assuming that all
available copies of this extent buffer are wrong and failing prematurely.
Fix this modify btree_read_extent_buffer_pages to read all copies of
the data.
This failure was exhibitted in xfstests btrfs/124 which would
spuriously fail its balance operations. The reason was that when balance
was run following re-introduction of the missing raid1 disk
__btrfs_map_block would map the read request to stripe 0, which
corresponded to devid 2 (the disk which is being removed in the test):
item 2 key (FIRST_CHUNK_TREE CHUNK_ITEM 3553624064) itemoff 15975 itemsize 112
length 1073741824 owner 2 stripe_len 65536 type DATA|RAID1
io_align 65536 io_width 65536 sector_size 4096
num_stripes 2 sub_stripes 1
stripe 0 devid 2 offset 2156920832
dev_uuid 8466c350-ed0c-4c3b-b17d-6379b445d5c8
stripe 1 devid 1 offset 3553624064
dev_uuid 1265d8db-5596-477e-af03-df08eb38d2ca
This caused read requests for a checksum item that to be routed to the
stale disk which triggered the aforementioned logic involving
EXTENT_BUFFER_CORRUPT flag. This then triggered cascading failures of
the balance operation.
Fixes: a826d6dcb32d ("Btrfs: check items for correctness as we search")
CC: stable(a)vger.kernel.org # 4.4+
Suggested-by: Qu Wenruo <wqu(a)suse.com>
Reviewed-by: Qu Wenruo <wqu(a)suse.com>
Signed-off-by: Nikolay Borisov <nborisov(a)suse.com>
Signed-off-by: David Sterba <dsterba(a)suse.com>
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 3f0b6d1936e8..6d776717d8b3 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -477,9 +477,9 @@ static int btree_read_extent_buffer_pages(struct btrfs_fs_info *fs_info,
int mirror_num = 0;
int failed_mirror = 0;
- clear_bit(EXTENT_BUFFER_CORRUPT, &eb->bflags);
io_tree = &BTRFS_I(fs_info->btree_inode)->io_tree;
while (1) {
+ clear_bit(EXTENT_BUFFER_CORRUPT, &eb->bflags);
ret = read_extent_buffer_pages(io_tree, eb, WAIT_COMPLETE,
mirror_num);
if (!ret) {
@@ -493,15 +493,6 @@ static int btree_read_extent_buffer_pages(struct btrfs_fs_info *fs_info,
break;
}
- /*
- * This buffer's crc is fine, but its contents are corrupted, so
- * there is no reason to read the other copies, they won't be
- * any less wrong.
- */
- if (test_bit(EXTENT_BUFFER_CORRUPT, &eb->bflags) ||
- ret == -EUCLEAN)
- break;
-
num_copies = btrfs_num_copies(fs_info,
eb->start, eb->len);
if (num_copies == 1)
The patch below does not apply to the 4.9-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From ceff2f4dcd44abf35864d9a99f85ac619e89a01d Mon Sep 17 00:00:00 2001
From: Johan Hovold <johan(a)kernel.org>
Date: Mon, 27 Aug 2018 10:21:46 +0200
Subject: [PATCH] drm/mediatek: fix OF sibling-node lookup
Use the new of_get_compatible_child() helper to lookup the sibling
instead of using of_find_compatible_node(), which searches the entire
tree from a given start node and thus can return an unrelated (i.e.
non-sibling) node.
This also addresses a potential use-after-free (e.g. after probe
deferral) as the tree-wide helper drops a reference to its first
argument (i.e. the parent device node).
While at it, also fix the related cec-node reference leak.
Fixes: 8f83f26891e1 ("drm/mediatek: Add HDMI support")
Cc: stable <stable(a)vger.kernel.org> # 4.8
Cc: Junzhi Zhao <junzhi.zhao(a)mediatek.com>
Cc: Philipp Zabel <p.zabel(a)pengutronix.de>
Cc: CK Hu <ck.hu(a)mediatek.com>
Cc: David Airlie <airlied(a)linux.ie>
Signed-off-by: Johan Hovold <johan(a)kernel.org>
Signed-off-by: Rob Herring <robh(a)kernel.org>
diff --git a/drivers/gpu/drm/mediatek/mtk_hdmi.c b/drivers/gpu/drm/mediatek/mtk_hdmi.c
index 2d45d1dd9554..643f5edd68fe 100644
--- a/drivers/gpu/drm/mediatek/mtk_hdmi.c
+++ b/drivers/gpu/drm/mediatek/mtk_hdmi.c
@@ -1446,8 +1446,7 @@ static int mtk_hdmi_dt_parse_pdata(struct mtk_hdmi *hdmi,
}
/* The CEC module handles HDMI hotplug detection */
- cec_np = of_find_compatible_node(np->parent, NULL,
- "mediatek,mt8173-cec");
+ cec_np = of_get_compatible_child(np->parent, "mediatek,mt8173-cec");
if (!cec_np) {
dev_err(dev, "Failed to find CEC node\n");
return -EINVAL;
@@ -1457,8 +1456,10 @@ static int mtk_hdmi_dt_parse_pdata(struct mtk_hdmi *hdmi,
if (!cec_pdev) {
dev_err(hdmi->dev, "Waiting for CEC device %pOF\n",
cec_np);
+ of_node_put(cec_np);
return -EPROBE_DEFER;
}
+ of_node_put(cec_np);
hdmi->cec_dev = &cec_pdev->dev;
/*
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From f9a7082327e26f54067a49cac2316d31e0cc8ba7 Mon Sep 17 00:00:00 2001
From: Johan Hovold <johan(a)kernel.org>
Date: Mon, 27 Aug 2018 10:21:47 +0200
Subject: [PATCH] drm/msm: fix OF child-node lookup
Use the new of_get_compatible_child() helper to lookup the legacy
pwrlevels child node instead of using of_find_compatible_node(), which
searches the entire tree from a given start node and thus can return an
unrelated (i.e. non-child) node.
This also addresses a potential use-after-free (e.g. after probe
deferral) as the tree-wide helper drops a reference to its first
argument (i.e. the probed device's node).
While at it, also fix the related child-node reference leak.
Fixes: e2af8b6b0ca1 ("drm/msm: gpu: Use OPP tables if we can")
Cc: stable <stable(a)vger.kernel.org> # 4.12
Cc: Jordan Crouse <jcrouse(a)codeaurora.org>
Cc: Rob Clark <robdclark(a)gmail.com>
Cc: David Airlie <airlied(a)linux.ie>
Signed-off-by: Johan Hovold <johan(a)kernel.org>
Signed-off-by: Rob Herring <robh(a)kernel.org>
diff --git a/drivers/gpu/drm/msm/adreno/adreno_gpu.c b/drivers/gpu/drm/msm/adreno/adreno_gpu.c
index da1363a0c54d..93d70f4a2154 100644
--- a/drivers/gpu/drm/msm/adreno/adreno_gpu.c
+++ b/drivers/gpu/drm/msm/adreno/adreno_gpu.c
@@ -633,8 +633,7 @@ static int adreno_get_legacy_pwrlevels(struct device *dev)
struct device_node *child, *node;
int ret;
- node = of_find_compatible_node(dev->of_node, NULL,
- "qcom,gpu-pwrlevels");
+ node = of_get_compatible_child(dev->of_node, "qcom,gpu-pwrlevels");
if (!node) {
dev_err(dev, "Could not find the GPU powerlevels\n");
return -ENXIO;
@@ -655,6 +654,8 @@ static int adreno_get_legacy_pwrlevels(struct device *dev)
dev_pm_opp_add(dev, val, 0);
}
+ of_node_put(node);
+
return 0;
}
From: Alek Du <alek.du(a)intel.com>
We observed some premature timeouts on a virtualization platform, the log
is like this:
case 1:
[159525.255629] mmc1: Internal clock never stabilised.
[159525.255818] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[159525.256049] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00001002
...
[159525.257205] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x0000fa03
>From the clock control register dump, we are pretty sure the clock was
stablized.
case 2:
[ 914.550127] mmc1: Reset 0x2 never completed.
[ 914.550321] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 914.550608] mmc1: sdhci: Sys addr: 0x00000010 | Version: 0x00001002
After checking the sdhci code, we found the timeout check actually has a
little window that the CPU can be scheduled out and when it comes back,
the original time set or check is not valid.
Fixes: 5a436cc0af62 ("mmc: sdhci: Optimize delay loops")
Cc: stable(a)vger.kernel.org # v4.12+
Signed-off-by: Alek Du <alek.du(a)intel.com>
---
drivers/mmc/host/sdhci.c | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
index 99bdae53fa2e..451b08a818a9 100644
--- a/drivers/mmc/host/sdhci.c
+++ b/drivers/mmc/host/sdhci.c
@@ -216,8 +216,12 @@ void sdhci_reset(struct sdhci_host *host, u8 mask)
timeout = ktime_add_ms(ktime_get(), 100);
/* hw clears the bit when it's done */
- while (sdhci_readb(host, SDHCI_SOFTWARE_RESET) & mask) {
- if (ktime_after(ktime_get(), timeout)) {
+ while (1) {
+ bool timedout = ktime_after(ktime_get(), timeout);
+
+ if (!(sdhci_readb(host, SDHCI_SOFTWARE_RESET) & mask))
+ break;
+ if (timedout) {
pr_err("%s: Reset 0x%x never completed.\n",
mmc_hostname(host->mmc), (int)mask);
sdhci_dumpregs(host);
@@ -1608,9 +1612,13 @@ void sdhci_enable_clk(struct sdhci_host *host, u16 clk)
/* Wait max 20 ms */
timeout = ktime_add_ms(ktime_get(), 20);
- while (!((clk = sdhci_readw(host, SDHCI_CLOCK_CONTROL))
- & SDHCI_CLOCK_INT_STABLE)) {
- if (ktime_after(ktime_get(), timeout)) {
+ while (1) {
+ bool timedout = ktime_after(ktime_get(), timeout);
+
+ clk = sdhci_readw(host, SDHCI_CLOCK_CONTROL);
+ if (clk & SDHCI_CLOCK_INT_STABLE)
+ break;
+ if (timedout) {
pr_err("%s: Internal clock never stabilised.\n",
mmc_hostname(host->mmc));
sdhci_dumpregs(host);
--
2.17.1
From: Markus Hofstaetter <markus.hofstaetter(a)ait.ac.at>
commit f16703360da7731a057df2ffa902306819c22398 upstream.
Some PWMs are disabled by default or the default pin setting
does not match the LED_OFF state (e.g., active-low leds).
Hence, the driver may end up reporting 0 brightness, but
the leds are actually on using full brightness, because
it never enforces its default configuration.
So enforce it by calling led_pwm_set() after successfully
registering the device.
Tested on a Phytec phyFLEX i.MX6Q board based on kernel
v3.19.5.
Signed-off-by: Markus Hofstaetter <markus.hofstaetter(a)ait.ac.at>
Tested-by: Markus Hofstaetter <markus.hofstaetter(a)ait.ac.at>
Signed-off-by: Jacek Anaszewski <j.anaszewski(a)samsung.com>
Signed-off-by: Krzysztof Kozlowski <krzk(a)kernel.org>
---
drivers/leds/leds-pwm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/leds/leds-pwm.c b/drivers/leds/leds-pwm.c
index 1d07e3e83d29..3149dbece146 100644
--- a/drivers/leds/leds-pwm.c
+++ b/drivers/leds/leds-pwm.c
@@ -132,6 +132,7 @@ static int led_pwm_add(struct device *dev, struct led_pwm_priv *priv,
ret = led_classdev_register(dev, &led_data->cdev);
if (ret == 0) {
priv->num_leds++;
+ led_pwm_set(&led_data->cdev, led_data->cdev.brightness);
} else {
dev_err(dev, "failed to register PWM led for %s: %d\n",
led->name, ret);
--
2.7.4
The patch below does not apply to the 4.4-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From db7a691a1551a748cb92d9c89c6b190ea87e28d5 Mon Sep 17 00:00:00 2001
From: Michael Guralnik <michaelgur(a)mellanox.com>
Date: Wed, 21 Nov 2018 15:03:54 +0200
Subject: [PATCH] IB/mlx5: Avoid load failure due to unknown link width
If the firmware reports a connection width that is not 1x, 4x, 8x or 12x
it causes the driver to fail during initialization.
To prevent this failure every time a new width is introduced to the RDMA
stack, we will set a default 4x width for these widths which ar unknown to
the driver.
This is needed to allow to run old kernels with new firmware.
Cc: <stable(a)vger.kernel.org> # 4.1
Fixes: 1b5daf11b015 ("IB/mlx5: Avoid using the MAD_IFC command under ISSI > 0 mode")
Signed-off-by: Michael Guralnik <michaelgur(a)mellanox.com>
Reviewed-by: Majd Dibbiny <majd(a)mellanox.com>
Signed-off-by: Leon Romanovsky <leonro(a)mellanox.com>
Signed-off-by: Jason Gunthorpe <jgg(a)mellanox.com>
diff --git a/drivers/infiniband/hw/mlx5/main.c b/drivers/infiniband/hw/mlx5/main.c
index e9c428071df3..3569fda07e07 100644
--- a/drivers/infiniband/hw/mlx5/main.c
+++ b/drivers/infiniband/hw/mlx5/main.c
@@ -1094,31 +1094,26 @@ enum mlx5_ib_width {
MLX5_IB_WIDTH_12X = 1 << 4
};
-static int translate_active_width(struct ib_device *ibdev, u8 active_width,
+static void translate_active_width(struct ib_device *ibdev, u8 active_width,
u8 *ib_width)
{
struct mlx5_ib_dev *dev = to_mdev(ibdev);
- int err = 0;
- if (active_width & MLX5_IB_WIDTH_1X) {
+ if (active_width & MLX5_IB_WIDTH_1X)
*ib_width = IB_WIDTH_1X;
- } else if (active_width & MLX5_IB_WIDTH_2X) {
- mlx5_ib_dbg(dev, "active_width %d is not supported by IB spec\n",
- (int)active_width);
- err = -EINVAL;
- } else if (active_width & MLX5_IB_WIDTH_4X) {
+ else if (active_width & MLX5_IB_WIDTH_4X)
*ib_width = IB_WIDTH_4X;
- } else if (active_width & MLX5_IB_WIDTH_8X) {
+ else if (active_width & MLX5_IB_WIDTH_8X)
*ib_width = IB_WIDTH_8X;
- } else if (active_width & MLX5_IB_WIDTH_12X) {
+ else if (active_width & MLX5_IB_WIDTH_12X)
*ib_width = IB_WIDTH_12X;
- } else {
- mlx5_ib_dbg(dev, "Invalid active_width %d\n",
+ else {
+ mlx5_ib_dbg(dev, "Invalid active_width %d, setting width to default value: 4x\n",
(int)active_width);
- err = -EINVAL;
+ *ib_width = IB_WIDTH_4X;
}
- return err;
+ return;
}
static int mlx5_mtu_to_ib_mtu(int mtu)
@@ -1225,10 +1220,8 @@ static int mlx5_query_hca_port(struct ib_device *ibdev, u8 port,
if (err)
goto out;
- err = translate_active_width(ibdev, ib_link_width_oper,
- &props->active_width);
- if (err)
- goto out;
+ translate_active_width(ibdev, ib_link_width_oper, &props->active_width);
+
err = mlx5_query_port_ib_proto_oper(mdev, &props->active_speed, port);
if (err)
goto out;
The patch below does not apply to the 4.14-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable(a)vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
>From 3054426dc68e5d63aa6a6e9b91ac4ec78e3f3805 Mon Sep 17 00:00:00 2001
From: Pavankumar Kondeti <pkondeti(a)codeaurora.org>
Date: Tue, 30 Oct 2018 12:24:33 +0530
Subject: [PATCH] sched, trace: Fix prev_state output in sched_switch
tracepoint
commit 3f5fe9fef5b2 ("sched/debug: Fix task state recording/printout")
tried to fix the problem introduced by a previous commit efb40f588b43
("sched/tracing: Fix trace_sched_switch task-state printing"). However
the prev_state output in sched_switch is still broken.
task_state_index() uses fls() which considers the LSB as 1. Left
shifting 1 by this value gives an incorrect mapping to the task state.
Fix this by decrementing the value returned by __get_task_state()
before shifting.
Link: http://lkml.kernel.org/r/1540882473-1103-1-git-send-email-pkondeti@codeauro…
Cc: stable(a)vger.kernel.org
Fixes: 3f5fe9fef5b2 ("sched/debug: Fix task state recording/printout")
Signed-off-by: Pavankumar Kondeti <pkondeti(a)codeaurora.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt(a)goodmis.org>
diff --git a/include/trace/events/sched.h b/include/trace/events/sched.h
index f07b270d4fc4..9a4bdfadab07 100644
--- a/include/trace/events/sched.h
+++ b/include/trace/events/sched.h
@@ -107,6 +107,8 @@ DEFINE_EVENT(sched_wakeup_template, sched_wakeup_new,
#ifdef CREATE_TRACE_POINTS
static inline long __trace_sched_switch_state(bool preempt, struct task_struct *p)
{
+ unsigned int state;
+
#ifdef CONFIG_SCHED_DEBUG
BUG_ON(p != current);
#endif /* CONFIG_SCHED_DEBUG */
@@ -118,7 +120,15 @@ static inline long __trace_sched_switch_state(bool preempt, struct task_struct *
if (preempt)
return TASK_REPORT_MAX;
- return 1 << task_state_index(p);
+ /*
+ * task_state_index() uses fls() and returns a value from 0-8 range.
+ * Decrement it by 1 (except TASK_RUNNING state i.e 0) before using
+ * it for left shift operation to get the correct task->state
+ * mapping.
+ */
+ state = task_state_index(p);
+
+ return state ? (1 << (state - 1)) : state;
}
#endif /* CREATE_TRACE_POINTS */
On Sun, Dec 2, 2018 at 4:51 PM Sasha Levin <sashal(a)kernel.org> wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> libceph: implement CEPHX_V2 calculation mode
>
> to the 4.14-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=sum…
>
> The filename of the patch is:
> libceph-implement-cephx_v2-calculation-mode.patch
> and it can be found in the queue-4.14 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable(a)vger.kernel.org> know about it.
>
>
>
> commit 14735e0afb6ed378becd0dedf37d1e5ddfa12084
> Author: Ilya Dryomov <idryomov(a)gmail.com>
> Date: Fri Jul 27 19:25:32 2018 +0200
>
> libceph: implement CEPHX_V2 calculation mode
>
> commit cc255c76c70f7a87d97939621eae04b600d9f4a1 upstream.
>
> Derive the signature from the entire buffer (both AES cipher blocks)
> instead of using just the first half of the first block, leaving out
> data_crc entirely.
>
> This addresses CVE-2018-1129.
>
> Link: http://tracker.ceph.com/issues/24837
> Signed-off-by: Ilya Dryomov <idryomov(a)gmail.com>
> Reviewed-by: Sage Weil <sage(a)redhat.com>
> Signed-off-by: Ben Hutchings <ben.hutchings(a)codethink.co.uk>
> Signed-off-by: Sasha Levin <sashal(a)kernel.org>
Hi Sasha,
The CVEs mentioned in this series are server side and CEPHX_V2 is
probably more of a new feature than a security fix. That said, I don't
object to including it in 4.14.z. If you do, please pick up the
remaining two patches for interoperability:
f1d10e046379 libceph: weaken sizeof check in ceph_x_verify_authorizer_reply()
130f52f2b203 libceph: check authorizer reply/challenge length before reading
Thanks,
Ilya
Intel Merrifield has a reduced size of FIFO used in iDMA 32-bit controller,
i.e. 512 bytes instead of 1024.
Fix this by partitioning it as 64 bytes per channel.
Note, in the future we might switch to 'fifo-size' property instead of
hard coded value.
Fixes: 199244d69458 ("dmaengine: dw: add support of iDMA 32-bit hardware")
Signed-off-by: Andy Shevchenko <andriy.shevchenko(a)linux.intel.com>
Cc: stable(a)vger.kernel.org
---
drivers/dma/dw/core.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/dma/dw/core.c b/drivers/dma/dw/core.c
index 2c5ca1961256..dc053e62f894 100644
--- a/drivers/dma/dw/core.c
+++ b/drivers/dma/dw/core.c
@@ -1061,12 +1061,12 @@ static void dwc_issue_pending(struct dma_chan *chan)
/*
* Program FIFO size of channels.
*
- * By default full FIFO (1024 bytes) is assigned to channel 0. Here we
+ * By default full FIFO (512 bytes) is assigned to channel 0. Here we
* slice FIFO on equal parts between channels.
*/
static void idma32_fifo_partition(struct dw_dma *dw)
{
- u64 value = IDMA32C_FP_PSIZE_CH0(128) | IDMA32C_FP_PSIZE_CH1(128) |
+ u64 value = IDMA32C_FP_PSIZE_CH0(64) | IDMA32C_FP_PSIZE_CH1(64) |
IDMA32C_FP_UPDATE;
u64 fifo_partition = 0;
@@ -1079,7 +1079,7 @@ static void idma32_fifo_partition(struct dw_dma *dw)
/* Fill FIFO_PARTITION high bits (Channels 2..3, 6..7) */
fifo_partition |= value << 32;
- /* Program FIFO Partition registers - 128 bytes for each channel */
+ /* Program FIFO Partition registers - 64 bytes per channel */
idma32_writeq(dw, FIFO_PARTITION1, fifo_partition);
idma32_writeq(dw, FIFO_PARTITION0, fifo_partition);
}
--
2.19.2
This is the start of the stable review cycle for the 4.9.143 release.
There are 50 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Thu Dec 6 10:36:59 UTC 2018.
Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.143-rc…
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.9.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
Linux 4.9.143-rc1
Chris Fries <cfries(a)google.com>
kbuild: Set KBUILD_CFLAGS before incl. arch Makefile
Ard Biesheuvel <ard.biesheuvel(a)linaro.org>
efi/libstub: Make file I/O chunking x86-specific
Arnd Bergmann <arnd(a)arndb.de>
workqueue: avoid clang warning
Stefan Agner <stefan(a)agner.ch>
ARM: trusted_foundations: do not use naked function
Stefan Agner <stefan(a)agner.ch>
bus: arm-cci: remove unnecessary unreachable()
Stefan Agner <stefan(a)agner.ch>
ARM: 8767/1: add support for building ARM kernel with clang
Stefan Agner <stefan(a)agner.ch>
ARM: 8766/1: drop no-thumb-interwork in EABI mode
Alistair Strachan <astrachan(a)google.com>
efi/libstub: arm: support building with clang
YueHaibing <yuehaibing(a)huawei.com>
misc: mic/scif: fix copy-paste error in scif_create_remote_lookup
Dexuan Cui <decui(a)microsoft.com>
Drivers: hv: vmbus: check the creation_status in vmbus_establish_gpadl()
Yu Zhao <yuzhao(a)google.com>
mm: use swp_offset as key in shmem_replace_page()
Martin Kelly <martin(a)martingkelly.com>
iio:st_magn: Fix enable device after trigger
Felipe Balbi <felipe.balbi(a)linux.intel.com>
Revert "usb: dwc3: gadget: skip Set/Clear Halt when invalid"
Michael Niewöhner <linux(a)mniewoehner.de>
usb: core: quirks: add RESET_RESUME quirk for Cherry G230 Stream series
Kai-Heng Feng <kai.heng.feng(a)canonical.com>
USB: usb-storage: Add new IDs to ums-realtek
Josef Bacik <josef(a)toxicpanda.com>
btrfs: release metadata before running delayed refs
Richard Genoud <richard.genoud(a)gmail.com>
dmaengine: at_hdmac: fix module unloading
Richard Genoud <richard.genoud(a)gmail.com>
dmaengine: at_hdmac: fix memory leak in at_dma_xlate()
Pan Bian <bianpan2016(a)163.com>
ext2: fix potential use after free
Takashi Iwai <tiwai(a)suse.de>
ALSA: sparc: Fix invalid snd_free_pages() at error path
Takashi Iwai <tiwai(a)suse.de>
ALSA: control: Fix race between adding and removing a user element
Takashi Iwai <tiwai(a)suse.de>
ALSA: ac97: Fix incorrect bit shift at AC97-SPSA control write
Takashi Iwai <tiwai(a)suse.de>
ALSA: wss: Fix invalid snd_free_pages() at error path
Maximilian Heyne <mheyne(a)amazon.de>
fs: fix lost error code in dio_complete
Jiri Olsa <jolsa(a)kernel.org>
perf/x86/intel: Add generic branch tracing check to intel_pmu_has_bts()
Jiri Olsa <jolsa(a)kernel.org>
perf/x86/intel: Move branch tracing setup to the Intel-specific source file
Filipe Manana <fdmanana(a)suse.com>
Btrfs: ensure path name is null terminated at btrfs_control_ioctl
Max Filippov <jcmvbkbc(a)gmail.com>
xtensa: fix coprocessor context offset definitions
Max Filippov <jcmvbkbc(a)gmail.com>
xtensa: enable coprocessors that are being flushed
Wanpeng Li <wanpengli(a)tencent.com>
KVM: X86: Fix scan ioapic use-before-initialization
Jim Mattson <jmattson(a)google.com>
kvm: svm: Ensure an IBPB on all affected CPUs when freeing a vmcb
Junaid Shahid <junaids(a)google.com>
kvm: mmu: Fix race in emulated page table writes
Bernd Eckstein <3erndeckstein(a)gmail.com>
usbnet: ipheth: fix potential recvmsg bug and recvmsg bug 2
Julian Wiedmann <jwi(a)linux.ibm.com>
s390/qeth: fix length check in SNMP processing
Pan Bian <bianpan2016(a)163.com>
rapidio/rionet: do not free skb before reading its length
Petr Machata <petrm(a)mellanox.com>
net: skb_scrub_packet(): Scrub offload_fwd_mark
Sasha Levin <sashal(a)kernel.org>
Revert "wlcore: Add missing PM call for wlcore_cmd_wait_for_event_or_timeout()"
Matthias Schwarzott <zzam(a)gentoo.org>
media: em28xx: Fix use-after-free when disconnecting
Hugh Dickins <hughd(a)google.com>
mm/khugepaged: collapse_shmem() do not crash on Compound
Hugh Dickins <hughd(a)google.com>
mm/khugepaged: collapse_shmem() without freezing new_page
Hugh Dickins <hughd(a)google.com>
mm/khugepaged: minor reorderings in collapse_shmem()
Hugh Dickins <hughd(a)google.com>
mm/khugepaged: collapse_shmem() remember to clear holes
Hugh Dickins <hughd(a)google.com>
mm/khugepaged: fix crashes due to misaccounted holes
Mike Rapoport <rppt(a)linux.vnet.ibm.com>
shmem: introduce shmem_inode_acct_block
Mike Rapoport <rppt(a)linux.vnet.ibm.com>
shmem: shmem_charge: verify max_block is not exceeded before inode update
Hugh Dickins <hughd(a)google.com>
mm/khugepaged: collapse_shmem() stop if punched or truncated
Hugh Dickins <hughd(a)google.com>
mm/huge_memory: fix lockdep complaint on 32-bit i_size_read()
Hugh Dickins <hughd(a)google.com>
mm/huge_memory: splitting set mapping+index before unfreeze
Konstantin Khlebnikov <khlebnikov(a)yandex-team.ru>
mm/huge_memory.c: reorder operations in __split_huge_page_tail()
Hugh Dickins <hughd(a)google.com>
mm/huge_memory: rename freeze_page() to unmap_page()
-------------
Diffstat:
Makefile | 69 ++++++-------
arch/arm/Makefile | 2 +-
arch/arm/boot/compressed/Makefile | 2 +-
arch/arm/firmware/trusted_foundations.c | 14 ++-
arch/x86/events/core.c | 20 ----
arch/x86/events/intel/core.c | 52 +++++++---
arch/x86/events/perf_event.h | 13 ++-
arch/x86/kvm/mmu.c | 27 ++----
arch/x86/kvm/svm.c | 20 +++-
arch/x86/kvm/x86.c | 3 +-
arch/xtensa/kernel/asm-offsets.c | 16 +--
arch/xtensa/kernel/process.c | 5 +-
drivers/bus/arm-cci.c | 2 -
drivers/dma/at_hdmac.c | 10 +-
drivers/firmware/efi/libstub/Makefile | 3 +-
drivers/firmware/efi/libstub/efi-stub-helper.c | 11 ++-
drivers/hv/channel.c | 8 ++
drivers/iio/magnetometer/st_magn_buffer.c | 12 +--
drivers/media/usb/em28xx/em28xx-dvb.c | 3 +-
drivers/misc/mic/scif/scif_rma.c | 2 +-
drivers/net/rionet.c | 2 +-
drivers/net/usb/ipheth.c | 10 +-
drivers/net/wireless/ti/wlcore/cmd.c | 6 --
drivers/s390/net/qeth_core_main.c | 27 +++---
drivers/usb/core/quirks.c | 3 +
drivers/usb/dwc3/gadget.c | 5 -
drivers/usb/storage/unusual_realtek.h | 10 ++
fs/btrfs/super.c | 1 +
fs/btrfs/transaction.c | 6 +-
fs/direct-io.c | 4 +-
fs/ext2/xattr.c | 2 +-
include/linux/workqueue.h | 4 +-
mm/huge_memory.c | 79 +++++++--------
mm/khugepaged.c | 129 ++++++++++++++-----------
mm/shmem.c | 97 ++++++++++---------
net/core/skbuff.c | 4 +
sound/core/control.c | 80 ++++++++-------
sound/isa/wss/wss_lib.c | 2 -
sound/pci/ac97/ac97_codec.c | 2 +-
sound/sparc/cs4231.c | 8 +-
40 files changed, 424 insertions(+), 351 deletions(-)
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Commit: 61c68f2a2af0 Linux 4.19.7
The results of these automated tests are provided below.
Overall result: PASSED
Patch merge: OK
Compile: OK
Kernel tests: OK
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 2 architectures:
aarch64:
make options: make INSTALL_MOD_STRIP=1 -j56 targz-pkg
configuration: https://artifacts.cki-project.org/builds/aarch64/61c68f2a2af0f3dc531053524f…
x86_64:
make options: make INSTALL_MOD_STRIP=1 -j56 targz-pkg
configuration: https://artifacts.cki-project.org/builds/x86_64/61c68f2a2af0f3dc531053524f9…
Hardware testing
----------------
We booted each kernel and ran the following tests:
arm64:
/distribution/kpkginstall (boot test)
LTP lite - release 20180515
xfstests: ext4
xfstests: xfs
/kernel/misc/amtu
x86_64:
/distribution/kpkginstall (boot test)
LTP lite - release 20180515
xfstests: ext4
xfstests: xfs
/kernel/misc/amtu
I'm announcing the release of the 4.14.86 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.y
and can be browsed at the normal kernel.org git web browser:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
thanks,
greg k-h
------------
Documentation/admin-guide/kernel-parameters.txt | 56
Documentation/userspace-api/spec_ctrl.rst | 9
Makefile | 2
arch/arm/boot/dts/rk3288-veyron.dtsi | 6
arch/arm64/boot/dts/rockchip/rk3399-puma-haikou.dts | 2
arch/x86/Kconfig | 12
arch/x86/Makefile | 5
arch/x86/events/core.c | 20
arch/x86/events/intel/core.c | 52
arch/x86/events/perf_event.h | 13
arch/x86/include/asm/cpufeatures.h | 2
arch/x86/include/asm/msr-index.h | 5
arch/x86/include/asm/nospec-branch.h | 44
arch/x86/include/asm/spec-ctrl.h | 20
arch/x86/include/asm/switch_to.h | 3
arch/x86/include/asm/thread_info.h | 20
arch/x86/include/asm/tlbflush.h | 8
arch/x86/kernel/cpu/amd.c | 4
arch/x86/kernel/cpu/bugs.c | 510 ++++++-
arch/x86/kernel/cpu/common.c | 9
arch/x86/kernel/cpu/mcheck/mce_amd.c | 19
arch/x86/kernel/fpu/signal.c | 4
arch/x86/kernel/process.c | 101 +
arch/x86/kernel/process.h | 39
arch/x86/kernel/process_32.c | 10
arch/x86/kernel/process_64.c | 10
arch/x86/kvm/cpuid.c | 10
arch/x86/kvm/mmu.c | 27
arch/x86/kvm/svm.c | 28
arch/x86/kvm/x86.c | 4
arch/x86/mm/tlb.c | 115 +
arch/xtensa/kernel/asm-offsets.c | 16
arch/xtensa/kernel/process.c | 5
arch/xtensa/kernel/ptrace.c | 42
drivers/android/binder.c | 21
drivers/android/binder_alloc.c | 14
drivers/android/binder_alloc.h | 3
drivers/dma/at_hdmac.c | 10
drivers/hv/channel.c | 8
drivers/iio/magnetometer/st_magn_buffer.c | 12
drivers/media/usb/em28xx/em28xx-dvb.c | 3
drivers/misc/mic/scif/scif_rma.c | 2
drivers/mtd/ubi/vtbl.c | 20
drivers/net/ethernet/cavium/thunder/nicvf_main.c | 9
drivers/net/ethernet/cavium/thunder/nicvf_queues.c | 4
drivers/net/rionet.c | 2
drivers/net/usb/ipheth.c | 10
drivers/net/virtio_net.c | 13
drivers/net/wireless/ath/wil6210/wmi.c | 8
drivers/net/wireless/ti/wlcore/cmd.c | 6
drivers/pci/dwc/pci-layerscape.c | 2
drivers/s390/net/qeth_core_main.c | 27
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 2
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c | 7
drivers/usb/core/quirks.c | 3
drivers/usb/dwc3/gadget.c | 5
drivers/usb/storage/unusual_realtek.h | 10
fs/btrfs/Makefile | 2
fs/btrfs/disk-io.c | 153 --
fs/btrfs/extent-tree.c | 86 +
fs/btrfs/relocation.c | 1
fs/btrfs/super.c | 1
fs/btrfs/transaction.c | 6
fs/btrfs/tree-checker.c | 649 ++++++++++
fs/btrfs/tree-checker.h | 38
fs/btrfs/volumes.c | 30
fs/btrfs/volumes.h | 2
fs/ceph/mds_client.c | 11
fs/direct-io.c | 4
fs/ext2/xattr.c | 2
fs/f2fs/checkpoint.c | 43
fs/f2fs/data.c | 52
fs/f2fs/f2fs.h | 41
fs/f2fs/file.c | 21
fs/f2fs/inode.c | 78 +
fs/f2fs/node.c | 11
fs/f2fs/recovery.c | 6
fs/f2fs/segment.c | 13
fs/f2fs/segment.h | 24
fs/f2fs/super.c | 96 +
fs/xfs/libxfs/xfs_attr.c | 9
include/linux/bpf_verifier.h | 1
include/linux/ceph/auth.h | 8
include/linux/ceph/ceph_features.h | 7
include/linux/ceph/messenger.h | 6
include/linux/ceph/msgr.h | 2
include/linux/jump_label.h | 7
include/linux/ptrace.h | 4
include/linux/sched.h | 9
include/linux/sched/smt.h | 20
include/linux/skbuff.h | 18
include/net/tls.h | 4
include/uapi/linux/btrfs_tree.h | 1
include/uapi/linux/prctl.h | 1
kernel/bpf/verifier.c | 62
kernel/cpu.c | 14
kernel/jump_label.c | 12
kernel/sched/core.c | 19
kernel/sched/fair.c | 4
kernel/sched/sched.h | 4
lib/test_kmod.c | 1
mm/huge_memory.c | 79 -
mm/khugepaged.c | 129 +
mm/shmem.c | 12
net/ceph/auth.c | 16
net/ceph/auth_x.c | 223 ++-
net/ceph/auth_x_protocol.h | 7
net/ceph/messenger.c | 93 -
net/ceph/osd_client.c | 11
net/core/skbuff.c | 4
net/packet/af_packet.c | 4
net/tls/tls_main.c | 124 +
net/tls/tls_sw.c | 13
scripts/Makefile.build | 2
sound/core/control.c | 80 -
sound/isa/wss/wss_lib.c | 2
sound/pci/ac97/ac97_codec.c | 2
sound/pci/hda/patch_realtek.c | 9
sound/sparc/cs4231.c | 8
119 files changed, 2926 insertions(+), 908 deletions(-)
Alexei Starovoitov (1):
bpf: Prevent memory disambiguation attack
Anisse Astier (1):
ALSA: hda/realtek - fix headset mic detection for MSI MS-B171
Arnd Bergmann (1):
btrfs: tree-checker: use %zu format string for size_t
Ben Hutchings (1):
f2fs: Add sanity_check_inode() function
Ben Wolsieffer (1):
staging: vchiq_arm: fix compat VCHIQ_IOC_AWAIT_COMPLETION
Bernd Eckstein (1):
usbnet: ipheth: fix potential recvmsg bug and recvmsg bug 2
Boris Pismenny (1):
tls: Use correct sk->sk_prot for IPV6
Borislav Petkov (1):
x86/MCE/AMD: Fix the thresholding machinery initialization order
Chao Yu (9):
f2fs: clean up with is_valid_blkaddr()
f2fs: introduce and spread verify_blkaddr
f2fs: fix to do sanity check with secs_per_zone
f2fs: fix to do sanity check with extra_attr feature
f2fs: fix to do sanity check with user_block_count
f2fs: fix to do sanity check with node footer and iblocks
f2fs: fix to do sanity check with block address in main area
f2fs: fix to do sanity check with i_extra_isize
f2fs: fix to do sanity check with cp_pack_start_sum
Christoph Muellner (1):
arm64: dts: rockchip: Fix PCIe reset polarity for rk3399-puma-haikou.
Darrick J. Wong (1):
xfs: don't fail when converting shortform attr to long form during ATTR_REPLACE
David Sterba (1):
btrfs: tree-check: reduce stack consumption in check_dir_item
Dexuan Cui (1):
Drivers: hv: vmbus: check the creation_status in vmbus_establish_gpadl()
Felipe Balbi (1):
Revert "usb: dwc3: gadget: skip Set/Clear Halt when invalid"
Filipe Manana (1):
Btrfs: ensure path name is null terminated at btrfs_control_ioctl
Greg Kroah-Hartman (1):
Linux 4.14.86
Gu Jinxiang (1):
btrfs: validate type when reading a chunk
Heiko Stuebner (1):
ARM: dts: rockchip: Remove @0 from the veyron memory node
Hou Zhiqiang (1):
PCI: layerscape: Fix wrong invocation of outbound window disable accessor
Hugh Dickins (9):
mm/huge_memory: rename freeze_page() to unmap_page()
mm/huge_memory: splitting set mapping+index before unfreeze
mm/huge_memory: fix lockdep complaint on 32-bit i_size_read()
mm/khugepaged: collapse_shmem() stop if punched or truncated
mm/khugepaged: fix crashes due to misaccounted holes
mm/khugepaged: collapse_shmem() remember to clear holes
mm/khugepaged: minor reorderings in collapse_shmem()
mm/khugepaged: collapse_shmem() without freezing new_page
mm/khugepaged: collapse_shmem() do not crash on Compound
Ilya Dryomov (8):
libceph: store ceph_auth_handshake pointer in ceph_connection
libceph: factor out __prepare_write_connect()
libceph: factor out __ceph_x_decrypt()
libceph: factor out encrypt_authorizer()
libceph: add authorizer challenge
libceph: implement CEPHX_V2 calculation mode
libceph: weaken sizeof check in ceph_x_verify_authorizer_reply()
libceph: check authorizer reply/challenge length before reading
Ilya Lesokhin (4):
tls: Add function to update the TLS socket configuration
tls: Fix TLS ulp context leak, when TLS_TX setsockopt is not used.
tls: Avoid copying crypto_info again after cipher_type check.
tls: don't override sk_write_space if tls_set_sw_offload fails.
Jaegeuk Kim (3):
f2fs: sanity check on sit entry
f2fs: enhance sanity_check_raw_super() to avoid potential overflow
f2fs: fix missing up_read
Jason Wang (2):
virtio-net: disable guest csum during XDP set
virtio-net: fail XDP set if guest csum is negotiated
Jim Mattson (1):
kvm: svm: Ensure an IBPB on all affected CPUs when freeing a vmcb
Jiri Kosina (3):
x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation
x86/speculation: Apply IBPB more strictly to avoid cross-process data leak
x86/speculation: Propagate information about RSB filling mitigation to sysfs
Jiri Olsa (2):
perf/x86/intel: Move branch tracing setup to the Intel-specific source file
perf/x86/intel: Add generic branch tracing check to intel_pmu_has_bts()
Josef Bacik (1):
btrfs: release metadata before running delayed refs
Julian Wiedmann (1):
s390/qeth: fix length check in SNMP processing
Junaid Shahid (1):
kvm: mmu: Fix race in emulated page table writes
Kai-Heng Feng (1):
USB: usb-storage: Add new IDs to ums-realtek
Kailang Yang (1):
ALSA: hda/realtek - Support ALC300
Konrad Rzeszutek Wilk (3):
x86/bugs: Add AMD's variant of SSB_NO
x86/bugs: Add AMD's SPEC_CTRL MSR usage
x86/bugs: Switch the selection of mitigation from CPU vendor to CPU features
Konstantin Khlebnikov (1):
mm/huge_memory.c: reorder operations in __split_huge_page_tail()
Larry Finger (1):
staging: rtl8723bs: Add missing return for cfg80211_rtw_get_station
Lior David (1):
wil6210: missing length check in wmi_set_ie
Liran Alon (1):
KVM: x86: Fix kernel info-leak in KVM_HC_CLOCK_PAIRING hypercall
Lorenzo Bianconi (2):
net: thunderx: set xdp_prog to NULL if bpf_prog_add fails
net: thunderx: set tso_hdrs pointer to NULL in nicvf_free_snd_queue
Luis Chamberlain (1):
lib/test_kmod.c: fix rmmod double free
Martin Kelly (1):
iio:st_magn: Fix enable device after trigger
Matthias Schwarzott (1):
media: em28xx: Fix use-after-free when disconnecting
Max Filippov (3):
xtensa: enable coprocessors that are being flushed
xtensa: fix coprocessor context offset definitions
xtensa: fix coprocessor part of ptrace_{get,set}xregs
Maximilian Heyne (1):
fs: fix lost error code in dio_complete
Michael Niewöhner (1):
usb: core: quirks: add RESET_RESUME quirk for Cherry G230 Stream series
Pan Bian (3):
rapidio/rionet: do not free skb before reading its length
btrfs: relocation: set trans to be NULL after ending transaction
ext2: fix potential use after free
Peter Zijlstra (1):
sched/core: Fix cpu.max vs. cpuhotplug deadlock
Peter Zijlstra (Intel) (1):
sched/smt: Make sched_smt_present track topology
Petr Machata (1):
net: skb_scrub_packet(): Scrub offload_fwd_mark
Qu Wenruo (13):
btrfs: Verify that every chunk has corresponding block group at mount time
btrfs: Refactor check_leaf function for later expansion
btrfs: Check if item pointer overlaps with the item itself
btrfs: Add sanity check for EXTENT_DATA when reading out leaf
btrfs: Add checker for EXTENT_CSUM
btrfs: Move leaf and node validation checker to tree-checker.c
btrfs: tree-checker: Enhance btrfs_check_node output
btrfs: tree-checker: Fix false panic for sanity test
btrfs: tree-checker: Add checker for dir item
btrfs: tree-checker: Verify block_group_item
btrfs: tree-checker: Detect invalid and empty essential trees
btrfs: Check that each block group has corresponding chunk at mount time
btrfs: tree-checker: Check level for leaves and nodes
Richard Genoud (2):
dmaengine: at_hdmac: fix memory leak in at_dma_xlate()
dmaengine: at_hdmac: fix module unloading
Richard Weinberger (1):
ubi: Initialize Fastmap checkmapping correctly
Sasha Levin (1):
Revert "wlcore: Add missing PM call for wlcore_cmd_wait_for_event_or_timeout()"
Sebastian Andrzej Siewior (1):
x86/fpu: Disable bottom halves while loading FPU registers
Shaokun Zhang (1):
btrfs: tree-checker: Fix misleading group system information
Takashi Iwai (4):
ALSA: wss: Fix invalid snd_free_pages() at error path
ALSA: ac97: Fix incorrect bit shift at AC97-SPSA control write
ALSA: control: Fix race between adding and removing a user element
ALSA: sparc: Fix invalid snd_free_pages() at error path
Thomas Gleixner (21):
x86/speculation: Rename SSBD update functions
x86/Kconfig: Select SCHED_SMT if SMP enabled
sched/smt: Expose sched_smt_present static key
x86/speculation: Rework SMT state change
x86/l1tf: Show actual SMT state
x86/speculation: Reorder the spec_v2 code
x86/speculation: Mark string arrays const correctly
x86/speculataion: Mark command line parser data __initdata
x86/speculation: Unify conditional spectre v2 print functions
x86/speculation: Add command line control for indirect branch speculation
x86/process: Consolidate and simplify switch_to_xtra() code
x86/speculation: Avoid __switch_to_xtra() calls
x86/speculation: Prepare for conditional IBPB in switch_mm()
ptrace: Remove unused ptrace_may_access_sched() and MODE_IBRS
x86/speculation: Split out TIF update
x86/speculation: Prevent stale SPEC_CTRL msr content
x86/speculation: Prepare arch_smt_update() for PRCTL mode
x86/speculation: Add prctl() control for indirect branch speculation
x86/speculation: Enable prctl mode for spectre_v2_user
x86/speculation: Add seccomp Spectre v2 user space protection mode
x86/speculation: Provide IBPB always command line options
Tim Chen (7):
x86/speculation: Update the TIF_SSBD comment
x86/speculation: Clean up spectre_v2_parse_cmdline()
x86/speculation: Remove unnecessary ret variable in cpu_show_common()
x86/speculation: Move STIPB/IBPB string conditionals out of cpu_show_common()
x86/speculation: Disable STIBP when enhanced IBRS is in use
x86/speculation: Reorganize speculation control MSRs update
x86/speculation: Prepare for per task indirect branch speculation control
Todd Kjos (1):
binder: fix race that allows malicious free of live buffer
Tom Lendacky (2):
x86/bugs: Update when to check for the LS_CFG SSBD mitigation
x86/bugs: Fix the AMD SSBD usage of the SPEC_CTRL MSR
Vakul Garg (1):
net/tls: Fixed return value when tls_complete_pending_work() fails
Wanpeng Li (1):
KVM: X86: Fix scan ioapic use-before-initialization
Willem de Bruijn (1):
packet: copy user buffers before orphan or clone
Yu Zhao (1):
mm: use swp_offset as key in shmem_replace_page()
YueHaibing (1):
misc: mic/scif: fix copy-paste error in scif_create_remote_lookup
Yunlei He (1):
f2fs: check blkaddr more accuratly before issue a bio
Zhenzhong Duan (3):
x86/speculation: Add RETPOLINE_AMD support to the inline asm CALL_NOSPEC variant
x86/retpoline: Make CONFIG_RETPOLINE depend on compiler support
x86/retpoline: Remove minimal retpoline support
This is an automatic generated email to let you know that the following patch were queued:
Subject: media: vicodec: fix memchr() kernel oops
Author: Hans Verkuil <hverkuil(a)xs4all.nl>
Date: Sat Nov 17 06:25:08 2018 -0500
The size passed to memchr is too large as it assumes the search
starts at the start of the buffer, but it can start at an offset.
Cc: <stable(a)vger.kernel.org> # for v4.19 and up
Signed-off-by: Hans Verkuil <hverkuil(a)xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung(a)kernel.org>
drivers/media/platform/vicodec/vicodec-core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
---
diff --git a/drivers/media/platform/vicodec/vicodec-core.c b/drivers/media/platform/vicodec/vicodec-core.c
index b292cff26c86..013cdebecbc4 100644
--- a/drivers/media/platform/vicodec/vicodec-core.c
+++ b/drivers/media/platform/vicodec/vicodec-core.c
@@ -304,7 +304,8 @@ restart:
for (; p < p_out + sz; p++) {
u32 copy;
- p = memchr(p, magic[ctx->comp_magic_cnt], sz);
+ p = memchr(p, magic[ctx->comp_magic_cnt],
+ p_out + sz - p);
if (!p) {
ctx->comp_magic_cnt = 0;
break;
Changes since v2 [1]:
* Fix links in the changelogs to reference lkml.kernel.org instead of
lore.kernel.org (Peter)
* Collect Acked-by's from Kirill and Peter.
* Add more Cc's for patches 1 and 2.
* Strengthen the lead-in comment for the set_p*_safe() helpers (Dave)
[1]: https://lkml.org/lkml/2018/12/1/358
---
>From patch 5:
Commit f77084d96355 "x86/mm/pat: Disable preemption around
__flush_tlb_all()" addressed a case where __flush_tlb_all() is called
without preemption being disabled. It also left a warning to catch other
cases where preemption is not disabled. That warning triggers for the
memory hotplug path which is also used for persistent memory enabling:
WARNING: CPU: 35 PID: 911 at ./arch/x86/include/asm/tlbflush.h:460
RIP: 0010:__flush_tlb_all+0x1b/0x3a
[..]
Call Trace:
phys_pud_init+0x29c/0x2bb
kernel_physical_mapping_init+0xfc/0x219
init_memory_mapping+0x1a5/0x3b0
arch_add_memory+0x2c/0x50
devm_memremap_pages+0x3aa/0x610
pmem_attach_disk+0x585/0x700 [nd_pmem]
Andy wondered why a path that can sleep was using __flush_tlb_all() [1]
and Dave confirmed the expectation for TLB flush is for modifying /
invalidating existing pte entries, but not initial population [2]. Drop
the usage of __flush_tlb_all() in phys_{p4d,pud,pmd}_init() on the
expectation that this path is only ever populating empty entries for the
linear map. Note, at linear map teardown time there is a call to the
all-cpu flush_tlb_all() to invalidate the removed mappings.
Additionally, Dave wanted some runtime assurances that
kernel_physical_mapping_init() is only populating and not changing
existing page table entries. Patches 1 - 4 are implementing a new
set_pte() family of helpers for that purpose.
Patch 5 is tagged for -stable because the false positive warning is now
showing up on 4.19-stable kernels. Patches 1 - 4 are not tagged for
-stable, but if the sanity checking is needed please mark them as such.
The hang that was observed while developing the sanity checking
implementation was resolved by Peter's suggestion to not trigger when
the same pte value is being rewritten.
---
Dan Williams (5):
generic/pgtable: Make {pmd,pud}_same() unconditionally available
generic/pgtable: Introduce {p4d,pgd}_same()
generic/pgtable: Introduce set_pte_safe()
x86/mm: Validate kernel_physical_mapping_init() pte population
x86/mm: Drop usage of __flush_tlb_all() in kernel_physical_mapping_init()
arch/x86/include/asm/pgalloc.h | 27 ++++++++++++++
arch/x86/mm/init_64.c | 30 ++++++----------
include/asm-generic/5level-fixup.h | 1 +
include/asm-generic/pgtable-nop4d-hack.h | 1 +
include/asm-generic/pgtable-nop4d.h | 1 +
include/asm-generic/pgtable-nopud.h | 1 +
include/asm-generic/pgtable.h | 56 +++++++++++++++++++++++++-----
7 files changed, 90 insertions(+), 27 deletions(-)
From: Hans Verkuil <hverkuil(a)xs4all.nl>
[ Upstream commit 7cf7b2e977abf3f992036939e35a8eab60013aff ]
Lower the minimum height to 360 to be consistent with the webcam input of vivid.
The 480 was rather arbitrary but it made it harder to use vivid as a source for
encoding since the default resolution when you load vivid is 640x360.
Signed-off-by: Hans Verkuil <hans.verkuil(a)cisco.com>
Reviewed-by: Kieran Bingham <kieran.bingham+renesas(a)ideasonboard.com>
Signed-off-by: Hans Verkuil <hverkuil(a)xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung(a)kernel.org>
Signed-off-by: Sasha Levin <sashal(a)kernel.org>
---
drivers/media/platform/vicodec/vicodec-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/vicodec/vicodec-core.c b/drivers/media/platform/vicodec/vicodec-core.c
index 408cd55d3580..daa5caa6adc6 100644
--- a/drivers/media/platform/vicodec/vicodec-core.c
+++ b/drivers/media/platform/vicodec/vicodec-core.c
@@ -42,7 +42,7 @@ MODULE_PARM_DESC(debug, " activates debug info");
#define MAX_WIDTH 4096U
#define MIN_WIDTH 640U
#define MAX_HEIGHT 2160U
-#define MIN_HEIGHT 480U
+#define MIN_HEIGHT 360U
#define dprintk(dev, fmt, arg...) \
v4l2_dbg(1, debug, &dev->v4l2_dev, "%s: " fmt, __func__, ## arg)
--
2.17.1
Hey,
On 2018-12-04 22:53, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
>
> The bot has tested the following trees: v4.19.6, v4.14.85, v4.9.142, v4.4.166, v3.18.128,
>
> v4.19.6: Build OK!
> v4.14.85: Failed to apply! Possible dependencies:
> cd414f3d9316 ("drm/msm: Move memptrs to msm_gpu")
> eec874ce5ff1 ("drm/msm/adreno: load gpu at probe/bind time")
> f7de15450e90 ("drm/msm: Add per-instance submit queues")
> f97decac5f4c ("drm/msm: Support multiple ringbuffers")
v4.14.85 can be rebased fairly cleanly:
https://gitlab.collabora.com/robertfoss/linux/commits/msm_in_fence_put_v3_v…
However v4.9.142 and earlier does not rebase very cleanly at all.
I don't know what the rule of thumb for backporting fixes is, but the feature
that is fixed here does not seem to exist in v4.9.142 and earlier.
Rob.
>
> v4.9.142: Failed to apply! Possible dependencies:
> 1cec20f0ea0e ("dma-buf: Restart reservation_object_wait_timeout_rcu() after writes")
> 78010cd9736e ("dma-buf/fence: add an lockdep_assert_held()")
> f54d1867005c ("dma-buf: Rename struct fence to dma_fence")
> fedf54132d24 ("dma-buf: Restart reservation_object_get_fences_rcu() after writes")
>
> v4.4.166: Failed to apply! Possible dependencies:
> 0f477c6dea70 ("staging/android/sync: add sync_fence_create_dma")
> 31954660a7a6 ("dma-buf/sync_file: improve Kconfig description for Sync Files")
> 375fb53ec1be ("staging: android: replace explicit NULL comparison")
> 395dec6f6bc5 ("Documentation: add doc for sync_file_get_fence()")
> 62304fb1fc08 ("dma-buf/sync_file: de-stage sync_file")
> 696f74cf5439 ("staging/android: move sync_file functions comments to sync.c")
> 699f68556943 ("android: unconditionally remove callbacks in sync_fence_free()")
> 73465f1c0825 ("staging/android/sync: Support sync points created from dma-fences")
> 8a0044846115 ("staging/android: create a 'sync' dir for debugfs information")
> 9b32381ca50f ("staging/android: fix sync framework documentation")
> a44eb74cd413 ("staging/android: move SW_SYNC_USER to a debugfs file")
> b55b54b5db33 ("staging/android: remove struct sync_pt")
> c01a958eca6e ("drm/msm: reject submit ioctl if no gpu")
> c784c82a3fd6 ("Documentation: add Sync File doc")
> cd572182bd3d ("Staging: android: Fix brace coding style warning in sync_debug.c")
> d4cab38e153d ("staging/android: prepare sync_file for de-staging")
> d7c3110c28de ("staging/android: remove name arg from sync_file_create()")
> d7fdb0ae9d11 ("staging/android: rename sync_fence to sync_file")
> f54d1867005c ("dma-buf: Rename struct fence to dma_fence")
> fac8434dab96 ("Documentation: Fix some grammar mistakes in sync_file.txt")
>
> v3.18.128: Failed to apply! Possible dependencies:
> 0541cdf585a8 ("Staging: android: fix line length coding style issue in sync_debug.c")
> 0f477c6dea70 ("staging/android/sync: add sync_fence_create_dma")
> 31954660a7a6 ("dma-buf/sync_file: improve Kconfig description for Sync Files")
> 353fdf17060b ("staging: android: Replace timeval with timespec64")
> 375fb53ec1be ("staging: android: replace explicit NULL comparison")
> 395dec6f6bc5 ("Documentation: add doc for sync_file_get_fence()")
> 62304fb1fc08 ("dma-buf/sync_file: de-stage sync_file")
> 699f68556943 ("android: unconditionally remove callbacks in sync_fence_free()")
> 73465f1c0825 ("staging/android/sync: Support sync points created from dma-fences")
> 8a0044846115 ("staging/android: create a 'sync' dir for debugfs information")
> 9b32381ca50f ("staging/android: fix sync framework documentation")
> a44eb74cd413 ("staging/android: move SW_SYNC_USER to a debugfs file")
> b8797affa142 ("staging: android: fix coding style checks in sw_sync.c")
> c01a958eca6e ("drm/msm: reject submit ioctl if no gpu")
> c784c82a3fd6 ("Documentation: add Sync File doc")
> cd572182bd3d ("Staging: android: Fix brace coding style warning in sync_debug.c")
> d30649a8b618 ("staging: android: Remove unnecessary externs")
> d4cab38e153d ("staging/android: prepare sync_file for de-staging")
> d7c3110c28de ("staging/android: remove name arg from sync_file_create()")
> d7fdb0ae9d11 ("staging/android: rename sync_fence to sync_file")
> db1ad33bcfc4 ("drivers/staging: make android sw_sync.c explicitly non-modular")
> f54d1867005c ("dma-buf: Rename struct fence to dma_fence")
> fac8434dab96 ("Documentation: Fix some grammar mistakes in sync_file.txt")
>
>
> How should we proceed with this patch?
>
> --
> Thanks,
> Sasha
>
Don't allow USB3 U1 or U2 if the latency to wake up from the U-state
reaches the service interval for a periodic endpoint.
This is according to xhci 1.1 specification section 4.23.5.2 extra note:
"Software shall ensure that a device is prevented from entering a U-state
where its worst case exit latency approaches the ESIT."
Allowing too long exit latencies for periodic endpoint confuses xHC
internal scheduling, and new devices may fail to enumerate with a
"Not enough bandwidth for new device state" error from the host.
Cc: <stable(a)vger.kernel.org>
Signed-off-by: Mathias Nyman <mathias.nyman(a)linux.intel.com>
---
drivers/usb/host/xhci.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index c20b85e..dae3be1 100644
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -4514,6 +4514,14 @@ static u16 xhci_calculate_u1_timeout(struct xhci_hcd *xhci,
{
unsigned long long timeout_ns;
+ /* Prevent U1 if service interval is shorter than U1 exit latency */
+ if (usb_endpoint_xfer_int(desc) || usb_endpoint_xfer_isoc(desc)) {
+ if (xhci_service_interval_to_ns(desc) <= udev->u1_params.mel) {
+ dev_dbg(&udev->dev, "Disable U1, ESIT shorter than exit latency\n");
+ return USB3_LPM_DISABLED;
+ }
+ }
+
if (xhci->quirks & XHCI_INTEL_HOST)
timeout_ns = xhci_calculate_intel_u1_timeout(udev, desc);
else
@@ -4570,6 +4578,14 @@ static u16 xhci_calculate_u2_timeout(struct xhci_hcd *xhci,
{
unsigned long long timeout_ns;
+ /* Prevent U2 if service interval is shorter than U2 exit latency */
+ if (usb_endpoint_xfer_int(desc) || usb_endpoint_xfer_isoc(desc)) {
+ if (xhci_service_interval_to_ns(desc) <= udev->u2_params.mel) {
+ dev_dbg(&udev->dev, "Disable U2, ESIT shorter than exit latency\n");
+ return USB3_LPM_DISABLED;
+ }
+ }
+
if (xhci->quirks & XHCI_INTEL_HOST)
timeout_ns = xhci_calculate_intel_u2_timeout(udev, desc);
else
--
2.7.4
From: Sandeep Singh <sandeep.singh(a)amd.com>
Occasionally AMD SNPS 3.0 xHC does not respond to
CSS when set, also it does not flag anything on SRE and HCE
to point the internal xHC errors on USBSTS register. This stalls
the entire system wide suspend and there is no point in stalling
just because of xHC CSS is not responding.
To work around this problem, if the xHC does not flag
anything on SRE and HCE, we can skip the CSS
timeout and allow the system to continue the suspend. Once the
system resume happens we can internally reset the controller
using XHCI_RESET_ON_RESUME quirk
Signed-off-by: Shyam Sundar S K <Shyam-sundar.S-k(a)amd.com>
Signed-off-by: Sandeep Singh <Sandeep.Singh(a)amd.com>
cc: Nehal Shah <Nehal-bakulchandra.Shah(a)amd.com>
Cc: <stable(a)vger.kernel.org>
Tested-by: Kai-Heng Feng <kai.heng.feng(a)canonical.com>
Signed-off-by: Mathias Nyman <mathias.nyman(a)linux.intel.com>
---
drivers/usb/host/xhci-pci.c | 4 ++++
drivers/usb/host/xhci.c | 26 ++++++++++++++++++++++----
drivers/usb/host/xhci.h | 3 +++
3 files changed, 29 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index a951526..a9ec705 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -139,6 +139,10 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)
pdev->device == 0x43bb))
xhci->quirks |= XHCI_SUSPEND_DELAY;
+ if (pdev->vendor == PCI_VENDOR_ID_AMD &&
+ (pdev->device == 0x15e0 || pdev->device == 0x15e1))
+ xhci->quirks |= XHCI_SNPS_BROKEN_SUSPEND;
+
if (pdev->vendor == PCI_VENDOR_ID_AMD)
xhci->quirks |= XHCI_TRUST_TX_LENGTH;
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index c928dbb..c20b85e 100644
--- a/drivers/usb/host/xhci.c
+++ b/drivers/usb/host/xhci.c
@@ -968,6 +968,7 @@ int xhci_suspend(struct xhci_hcd *xhci, bool do_wakeup)
unsigned int delay = XHCI_MAX_HALT_USEC;
struct usb_hcd *hcd = xhci_to_hcd(xhci);
u32 command;
+ u32 res;
if (!hcd->state)
return 0;
@@ -1021,11 +1022,28 @@ int xhci_suspend(struct xhci_hcd *xhci, bool do_wakeup)
command = readl(&xhci->op_regs->command);
command |= CMD_CSS;
writel(command, &xhci->op_regs->command);
+ xhci->broken_suspend = 0;
if (xhci_handshake(&xhci->op_regs->status,
STS_SAVE, 0, 10 * 1000)) {
- xhci_warn(xhci, "WARN: xHC save state timeout\n");
- spin_unlock_irq(&xhci->lock);
- return -ETIMEDOUT;
+ /*
+ * AMD SNPS xHC 3.0 occasionally does not clear the
+ * SSS bit of USBSTS and when driver tries to poll
+ * to see if the xHC clears BIT(8) which never happens
+ * and driver assumes that controller is not responding
+ * and times out. To workaround this, its good to check
+ * if SRE and HCE bits are not set (as per xhci
+ * Section 5.4.2) and bypass the timeout.
+ */
+ res = readl(&xhci->op_regs->status);
+ if ((xhci->quirks & XHCI_SNPS_BROKEN_SUSPEND) &&
+ (((res & STS_SRE) == 0) &&
+ ((res & STS_HCE) == 0))) {
+ xhci->broken_suspend = 1;
+ } else {
+ xhci_warn(xhci, "WARN: xHC save state timeout\n");
+ spin_unlock_irq(&xhci->lock);
+ return -ETIMEDOUT;
+ }
}
spin_unlock_irq(&xhci->lock);
@@ -1078,7 +1096,7 @@ int xhci_resume(struct xhci_hcd *xhci, bool hibernated)
set_bit(HCD_FLAG_HW_ACCESSIBLE, &xhci->shared_hcd->flags);
spin_lock_irq(&xhci->lock);
- if (xhci->quirks & XHCI_RESET_ON_RESUME)
+ if ((xhci->quirks & XHCI_RESET_ON_RESUME) || xhci->broken_suspend)
hibernated = true;
if (!hibernated) {
diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
index 260b259..c3515ba 100644
--- a/drivers/usb/host/xhci.h
+++ b/drivers/usb/host/xhci.h
@@ -1850,6 +1850,7 @@ struct xhci_hcd {
#define XHCI_ZERO_64B_REGS BIT_ULL(32)
#define XHCI_DEFAULT_PM_RUNTIME_ALLOW BIT_ULL(33)
#define XHCI_RESET_PLL_ON_DISCONNECT BIT_ULL(34)
+#define XHCI_SNPS_BROKEN_SUSPEND BIT_ULL(35)
unsigned int num_active_eps;
unsigned int limit_active_eps;
@@ -1879,6 +1880,8 @@ struct xhci_hcd {
void *dbc;
/* platform-specific data -- must come last */
unsigned long priv[0] __aligned(sizeof(s64));
+ /* Broken Suspend flag for SNPS Suspend resume issue */
+ u8 broken_suspend;
};
/* Platform specific overrides to generic XHCI hc_driver ops */
--
2.7.4
The USB-serial console implementation has never reported the actual
terminal settings used. Despite storing the corresponding cflags in its
struct console, this was never honoured on later tty open() where the
tty termios would be left initialised to the driver defaults.
Unlike the serial console implementation, the USB-serial code calls
subdriver open() already at console setup. While calling set_termios()
before open() looks like it could work for some USB-serial drivers,
others definitely do not expect this, so modelling this after serial
core is going to be intrusive, if at all possible.
Instead, use a (renamed) tty helper to save the termios data used at
console setup, so that the tty termios reflects the actual terminal
settings after a subsequent tty open().
Note that the calls to tty_init_termios() (tty_driver_install()) and
tty_save_termios() are serialised using the disconnect mutex.
This specifically fixes a regression that was triggered by a recent
change adding software flow control to the pl2303 driver: a getty trying
to disable flow control while leaving the baud rate unchanged would now
also set the baud rate to the driver default (prior to the flow-control
change this had been a noop).
Fixes: 7041d9c3f01b ("USB: serial: pl2303: add support for tx xon/xoff flow control")
Cc: stable <stable(a)vger.kernel.org> # 4.18
Reported-by: Jarkko Nikula <jarkko.nikula(a)linux.intel.com>
Cc: Florian Zumbiehl <florz(a)florz.de>
Signed-off-by: Johan Hovold <johan(a)kernel.org>
---
drivers/tty/tty_io.c | 11 +++++++++--
drivers/usb/serial/console.c | 2 +-
include/linux/tty.h | 1 +
3 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index ee80dfbd5442..687250ec8032 100644
--- a/drivers/tty/tty_io.c
+++ b/drivers/tty/tty_io.c
@@ -1373,7 +1373,13 @@ struct tty_struct *tty_init_dev(struct tty_driver *driver, int idx)
return ERR_PTR(retval);
}
-static void tty_free_termios(struct tty_struct *tty)
+/**
+ * tty_save_termios() - save tty termios data in driver table
+ * @tty: tty whose termios data to save
+ *
+ * Locking: Caller guarantees serialisation with tty_init_termios().
+ */
+void tty_save_termios(struct tty_struct *tty)
{
struct ktermios *tp;
int idx = tty->index;
@@ -1392,6 +1398,7 @@ static void tty_free_termios(struct tty_struct *tty)
}
*tp = tty->termios;
}
+EXPORT_SYMBOL_GPL(tty_save_termios);
/**
* tty_flush_works - flush all works of a tty/pty pair
@@ -1491,7 +1498,7 @@ static void release_tty(struct tty_struct *tty, int idx)
WARN_ON(!mutex_is_locked(&tty_mutex));
if (tty->ops->shutdown)
tty->ops->shutdown(tty);
- tty_free_termios(tty);
+ tty_save_termios(tty);
tty_driver_remove_tty(tty->driver, tty);
tty->port->itty = NULL;
if (tty->link)
diff --git a/drivers/usb/serial/console.c b/drivers/usb/serial/console.c
index 17940589c647..7d289302ff6c 100644
--- a/drivers/usb/serial/console.c
+++ b/drivers/usb/serial/console.c
@@ -101,7 +101,6 @@ static int usb_console_setup(struct console *co, char *options)
cflag |= PARENB;
break;
}
- co->cflag = cflag;
/*
* no need to check the index here: if the index is wrong, console
@@ -164,6 +163,7 @@ static int usb_console_setup(struct console *co, char *options)
serial->type->set_termios(tty, port, &dummy);
tty_port_tty_set(&port->port, NULL);
+ tty_save_termios(tty);
tty_kref_put(tty);
}
tty_port_set_initialized(&port->port, 1);
diff --git a/include/linux/tty.h b/include/linux/tty.h
index 414db2bce715..392138fe59b6 100644
--- a/include/linux/tty.h
+++ b/include/linux/tty.h
@@ -556,6 +556,7 @@ extern struct tty_struct *tty_init_dev(struct tty_driver *driver, int idx);
extern void tty_release_struct(struct tty_struct *tty, int idx);
extern int tty_release(struct inode *inode, struct file *filp);
extern void tty_init_termios(struct tty_struct *tty);
+extern void tty_save_termios(struct tty_struct *tty);
extern int tty_standard_install(struct tty_driver *driver,
struct tty_struct *tty);
--
2.19.2
This is a note to let you know that I've just added the patch titled
tty: serial: 8250_mtk: always resume the device in probe.
to my tty git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
in the tty-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From 100bc3e2bebf95506da57cbdf5f26b25f6da4c81 Mon Sep 17 00:00:00 2001
From: Peter Shih <pihsun(a)chromium.org>
Date: Tue, 27 Nov 2018 12:49:50 +0800
Subject: tty: serial: 8250_mtk: always resume the device in probe.
serial8250_register_8250_port calls uart_config_port, which calls
config_port on the port before it tries to power on the port. So we need
the port to be on before calling serial8250_register_8250_port. Change
the code to always do a runtime resume in probe before registering port,
and always do a runtime suspend in remove.
This basically reverts the change in commit 68e5fc4a255a ("tty: serial:
8250_mtk: use pm_runtime callbacks for enabling"), but still use
pm_runtime callbacks.
Fixes: 68e5fc4a255a ("tty: serial: 8250_mtk: use pm_runtime callbacks for enabling")
Signed-off-by: Peter Shih <pihsun(a)chromium.org>
Cc: stable <stable(a)vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/tty/serial/8250/8250_mtk.c | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_mtk.c b/drivers/tty/serial/8250/8250_mtk.c
index dd5e1cede2b5..c3f933d10295 100644
--- a/drivers/tty/serial/8250/8250_mtk.c
+++ b/drivers/tty/serial/8250/8250_mtk.c
@@ -213,17 +213,17 @@ static int mtk8250_probe(struct platform_device *pdev)
platform_set_drvdata(pdev, data);
- pm_runtime_enable(&pdev->dev);
- if (!pm_runtime_enabled(&pdev->dev)) {
- err = mtk8250_runtime_resume(&pdev->dev);
- if (err)
- return err;
- }
+ err = mtk8250_runtime_resume(&pdev->dev);
+ if (err)
+ return err;
data->line = serial8250_register_8250_port(&uart);
if (data->line < 0)
return data->line;
+ pm_runtime_set_active(&pdev->dev);
+ pm_runtime_enable(&pdev->dev);
+
return 0;
}
@@ -234,13 +234,11 @@ static int mtk8250_remove(struct platform_device *pdev)
pm_runtime_get_sync(&pdev->dev);
serial8250_unregister_port(data->line);
+ mtk8250_runtime_suspend(&pdev->dev);
pm_runtime_disable(&pdev->dev);
pm_runtime_put_noidle(&pdev->dev);
- if (!pm_runtime_status_suspended(&pdev->dev))
- mtk8250_runtime_suspend(&pdev->dev);
-
return 0;
}
--
2.19.2
From: Nathan Chancellor <natechancellor(a)gmail.com>
[ Upstream commit eef3dc34a1e0b01d53328b88c25237bcc7323777 ]
When building the kernel with Clang, the following section mismatch
warning appears:
WARNING: vmlinux.o(.text+0x38b3c): Section mismatch in reference from
the function omap44xx_prm_late_init() to the function
.init.text:omap44xx_prm_enable_io_wakeup()
The function omap44xx_prm_late_init() references
the function __init omap44xx_prm_enable_io_wakeup().
This is often because omap44xx_prm_late_init lacks a __init
annotation or the annotation of omap44xx_prm_enable_io_wakeup is wrong.
Remove the __init annotation from omap44xx_prm_enable_io_wakeup so there
is no more mismatch.
Signed-off-by: Nathan Chancellor <natechancellor(a)gmail.com>
Signed-off-by: Tony Lindgren <tony(a)atomide.com>
Signed-off-by: Sasha Levin <sashal(a)kernel.org>
---
arch/arm/mach-omap2/prm44xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/prm44xx.c b/arch/arm/mach-omap2/prm44xx.c
index 0958d070d3db..46e29afe1c09 100644
--- a/arch/arm/mach-omap2/prm44xx.c
+++ b/arch/arm/mach-omap2/prm44xx.c
@@ -333,7 +333,7 @@ void omap44xx_prm_reconfigure_io_chain(void)
* to occur, WAKEUPENABLE bits must be set in the pad mux registers, and
* omap44xx_prm_reconfigure_io_chain() must be called. No return value.
*/
-static void __init omap44xx_prm_enable_io_wakeup(void)
+static void omap44xx_prm_enable_io_wakeup(void)
{
s32 inst = omap4_prmst_get_prm_dev_inst();
--
2.17.1
From: Nathan Chancellor <natechancellor(a)gmail.com>
[ Upstream commit eef3dc34a1e0b01d53328b88c25237bcc7323777 ]
When building the kernel with Clang, the following section mismatch
warning appears:
WARNING: vmlinux.o(.text+0x38b3c): Section mismatch in reference from
the function omap44xx_prm_late_init() to the function
.init.text:omap44xx_prm_enable_io_wakeup()
The function omap44xx_prm_late_init() references
the function __init omap44xx_prm_enable_io_wakeup().
This is often because omap44xx_prm_late_init lacks a __init
annotation or the annotation of omap44xx_prm_enable_io_wakeup is wrong.
Remove the __init annotation from omap44xx_prm_enable_io_wakeup so there
is no more mismatch.
Signed-off-by: Nathan Chancellor <natechancellor(a)gmail.com>
Signed-off-by: Tony Lindgren <tony(a)atomide.com>
Signed-off-by: Sasha Levin <sashal(a)kernel.org>
---
arch/arm/mach-omap2/prm44xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/prm44xx.c b/arch/arm/mach-omap2/prm44xx.c
index 30768003f854..8c505284bc0c 100644
--- a/arch/arm/mach-omap2/prm44xx.c
+++ b/arch/arm/mach-omap2/prm44xx.c
@@ -344,7 +344,7 @@ static void omap44xx_prm_reconfigure_io_chain(void)
* to occur, WAKEUPENABLE bits must be set in the pad mux registers, and
* omap44xx_prm_reconfigure_io_chain() must be called. No return value.
*/
-static void __init omap44xx_prm_enable_io_wakeup(void)
+static void omap44xx_prm_enable_io_wakeup(void)
{
s32 inst = omap4_prmst_get_prm_dev_inst();
--
2.17.1
From: Nathan Chancellor <natechancellor(a)gmail.com>
[ Upstream commit eef3dc34a1e0b01d53328b88c25237bcc7323777 ]
When building the kernel with Clang, the following section mismatch
warning appears:
WARNING: vmlinux.o(.text+0x38b3c): Section mismatch in reference from
the function omap44xx_prm_late_init() to the function
.init.text:omap44xx_prm_enable_io_wakeup()
The function omap44xx_prm_late_init() references
the function __init omap44xx_prm_enable_io_wakeup().
This is often because omap44xx_prm_late_init lacks a __init
annotation or the annotation of omap44xx_prm_enable_io_wakeup is wrong.
Remove the __init annotation from omap44xx_prm_enable_io_wakeup so there
is no more mismatch.
Signed-off-by: Nathan Chancellor <natechancellor(a)gmail.com>
Signed-off-by: Tony Lindgren <tony(a)atomide.com>
Signed-off-by: Sasha Levin <sashal(a)kernel.org>
---
arch/arm/mach-omap2/prm44xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/prm44xx.c b/arch/arm/mach-omap2/prm44xx.c
index 30768003f854..8c505284bc0c 100644
--- a/arch/arm/mach-omap2/prm44xx.c
+++ b/arch/arm/mach-omap2/prm44xx.c
@@ -344,7 +344,7 @@ static void omap44xx_prm_reconfigure_io_chain(void)
* to occur, WAKEUPENABLE bits must be set in the pad mux registers, and
* omap44xx_prm_reconfigure_io_chain() must be called. No return value.
*/
-static void __init omap44xx_prm_enable_io_wakeup(void)
+static void omap44xx_prm_enable_io_wakeup(void)
{
s32 inst = omap4_prmst_get_prm_dev_inst();
--
2.17.1
From: Nathan Chancellor <natechancellor(a)gmail.com>
[ Upstream commit eef3dc34a1e0b01d53328b88c25237bcc7323777 ]
When building the kernel with Clang, the following section mismatch
warning appears:
WARNING: vmlinux.o(.text+0x38b3c): Section mismatch in reference from
the function omap44xx_prm_late_init() to the function
.init.text:omap44xx_prm_enable_io_wakeup()
The function omap44xx_prm_late_init() references
the function __init omap44xx_prm_enable_io_wakeup().
This is often because omap44xx_prm_late_init lacks a __init
annotation or the annotation of omap44xx_prm_enable_io_wakeup is wrong.
Remove the __init annotation from omap44xx_prm_enable_io_wakeup so there
is no more mismatch.
Signed-off-by: Nathan Chancellor <natechancellor(a)gmail.com>
Signed-off-by: Tony Lindgren <tony(a)atomide.com>
Signed-off-by: Sasha Levin <sashal(a)kernel.org>
---
arch/arm/mach-omap2/prm44xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/prm44xx.c b/arch/arm/mach-omap2/prm44xx.c
index 1c0c1663f078..5affa9f5300b 100644
--- a/arch/arm/mach-omap2/prm44xx.c
+++ b/arch/arm/mach-omap2/prm44xx.c
@@ -344,7 +344,7 @@ static void omap44xx_prm_reconfigure_io_chain(void)
* to occur, WAKEUPENABLE bits must be set in the pad mux registers, and
* omap44xx_prm_reconfigure_io_chain() must be called. No return value.
*/
-static void __init omap44xx_prm_enable_io_wakeup(void)
+static void omap44xx_prm_enable_io_wakeup(void)
{
s32 inst = omap4_prmst_get_prm_dev_inst();
--
2.17.1
This is a note to let you know that I've just added the patch titled
usb: quirk: add no-LPM quirk on SanDisk Ultra Flair device
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From 2f2dde6ba89b1ef1fe23c1138131b315d9aa4019 Mon Sep 17 00:00:00 2001
From: Harry Pan <harry.pan(a)intel.com>
Date: Thu, 29 Nov 2018 00:40:41 +0800
Subject: usb: quirk: add no-LPM quirk on SanDisk Ultra Flair device
Some lower volume SanDisk Ultra Flair in 16GB, which the VID:PID is
in 0781:5591, will aggressively request LPM of U1/U2 during runtime,
when using this thumb drive as the OS installation key we found the
device will generate failure during U1 exit path making it dropped
from the USB bus, this causes a corrupted installation in system at
the end.
i.e.,
[ 166.918296] hub 2-0:1.0: state 7 ports 7 chg 0000 evt 0004
[ 166.918327] usb usb2-port2: link state change
[ 166.918337] usb usb2-port2: do warm reset
[ 166.970039] usb usb2-port2: not warm reset yet, waiting 50ms
[ 167.022040] usb usb2-port2: not warm reset yet, waiting 200ms
[ 167.276043] usb usb2-port2: status 02c0, change 0041, 5.0 Gb/s
[ 167.276050] usb 2-2: USB disconnect, device number 2
[ 167.276058] usb 2-2: unregistering device
[ 167.276060] usb 2-2: unregistering interface 2-2:1.0
[ 167.276170] xhci_hcd 0000:00:15.0: shutdown urb ffffa3c7cc695cc0 ep1in-bulk
[ 167.284055] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 167.284064] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 33 04 90 00 01 00 00
...
Analyzed the USB trace in the link layer we realized it is because
of the 6-ms timer of tRecoveryConfigurationTimeout which documented
on the USB 3.2 Revision 1.0, the section 7.5.10.4.2 of "Exit from
Recovery.Configuration"; device initiates U1 exit -> Recovery.Active
-> Recovery.Configuration, then the host timer timeout makes the link
transits to eSS.Inactive -> Rx.Detect follows by a Warm Reset.
Interestingly, the other higher volume of SanDisk Ultra Flair sharing
the same VID:PID, such as 64GB, would not request LPM during runtime,
it sticks at U0 always, thus disabling LPM does not affect those thumb
drives at all.
The same odd occures in SanDisk Ultra Fit 16GB, VID:PID in 0781:5583.
Signed-off-by: Harry Pan <harry.pan(a)intel.com>
Cc: stable <stable(a)vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/usb/core/quirks.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index 0690fcff0ea2..514c5214ddb2 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -333,6 +333,10 @@ static const struct usb_device_id usb_quirk_list[] = {
/* Midiman M-Audio Keystation 88es */
{ USB_DEVICE(0x0763, 0x0192), .driver_info = USB_QUIRK_RESET_RESUME },
+ /* SanDisk Ultra Fit and Ultra Flair */
+ { USB_DEVICE(0x0781, 0x5583), .driver_info = USB_QUIRK_NO_LPM },
+ { USB_DEVICE(0x0781, 0x5591), .driver_info = USB_QUIRK_NO_LPM },
+
/* M-Systems Flash Disk Pioneers */
{ USB_DEVICE(0x08ec, 0x1000), .driver_info = USB_QUIRK_RESET_RESUME },
--
2.19.2
This is a note to let you know that I've just added the patch titled
usb: appledisplay: Add 27" Apple Cinema Display
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From d7859905301880ad3e16272399d26900af3ac496 Mon Sep 17 00:00:00 2001
From: Alexander Theissen <alex.theissen(a)me.com>
Date: Tue, 4 Dec 2018 23:43:35 +0100
Subject: usb: appledisplay: Add 27" Apple Cinema Display
Add another Apple Cinema Display to the list of supported displays.
Signed-off-by: Alexander Theissen <alex.theissen(a)me.com>
Cc: stable <stable(a)vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/usb/misc/appledisplay.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/misc/appledisplay.c b/drivers/usb/misc/appledisplay.c
index 85b48c6ddc7e..39ca31b4de46 100644
--- a/drivers/usb/misc/appledisplay.c
+++ b/drivers/usb/misc/appledisplay.c
@@ -51,6 +51,7 @@ static const struct usb_device_id appledisplay_table[] = {
{ APPLEDISPLAY_DEVICE(0x921c) },
{ APPLEDISPLAY_DEVICE(0x921d) },
{ APPLEDISPLAY_DEVICE(0x9222) },
+ { APPLEDISPLAY_DEVICE(0x9226) },
{ APPLEDISPLAY_DEVICE(0x9236) },
/* Terminating entry */
--
2.19.2
Hi,
On Sun, Sep 9, 2018 at 9:24 PM Terin Stock <terin(a)terinstock.com> wrote:
>
> Modify the wait delay utilize the high resolution timer API to allow for
> more precisely scheduled callbacks.
>
> A previous commit added a 1ms retry delay after multiple consecutive
> NAKed transactions using jiffies. On systems with a low timer interrupt
> frequency, this delay may be significantly longer than specified,
> resulting in misbehavior with some USB devices.
>
> This scenario was reached on a Raspberry Pi 3B with a Macally FDD-USB
> floppy drive (identified as 0424:0fdc Standard Microsystems Corp.
> Floppy, based on the USB97CFDC USB FDC). With the relay delay, the drive
> would be unable to mount a disk, replying with NAKs until the device was
> reset.
>
> Using ktime, the delta between starting the timer (in dwc2_hcd_qh_add)
> and the callback function can be determined. With the original delay
> implementation, this value was consistently approximately 12ms. (output
> in us).
>
> <idle>-0 [000] ..s. 1600.559974: dwc2_wait_timer_fn: wait_timer delta: 11976
> <idle>-0 [000] ..s. 1600.571974: dwc2_wait_timer_fn: wait_timer delta: 11977
> <idle>-0 [000] ..s. 1600.583974: dwc2_wait_timer_fn: wait_timer delta: 11976
> <idle>-0 [000] ..s. 1600.595974: dwc2_wait_timer_fn: wait_timer delta: 11977
>
> After converting the relay delay to using a higher resolution timer, the
> delay was much closer to 1ms.
>
> <idle>-0 [000] d.h. 1956.553017: dwc2_wait_timer_fn: wait_timer delta: 1002
> <idle>-0 [000] d.h. 1956.554114: dwc2_wait_timer_fn: wait_timer delta: 1002
> <idle>-0 [000] d.h. 1957.542660: dwc2_wait_timer_fn: wait_timer delta: 1004
> <idle>-0 [000] d.h. 1957.543701: dwc2_wait_timer_fn: wait_timer delta: 1002
>
> The floppy drive operates properly with delays up to approximately 5ms,
> and sends NAKs for any delays that are longer.
>
> Fixes: 38d2b5fb75c1 ("usb: dwc2: host: Don't retry NAKed transactions right away")
> Signed-off-by: Terin Stock <terin(a)terinstock.com>
> ---
> drivers/usb/dwc2/hcd.h | 2 +-
> drivers/usb/dwc2/hcd_queue.c | 19 ++++++++++++-------
> 2 files changed, 13 insertions(+), 8 deletions(-)
Reviewed-by: Douglas Anderson <dianders(a)chromium.org>
Cc: stable(a)vger.kernel.org
This is a note to let you know that I've just added the patch titled
staging: rtl8712: Fix possible buffer overrun
to my staging git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
in the staging-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From 300cd664865bed5d50ae0a42fb4e3a6f415e8a10 Mon Sep 17 00:00:00 2001
From: Young Xiao <YangX92(a)hotmail.com>
Date: Wed, 28 Nov 2018 08:06:53 +0000
Subject: staging: rtl8712: Fix possible buffer overrun
In commit 8b7a13c3f404 ("staging: r8712u: Fix possible buffer
overrun") we fix a potential off by one by making the limit smaller.
The better fix is to make the buffer larger. This makes it match up
with the similar code in other drivers.
Fixes: 8b7a13c3f404 ("staging: r8712u: Fix possible buffer overrun")
Signed-off-by: Young Xiao <YangX92(a)hotmail.com>
Cc: stable <stable(a)vger.kernel.org>
Reviewed-by: Dan Carpenter <dan.carpenter(a)oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/staging/rtl8712/mlme_linux.c | 2 +-
drivers/staging/rtl8712/rtl871x_mlme.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8712/mlme_linux.c b/drivers/staging/rtl8712/mlme_linux.c
index 9d156efbc9ed..4d473f008aa4 100644
--- a/drivers/staging/rtl8712/mlme_linux.c
+++ b/drivers/staging/rtl8712/mlme_linux.c
@@ -146,7 +146,7 @@ void r8712_report_sec_ie(struct _adapter *adapter, u8 authmode, u8 *sec_ie)
p = buff;
p += sprintf(p, "ASSOCINFO(ReqIEs=");
len = sec_ie[1] + 2;
- len = (len < IW_CUSTOM_MAX) ? len : IW_CUSTOM_MAX - 1;
+ len = (len < IW_CUSTOM_MAX) ? len : IW_CUSTOM_MAX;
for (i = 0; i < len; i++)
p += sprintf(p, "%02x", sec_ie[i]);
p += sprintf(p, ")");
diff --git a/drivers/staging/rtl8712/rtl871x_mlme.c b/drivers/staging/rtl8712/rtl871x_mlme.c
index a7374006a9fb..986a1d526918 100644
--- a/drivers/staging/rtl8712/rtl871x_mlme.c
+++ b/drivers/staging/rtl8712/rtl871x_mlme.c
@@ -1346,7 +1346,7 @@ sint r8712_restruct_sec_ie(struct _adapter *adapter, u8 *in_ie,
u8 *out_ie, uint in_len)
{
u8 authmode = 0, match;
- u8 sec_ie[255], uncst_oui[4], bkup_ie[255];
+ u8 sec_ie[IW_CUSTOM_MAX], uncst_oui[4], bkup_ie[255];
u8 wpa_oui[4] = {0x0, 0x50, 0xf2, 0x01};
uint ielength, cnt, remove_cnt;
int iEntry;
--
2.19.2
This is a note to let you know that I've just added the patch titled
Revert commit ef9209b642f "staging: rtl8723bs: Fix indenting errors
to my staging git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
in the staging-linus branch.
The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel release.
If you have any questions about this process, please let me know.
>From 87e4a5405f087427fbf8b437d2796283dce2b38f Mon Sep 17 00:00:00 2001
From: Young Xiao <YangX92(a)hotmail.com>
Date: Tue, 27 Nov 2018 09:12:20 +0000
Subject: Revert commit ef9209b642f "staging: rtl8723bs: Fix indenting errors
and an off-by-one mistake in core/rtw_mlme_ext.c"
pstapriv->max_num_sta is always <= NUM_STA, since max_num_sta is either
set in _rtw_init_sta_priv() or rtw_set_beacon().
Fixes: ef9209b642f1 ("staging: rtl8723bs: Fix indenting errors and an off-by-one mistake in core/rtw_mlme_ext.c")
Signed-off-by: Young Xiao <YangX92(a)hotmail.com>
Reviewed-by: Dan Carpenter <dan.carpenter(a)oracle.com>
Cc: stable <stable(a)vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org>
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c b/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
index 69c7abc0e3a5..8445d516c93d 100644
--- a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
+++ b/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
@@ -1565,7 +1565,7 @@ unsigned int OnAssocReq(struct adapter *padapter, union recv_frame *precv_frame)
if (pstat->aid > 0) {
DBG_871X(" old AID %d\n", pstat->aid);
} else {
- for (pstat->aid = 1; pstat->aid < NUM_STA; pstat->aid++)
+ for (pstat->aid = 1; pstat->aid <= NUM_STA; pstat->aid++)
if (pstapriv->sta_aid[pstat->aid - 1] == NULL)
break;
--
2.19.2
The patch titled
Subject: panic: Avoid the extra noise dmesg
has been removed from the -mm tree. Its filename was
panic-avoid-the-extra-noise-dmesg.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
From: Feng Tang <feng.tang(a)intel.com>
Subject: panic: Avoid the extra noise dmesg
When kernel panic happens, it will first print the panic call stack,
then the ending msg like:
[ 35.743249] ---[ end Kernel panic - not syncing: Fatal exception
[ 35.749975] ------------[ cut here ]------------
The above message are very useful for debugging.
But if system is configured to not reboot on panic, say the "panic_timeout"
parameter equals 0, it will likely print out many noisy message like
WARN() call stack for each and every CPU except the panic one, messages
like below:
WARNING: CPU: 1 PID: 280 at kernel/sched/core.c:1198 set_task_cpu+0x183/0x190
Call Trace:
<IRQ>
try_to_wake_up
default_wake_function
autoremove_wake_function
__wake_up_common
__wake_up_common_lock
__wake_up
wake_up_klogd_work_func
irq_work_run_list
irq_work_tick
update_process_times
tick_sched_timer
__hrtimer_run_queues
hrtimer_interrupt
smp_apic_timer_interrupt
apic_timer_interrupt
For people working in console mode, the screen will first show the panic
call stack, but immediately overridded by these noisy extra messages, which
makes debugging much more difficult, as the original context gets lost on
screen.
Also these noisy messages will confuse some users, as I have seen many bug
reporters posted the noisy message into bugzilla, instead of the real panic
call stack and context.
Removing the "local_irq_enable" will avoid the noisy message.
The justification for the removing is: when code runs to this point, it
means user has chosed to not reboot, or do any special handling by using
the panic notifier method, no much point in re-enabling the interrupt.
Link: http://lkml.kernel.org/r/1543902228-23834-1-git-send-email-feng.tang@intel.…
Signed-off-by: Feng Tang <feng.tang(a)intel.com>
Cc: Thomas Gleixner <tglx(a)linutronix.de>
Cc: Kees Cook <keescook(a)chromium.org>
Cc: Borislav Petkov <bp(a)suse.de>
Cc: Petr Mladek <pmladek(a)suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky(a)gmail.com>
Cc: <stable(a)vger.kernel.org>
Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org>
---
--- a/kernel/panic.c~panic-avoid-the-extra-noise-dmesg
+++ a/kernel/panic.c
@@ -322,7 +322,6 @@ void panic(const char *fmt, ...)
}
#endif
pr_emerg("---[ end Kernel panic - not syncing: %s ]---\n", buf);
- local_irq_enable();
for (i = 0; ; i += PANIC_TIMER_STEP) {
touch_softlockup_watchdog();
if (i >= i_next) {
_
Patches currently in -mm which might be from feng.tang(a)intel.com are
panic-add-options-to-print-system-info-when-panic-happens.patch
kernel-sysctl-add-panic_print-into-sysctl.patch