Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1408385 > unrolled thread

Re: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [i2c: dev] d6760b14d4:  BUG: KASAN: slab-out-of-bounds in  of_device_uevent at addr ffff8800091b4c49 Wolfram Sang <wsa@the-dreams.de> - 2016-05-28 09:20 +0200
    Re: [i2c: dev] d6760b14d4:  BUG: KASAN: slab-out-of-bounds in  of_device_uevent at addr ffff8800091b4c49 Fengguang Wu <fengguang.wu@intel.com> - 2016-05-28 09:30 +0200
      Re: [i2c: dev] d6760b14d4:  BUG: KASAN: slab-out-of-bounds in  of_device_uevent at addr ffff8800091b4c49 Wolfram Sang <wsa@the-dreams.de> - 2016-05-28 09:40 +0200
        Re: [i2c: dev] d6760b14d4:  BUG: KASAN: slab-out-of-bounds in  of_device_uevent at addr ffff8800091b4c49 Fengguang Wu <fengguang.wu@intel.com> - 2016-05-28 12:20 +0200

#1408385 — Re: [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49

[Multipart message — attachments visible in raw view] — view raw

> 0day kernel testing robot got the below dmesg and the first bad commit is
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

So, I got a success message from buildbot "[wsa:i2c/for-next]
72a71f869c95dc11b73f09fe18c593d4a0618c3f BUILD SUCCESS".

I assume now that the above message covers only compile-testing while
linus master tree also gets boot testing? Correct?

I was under the impression before that the above message also covers
simple boot tests.

Thanks,

   Wolfram

[toc] | [next] | [standalone]

#1408386

On Sat, May 28, 2016 at 09:12:34AM +0200, Wolfram Sang wrote:
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> 
> So, I got a success message from buildbot "[wsa:i2c/for-next]
> 72a71f869c95dc11b73f09fe18c593d4a0618c3f BUILD SUCCESS".
> 
> I assume now that the above message covers only compile-testing while

That's right. "BUILD SUCCESS" only covers compile testing and static
checks.

> linus master tree also gets boot testing? Correct?

All branches will get boot testing. linus/master naturally receives
much more tests since all branches are eventually based on some Linus
commit.

> I was under the impression before that the above message also covers
> simple boot tests.

There will be simple boot tests quickly after the compile tests.
However boot tests typically need more time to be detected, bisected
and especially manual checked. We are yet to automate more boot error
reports.

Thanks,
Fengguang

[toc] | [prev] | [next] | [standalone]

#1408387

[Multipart message — attachments visible in raw view] — view raw

> There will be simple boot tests quickly after the compile tests.
> However boot tests typically need more time to be detected, bisected
> and especially manual checked. We are yet to automate more boot error
> reports.

Thanks for the heads up. Could there be success mails for boot tests,
too?

[toc] | [prev] | [next] | [standalone]

#1408440

On Sat, May 28, 2016 at 09:32:17AM +0200, Wolfram Sang wrote:
> 
> > There will be simple boot tests quickly after the compile tests.
> > However boot tests typically need more time to be detected, bisected
> > and especially manual checked. We are yet to automate more boot error
> > reports.
> 
> Thanks for the heads up. Could there be success mails for boot tests,
> too?

That may be too noisy to be useful. Boot errors may not be well
reproducible, may take different forms, and the base trees are
typically not clean -- even mainline tree has regular errors, for
example, here are the runtime error ids in kernel v4.6 with kconfig
x86_64-rhel:

boot_successes: 1470
boot_failures: 154
BUG:sleeping_function_called_from_invalid_context_at_kernel/irq/manage.c: 102
WARNING:at_drivers/gpu/drm/i915/intel_display.c:#intel_modeset_init[i915]: 4
drm:fw_domains_get[i915]]: 57
drm:__gen6_gt_wait_for_thread_c0[i915]]: 57
BUG:kernel_test_crashed: 4
invoked_oom-killer:gfp_mask=0x: 22
Mem-Info: 22
Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes: 18
invalid_opcode:#[##]SMP: 3
RIP:ftrace_stub: 16
Kernel_panic-not_syncing:Fatal_exception: 16
BUG:unable_to_handle_kernel: 13
Oops: 13
Out_of_memory:Kill_process: 4

However if you are still interested, we can try composing auto runtime
test report emails.

Thanks,
Fengguang

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web