Re: [Crash-utility] [PATCH] Fix for "bt" command incorrectly printing eframe stack with a bogus warning

Hello, For upstream crash, and this is more a general thought, what about ordering tests with most recent kernel changes being tested first: For example, in Lianbo's case, instead of: - (STREQ(sp->name, "call_softirq") || STREQ(sp->name, "do_softirq_own_stack"))) What about reversing the order of the tests: + (STREQ(sp->name, " do_softirq_own_stack") || STREQ(sp->name, " call_softirq"))) As distros tend to move fast forward, ordering tests with most recent kernel changes being tested first would make sense. Georges