linux-kernel - pm/linux-next cause network stop working with qemu-kvm/e1000

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-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQVZ5VZDo1KCun6SDonTJ=TGWLxm5zJQN5U4f1_52cKKwg@mail.gmail.com>
Date:	Fri, 22 Mar 2013 17:27:32 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Bob Moore <robert.moore@...el.com>
Cc:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: pm/linux-next cause network stop working with qemu-kvm/e1000

c13085e519e8984fede41fa3d6a5502523b10996 is the first bad commit
commit c13085e519e8984fede41fa3d6a5502523b10996
Author: Bob Moore <robert.moore@...el.com>
Date:   Fri Mar 8 09:19:38 2013 +0000

    ACPICA: Resource Mgr: Prevent infinite loops in resource walks

    Add checks for zero-length resource descriptors in all code that
    loops through a resource descriptor list. This prevents possible
    infinite loops because the length is used to increment the traveral
    pointer and detect the end-of-descriptor.

    Signed-off-by: Bob Moore <robert.moore@...el.com>
    Signed-off-by: Lv Zheng <lv.zheng@...el.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>

:040000 040000 84f29d6ee654ffe4c935ce9023208019b2ef09a5
c8a6613be9a5a130f69e654c5b560a8adb2174db M	drivers


long delay after
calling  ip_auto_config+0x0/0xea4 @ 1

also happen on one 8 sockets nehalem-ex.

If I revert that commit, network works again.

Thanks

Yinghai
--
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/