From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Qian Cai <cai@gmx.us>
Cc: linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
"Tobin C. Harding" <me@tobin.cc>,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Subject: Re: WARNING: CPU: 26 PID: 64391 at lib/vsprintf.c:2193 set_precision+0x84/0x90
Date: Tue, 13 Nov 2018 19:29:20 +0200 [thread overview]
Message-ID: <20181113172920.GI10650@smile.fi.intel.com> (raw)
In-Reply-To: <1542128132.12945.19.camel@gmx.us>
On Tue, Nov 13, 2018 at 11:55:32AM -0500, Qian Cai wrote:
+Cc Rasmus
> Running the trinity fuzzer with a non-root user on an aarch64 server with the
> latest mainline (rc2) generated this. Is it just a false alarm to ignore?
>
> [ 807.847370] precision 65525 too large
It seems like someone uses -EAGAIN as a parameter to printf().
Or rather this line
if (!fs && (request_module("fs-%.*s", len, name) == 0)) {
...
}
Care to print the len and name parameters before this line?
> [ 807.847449] WARNING: CPU: 26 PID: 64391 at lib/vsprintf.c:2193
> set_precision+0x84/0x90
> [ 807.860161] Modules linked in: cast6_generic cast_common lrw bridge 8021q
> garp mrp stp llc dlci tcp_diag inet_diag af_key pptp gre l2tp_ppp l2tp_netlink
> l2tp_core ip6_udp_tunnel udp_tunnel pppoe pppox ppp_generic slhc crypto_user
> ib_core nfnetlink scsi_transport_iscsi atm sctp vfat fat ghash_ce sha2_ce
> sha256_arm64 sha1_ce ses enclosure ipmi_ssif sg ipmi_si ipmi_devintf sbsa_gwdt
> ipmi_msghandler sch_fq_codel xfs libcrc32c marvell mpt3sas mlx5_core raid_class
> hibmc_drm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm
> ixgbe hisi_sas_v2_hw igb hisi_sas_main libsas hns_dsaf mlxfw devlink
> hns_enet_drv mdio i2c_designware_platform i2c_algo_bit i2c_designware_core
> ehci_platform scsi_transport_sas hns_mdio hnae dm_mirror dm_region_hash dm_log
> dm_mod
> [ 807.927838] CPU: 26 PID: 64391 Comm: trinity-c90 Kdump: loaded Tainted:
> G W 4.20.0-rc2+ #16
> [ 807.937494] Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.50
> 06/01/2018
> [ 807.944718] pstate: 60000005 (nZCv daif -PAN -UAO)
> [ 807.949515] pc : set_precision+0x84/0x90
> [ 807.953439] lr : set_precision+0x84/0x90
> [ 807.957362] sp : ffff801e6430f6b0
> [ 807.960677] x29: ffff801e6430f6b0 x28: ffff801e6430fb10
> [ 807.965992] x27: 0000000000000003 x26: 00000000ffffffd8
> [ 807.971307] x25: ffff801e6430fba0 x24: ffff801e6430fb48
> [ 807.976622] x23: ffff2000093ddfa0 x22: ffff801e6430f770
> [ 807.981937] x21: ffff2000090eb4a6 x20: ffff801e6430f770
> [ 807.987252] x19: 000000000000fff5 x18: 0000000000000000
> [ 807.992569] x17: 0000000000000000 x16: 0000000000000000
> [ 807.997884] x15: 0000000000000000 x14: 3878302031343220
> [ 808.003201] x13: 6265783020303939 x12: ffff04000172b49c
> [ 808.008516] x11: 1fffe4000172b49b x10: ffff04000172b49b
> [ 808.013832] x9 : 0000000000000000 x8 : 203532353536206e
> [ 808.019148] x7 : 6f69736963657270 x6 : 0000000041b58ab3
> [ 808.024463] x5 : dfff200000000000 x4 : dfff200000000000
> [ 808.029779] x3 : dfff200000000000 x2 : 65a2459128144800
> [ 808.035093] x1 : 65a2459128144800 x0 : 0000000000000000
> [ 808.040408] Call trace:
> [ 808.042861] set_precision+0x84/0x90
> [ 808.046440] vsnprintf+0x23c/0x858
> [ 808.049845] __request_module+0x1a0/0x8b8
> [ 808.053860] get_fs_type+0xb0/0x138
> [ 808.057351] do_mount+0x2c4/0x13c0
> [ 808.060756] ksys_mount+0xf4/0x110
> [ 808.064160] __arm64_sys_mount+0x70/0x88
> [ 808.068087] el0_svc_handler+0xd4/0x198
> [ 808.071928] el0_svc+0x8/0xc
> [ 808.074810] irq event stamp: 347872
> [ 808.078305] hardirqs last enabled at (347871): [<ffff2000082080e8>]
> vprintk_emit+0x2b0/0x5c0
> [ 808.086833] hardirqs last disabled at (347872): [<ffff200008081490>]
> do_debug_exception+0xd8/0x190
> [ 808.095795] softirqs last enabled at (347844): [<ffff200008082210>]
> __do_softirq+0x7c8/0x9c8
> [ 808.104325] softirqs last disabled at (347837): [<ffff20000812dbe4>]
> irq_exit+0x25c/0x2f0
> [ 808.112502] ---[ end trace 598902d30712b79e ]---
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2018-11-13 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 16:55 WARNING: CPU: 26 PID: 64391 at lib/vsprintf.c:2193 set_precision+0x84/0x90 Qian Cai
2018-11-13 17:20 ` Geert Uytterhoeven
2018-11-13 17:32 ` Andy Shevchenko
2018-11-13 17:29 ` Andy Shevchenko [this message]
2018-11-13 18:58 ` Qian Cai
2018-11-13 19:23 ` Steven Rostedt
2018-11-13 23:05 ` Petr Mladek
2018-11-14 9:38 ` Andy Shevchenko
2018-11-14 19:29 ` Petr Mladek
2018-11-14 20:35 ` Qian Cai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181113172920.GI10650@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=cai@gmx.us \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=pmladek@suse.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).