From: kernel test robot <oliver.sang@intel.com>
To: Jiao Zhou <jiaozhou@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-efi@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
Jiao Zhou <jiaozhou@google.com>,
"Ard Biesheuvel" <ardb@kernel.org>, Jeremy Kerr <jk@ozlabs.org>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [PATCH] kernel: Add Mount Option For Efivarfs
Date: Tue, 29 Aug 2023 14:24:53 +0800 [thread overview]
Message-ID: <202308291443.ea96ac66-oliver.sang@intel.com> (raw)
In-Reply-To: <20230822162350.1.I96423a31e88428004c2f4a28ccad13828adf433e@changeid>
Hello,
kernel test robot noticed "BUG:KASAN:global-out-of-bounds_in_fs_validate_description" on:
commit: 635056da10724c7af59483a8251f8e6432b50faa ("[PATCH] kernel: Add Mount Option For Efivarfs")
url: https://github.com/intel-lab-lkp/linux/commits/Jiao-Zhou/kernel-Add-Mount-Option-For-Efivarfs/20230823-002613
base: https://git.kernel.org/cgit/linux/kernel/git/efi/efi.git next
patch link: https://lore.kernel.org/all/20230822162350.1.I96423a31e88428004c2f4a28ccad13828adf433e@changeid/
patch subject: [PATCH] kernel: Add Mount Option For Efivarfs
in testcase: boot
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202308291443.ea96ac66-oliver.sang@intel.com
[ 17.276007][ T1] ==================================================================
[ 17.277001][ T1] BUG: KASAN: global-out-of-bounds in fs_validate_description+0x1c2/0x1e0
[ 17.278097][ T1] Read of size 8 at addr ffffffff84f20b80 by task swapper/1
[ 17.278821][ T1]
[ 17.278821][ T1] CPU: 0 PID: 1 Comm: swapper Not tainted 6.5.0-rc1-00012-g635056da1072 #1
[ 17.278821][ T1] Call Trace:
[ 17.278821][ T1] <TASK>
[ 17.278821][ T1] dump_stack_lvl+0x32/0xa0
[ 17.278821][ T1] print_address_description+0x33/0x3c0
[ 17.278821][ T1] ? fs_validate_description+0x1c2/0x1e0
[ 17.278821][ T1] print_report+0xc1/0x280
[ 17.278821][ T1] ? kasan_addr_to_slab+0x11/0x80
[ 17.278821][ T1] ? fs_validate_description+0x1c2/0x1e0
[ 17.278821][ T1] kasan_report+0x154/0x190
[ 17.278821][ T1] ? fs_validate_description+0x1c2/0x1e0
[ 17.278821][ T1] __asan_report_load8_noabort+0x18/0x20
[ 17.278821][ T1] fs_validate_description+0x1c2/0x1e0
[ 17.278821][ T1] register_filesystem+0x73/0x2b0
[ 17.278821][ T1] ? pstore_blk_init+0x720/0x720
[ 17.278821][ T1] efivarfs_init+0x24/0x50
[ 17.278821][ T1] do_one_initcall+0xfc/0x480
[ 17.278821][ T1] ? trace_event_raw_event_initcall_level+0x1c0/0x1c0
[ 17.278821][ T1] ? __kasan_kmalloc+0x96/0xa0
[ 17.278821][ T1] ? do_initcalls+0x47/0x5b0
[ 17.278821][ T1] do_initcalls+0x2ae/0x5b0
[ 17.278821][ T1] kernel_init_freeable+0x313/0x570
[ 17.278821][ T1] ? rest_init+0x260/0x260
[ 17.278821][ T1] kernel_init+0x23/0x240
[ 17.278821][ T1] ? rest_init+0x260/0x260
[ 17.278821][ T1] ret_from_fork+0x22/0x30
[ 17.278821][ T1] </TASK>
[ 17.278821][ T1]
[ 17.278821][ T1] The buggy address belongs to the variable:
[ 17.278821][ T1] efivarfs_parameters+0x40/0x80
[ 17.278821][ T1]
[ 17.278821][ T1] The buggy address belongs to the physical page:
[ 17.278821][ T1] page:(____ptrval____) refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x4f20
[ 17.278821][ T1] flags: 0x4000000000001000(reserved|zone=1)
[ 17.278821][ T1] page_type: 0xffffffff()
[ 17.278821][ T1] raw: 4000000000001000 ffffea000013c808 ffffea000013c808 0000000000000000
[ 17.278821][ T1] raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000
[ 17.278821][ T1] page dumped because: kasan: bad access detected
[ 17.278821][ T1] page_owner info is not present (never set?)
[ 17.278821][ T1]
[ 17.278821][ T1] Memory state around the buggy address:
[ 17.278821][ T1] ffffffff84f20a80: 00 00 f9 f9 f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9
[ 17.278821][ T1] ffffffff84f20b00: 04 f9 f9 f9 f9 f9 f9 f9 00 00 00 00 00 00 00 00
[ 17.278821][ T1] >ffffffff84f20b80: f9 f9 f9 f9 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.278821][ T1] ^
[ 17.278821][ T1] ffffffff84f20c00: 00 00 00 00 00 00 00 00 f9 f9 f9 f9 00 00 00 00
[ 17.278821][ T1] ffffffff84f20c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 17.278821][ T1] ==================================================================
[ 17.311721][ T1] Disabling lock debugging due to kernel taint
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230829/202308291443.ea96ac66-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-29 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 16:23 [PATCH] kernel: Add Mount Option For Efivarfs Jiao Zhou
2023-08-23 16:30 ` Ard Biesheuvel
2023-08-23 22:30 ` Matthew Garrett
[not found] ` <CAFyYRf2DschMpD35rkn4-0quKkga=kf0ztQQ3J9ZBvKmKTpAkw@mail.gmail.com>
2023-08-24 17:16 ` Matthew Garrett
2023-08-29 6:24 ` kernel test robot [this message]
2023-08-29 7:59 ` Ard Biesheuvel
2023-08-31 15:31 Jiao Zhou
2023-08-31 15:55 ` Ard Biesheuvel
2023-09-04 12:17 ` Christian Brauner
[not found] ` <CAFyYRf0xyZSLypcHvpzCXQ5dUztTXbE4Ea1xAcQLfbP4+9N9sQ@mail.gmail.com>
2023-09-06 7:06 ` Ard Biesheuvel
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=202308291443.ea96ac66-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=ardb@kernel.org \
--cc=jiaozhou@google.com \
--cc=jk@ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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).