linux-kernel - Re: panic with tg_shares

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b040c32a0812231546s70cf651la19aec03fb9a308c@mail.gmail.com>
Date:	Tue, 23 Dec 2008 15:46:34 -0800
From:	Ken Chen <kenchen@...gle.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: panic with tg_shares_up again?

On Tue, Dec 23, 2008 at 1:36 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> * Yinghai Lu <yinghai@...nel.org> wrote:
>
>> yesterday's tip on one 32 cores sytem
>
> Does reverting this:
>
> | commit d71f5a7c8bf9cd7c74159a53e522e363f2eddaf5
> | Author: Ken Chen <kenchen@...gle.com>
> | Date:   Fri Dec 19 10:11:50 2008 -0800
> |
> |     sched: fix uneven per-cpu task_group share distribution
>
> solve the crash?
>
>>
>> [   22.048032] calling  hpet_late_init+0x0/0x19c @ 1
>> [   22.052037] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31
>> [   22.057035] hpet0: 3 comparators, 32-bit 25.000000 MHz counter
>> [   22.068047] divide error: 0000 [#1] SMP
>> [   22.071994] last sysfs file:
>> [   22.072030] CPU 8
>> [   22.072030] Modules linked in:
>> [   22.072030] Pid: 0, comm: swapper Not tainted
>> 2.6.28-rc8-tip-01347-gab88ef6-dirty #327
>> [   22.072030] RIP: 0010:[<ffffffff8025066e>]  [<ffffffff8025066e>]
>> tg_shares_up+0x100/0x1d1
>> [   22.072030] RSP: 0018:ffff882024a87d48  EFLAGS: 00010246
>> [   22.072030] RAX: 0000000000618800 RBX: ffff880028081680 RCX: ffff88084421d680
>> [   22.072030] RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000000
>> [   22.072030] RBP: ffff882024a87db8 R08: 0000000000000080 R09: ffff88104441e460
>> [   22.072030] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff81117da0
>> [   22.072030] R13: 0000000000000040 R14: 0000000000000004 R15: 0000000000000800
>> [   22.072030] FS:  0000000000000000(0000) GS:ffff881824da7980(0000)
>> knlGS:0000000000000000
>> [   22.072030] CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
>> [   22.072030] CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006e0
>> [   22.072030] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> [   22.072030] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> [   22.072030] Process swapper (pid: 0, threadinfo ffff88182467c000,
>> task ffff880824af9650)
>> [   22.072030] Stack:
>> [   22.072030]  0000000000000020 ffffffff810ed680 0000000000001000
>> 0000000000000000
>> [   22.072030]  0000000000000000 ffff88104441e460 0000000000000283
>> 00000004810ee000
>> [   22.072030]  0000000000000000 ffffffff81117da0 ffff88104441e360
>> ffffffff8025056e
>> [   22.072030] Call Trace:
>> [   22.072030]  <IRQ> <0> [<ffffffff8025056e>] ? tg_shares_up+0x0/0x1d1
>> [   22.072030]  [<ffffffff8024a9e1>] ? tg_nop+0x0/0x8
>> [   22.072030]  [<ffffffff8024cd78>] walk_tg_tree+0x74/0x8d
>> [   22.072030]  [<ffffffff80254063>] update_shares+0x48/0x4d
>> [   22.072030]  [<ffffffff80254478>] rebalance_domains+0x161/0x53c
>> [   22.072030]  [<ffffffff8025489c>] run_rebalance_domains+0x49/0xe4
>> [   22.072030]  [<ffffffff8026020a>] __do_softirq+0x83/0x145
>> [   22.072030]  [<ffffffff8022a15c>] call_softirq+0x1c/0x28
>> [   22.072030]  [<ffffffff8022b0a0>] do_softirq+0x34/0x76
>> [   22.072030]  [<ffffffff8025ff1b>] irq_exit+0x3f/0x82
>> [   22.072030]  [<ffffffff8023a75d>] smp_apic_timer_interrupt+0x93/0xac
>> [   22.072030]  [<ffffffff80229b73>] apic_timer_interrupt+0x13/0x20
>> [   22.072030]  <EOI> <0>Code: 44 24 08 4a 8b 0c f0 48 85 c9 0f 84 b6
>> 00 00 00 49 8b 44 24 10 4a 8b 04 f0 48 8b 80 a8 00 00 00 48 85 c0 74
>> 10 49 0f af c7 31 d2 <48> f7 75 b0 48 89 45 d0 eb 11 4c 89 f8 31 d2 48
>> c7 45 d0 00 00
>> [   22.072030] RIP  [<ffffffff8025066e>] tg_shares_up+0x100/0x1d1
>> [   22.072030]  RSP <ffff882024a87d48>

Hmm, I had the div operation inside this check:

        if (rq_weight && sd_rq_weight) {
                raw_shares = (sd_shares * rq_weight) / sd_rq_weight;

I disassembled the above oops text, it appears that the check to
sd_rq_weight is missing.

And from my local build of linux-tip with the patch, I have the
following assembly:
     1  ffffffff8023b74f:  48 8b 88 a8 00 00 00    mov    0xa8(%rax),%rcx
     2  ffffffff8023b756:  48 c7 45 d0 00 00 00    movq   $0x0,-0x30(%rbp)
     3  ffffffff8023b75d:  00
     4  ffffffff8023b75e:  48 85 c9                test   %rcx,%rcx
     5  ffffffff8023b761:  0f 95 c0                setne  %al
     6  ffffffff8023b764:  84 45 af                test   %al,-0x51(%rbp)
     7  ffffffff8023b767:  74 15                   je     ffffffff8023b77e
     8  ffffffff8023b769:  48 8b 45 b8             mov    -0x48(%rbp),%rax
     9  ffffffff8023b76d:  31 d2                   xor    %edx,%edx
    10  ffffffff8023b76f:  48 0f af c1             imul   %rcx,%rax
    11  ffffffff8023b773:  48 f7 75 b0             divq   -0x50(%rbp)

line 6 is the compare against sd_rq_weight, but it was only to one
byte instead of the entire unsigned long.

/me scratching my head ....

- Ken
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/