Vivek Goyal <[email protected]> writes:
>> Bernhard's idea (kdump uses panic_notifier) is very good for me. But it isn't
>> good for kdump user, because they want to take a dump ASAP when panicked.
>>
>
> This one is better than registering kdump as one of the users of a
> panic_notifier() list.
>
> I think if there are any crash specific actions, they should be taken care
> in next kernel while it is booting.
>
> If something is really very time critical, and has to be done immediately
> after panic (I am not sure how can one ensure that given the fact any number
> of users can register on panic_notifier_list and you are not sure about your
> order in the list and when one will get the control), then probably that
> piece of code should be in kernel and called before crash_kexec().
>
> What is that specific piece of action which you can't do in second kernel?
>
> Eric, do you have any thoughts on this. I think these guys are referring
> to failover problem where immediately after panic() they want to send
> message to other node.
My thoughts are roughly the same as they were last time this was suggested.
I think adding a notifier to the kexec on panic path is a bad idea.
This functionality sounds wrong, because it makes it hard to ensure
reliability of the kexec on panic code path. We are still doing to
much on it as it stands. The working assumption on that code path
needs to be the kernel is broken. Anything else is just asking for
trouble.
Currently we do have a hook in place for code to be called. It is called
the purgatory section of /sbin/kexec. And it's user space so you can
do whatever you want there. Or you can wait until the second kernel
gets more fully booted.
If we really need to do something in the kernel we can patch the kernel
to make a function call from crash_kexec. We don't need any notifiers
to do this.
A further problem with notifiers is they mess up the state we would
like to debug. Which again makes them a problem.
So at least until a specific case is made for a specific piece of code
to get in I am totally opposed to the idea.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
