New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 887142 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Sep 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Aleena: kernel panic during boot

Project Member Reported by yuzhao@chromium.org, Sep 19

Issue description

Chrome OS Version: 11075.0
Chrome OS Platform: Aleena

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Enable KASAN
(2) Boot


Expected Result:
No kernel panic

Actual Result:
Kernel panic within ~30s after boot:

[   25.566073] general protection fault: 0000 [#1] PREEMPT SMP KASAN NOPTI
[   25.621976] gsmi: Log Shutdown Reason 0x03
<snipped>
[   25.747085] Call Trace:
[   25.749532]  name_show+0x51/0x6f
[   25.752760]  dev_attr_show+0x59/0xa0
[   25.756333]  ? device_namespace+0x9e/0x9e
[   25.760339]  sysfs_kf_seq_show+0x228/0x33b
[   25.764434]  seq_read+0x74f/0xd58
[   25.767747]  ? set_track+0x63/0xfa
[   25.771148]  ? kzalloc+0xf/0xf
[   25.774200]  ? _copy_to_user+0x87/0x9a
[   25.777947]  __vfs_read+0x106/0x320
[   25.781433]  ? mandatory_lock+0x94/0x94
[   25.785267]  ? fsnotify_unmount_inodes+0x17d/0x17d
[   25.790053]  ? inode_security+0x17/0x40
[   25.793885]  ? selinux_file_permission+0x176/0x342
[   25.798670]  ? security_file_permission+0x77/0x98
[   25.803369]  vfs_read+0xf3/0x197
[   25.806595]  SyS_read+0xfa/0x19b
[   25.809822]  ? file_end_write+0x91/0x91
[   25.813653]  ? filp_close+0xdb/0x100
[   25.817225]  ? file_end_write+0x91/0x91
[   25.821057]  do_syscall_64+0x184/0x1bb
[   25.824804]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
<snipped>
[   25.895502] RIP: rdev_get_name+0x29/0xa5 RSP: ffff8801d45779f0
[   26.550863] ---[ end trace fb2a7bb4f63aeba5 ]---

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Less 10 boots

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 21

Labels: merge-merged-chromeos-4.4
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/75ca529116159ad16ad7c6164331f9e5a8033d8b

commit 75ca529116159ad16ad7c6164331f9e5a8033d8b
Author: Yu Zhao <yuzhao@google.com>
Date: Fri Sep 21 02:03:33 2018

FROMGIT: regulator: fix crash caused by null driver data

dev_set_drvdata() needs to be called before device_register()
exposes device to userspace. Otherwise kernel crashes after it
gets null pointer from dev_get_drvdata() when userspace tries
to access sysfs entries.

[Removed backtrace for length -- broonie]

Signed-off-by: Yu Zhao <yuzhao@google.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Cc: stable@vger.kernel.org
(cherry picked from commit fb6de923ca3358a91525552b4907d4cb38730bdd
 git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git)

BUG= chromium:887142 
TEST=Built with KASAN and booted 10x without seeing any problem.

Change-Id: I81eda85e15cabb4f35d1eebdaac87a9c26a7a10b
Reviewed-on: https://chromium-review.googlesource.com/1237085
Commit-Queue: Yu Zhao <yuzhao@chromium.org>
Tested-by: Yu Zhao <yuzhao@chromium.org>
Trybot-Ready: Yu Zhao <yuzhao@chromium.org>
Reviewed-by: Guenter Roeck <groeck@chromium.org>
Reviewed-by: Justin TerAvest <teravest@chromium.org>

[modify] https://crrev.com/75ca529116159ad16ad7c6164331f9e5a8033d8b/drivers/regulator/core.c

Project Member

Comment 2 by bugdroid1@chromium.org, Sep 21

Labels: merge-merged-chromeos-4.14
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7b5ca9444f07b32cbcfaae121ff7ecd40d161f88

commit 7b5ca9444f07b32cbcfaae121ff7ecd40d161f88
Author: Yu Zhao <yuzhao@google.com>
Date: Fri Sep 21 02:03:44 2018

FROMGIT: regulator: fix crash caused by null driver data

dev_set_drvdata() needs to be called before device_register()
exposes device to userspace. Otherwise kernel crashes after it
gets null pointer from dev_get_drvdata() when userspace tries
to access sysfs entries.

[Removed backtrace for length -- broonie]

Signed-off-by: Yu Zhao <yuzhao@google.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Cc: stable@vger.kernel.org
(cherry picked from commit fb6de923ca3358a91525552b4907d4cb38730bdd
 git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git)

BUG= chromium:887142 
TEST=Built with KASAN and booted 10x without seeing any problem.

Change-Id: Ie793a52a228c9b1d97a9b13501aad3586d2dda06
Reviewed-on: https://chromium-review.googlesource.com/1237082
Commit-Queue: Yu Zhao <yuzhao@chromium.org>
Tested-by: Yu Zhao <yuzhao@chromium.org>
Trybot-Ready: Yu Zhao <yuzhao@chromium.org>
Reviewed-by: Guenter Roeck <groeck@chromium.org>
Reviewed-by: Justin TerAvest <teravest@chromium.org>

[modify] https://crrev.com/7b5ca9444f07b32cbcfaae121ff7ecd40d161f88/drivers/regulator/core.c

Status: Fixed (was: Started)
Not planning on backporting the patch to kernel versions older than 4.4. Marking the bug fix.

Sign in to add a comment