diff options
| author | Stephen Brennan <stephen.s.brennan@oracle.com> | 2022-02-14 17:37:35 -0800 |
|---|---|---|
| committer | Wei Liu <wei.liu@kernel.org> | 2022-02-18 13:09:38 +0000 |
| commit | d57d6fe5bf3463aad1332ecfc7555a6888b04fd9 (patch) | |
| tree | e7fe0e7acafcf85291cff7dfd4355ee6984cb296 /net/dccp/ccid.c | |
| parent | 6de74d1069b821e96460d0fc2edfc35785db04fb (diff) | |
| download | linux-d57d6fe5bf3463aad1332ecfc7555a6888b04fd9.tar.gz linux-d57d6fe5bf3463aad1332ecfc7555a6888b04fd9.tar.bz2 linux-d57d6fe5bf3463aad1332ecfc7555a6888b04fd9.zip | |
drivers: hv: log when enabling crash_kexec_post_notifiers
Recently I went down a rabbit hole looking at a race condition in
panic() on a Hyper-V guest. I assumed, since it was missing from the
command line, that crash_kexec_post_notifiers was disabled. Only after
a rather long reproduction and analysis process did I learn that Hyper-V
actually enables this setting unconditionally.
Users and debuggers alike would like to know when these things happen. I
think it would be good to print a message to the kernel log when this
happens, so that a grep for "crash_kexec_post_notifiers" shows relevant
results.
Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
Reviewed-by: Michael Kelley <mikelley@microsoft.com>
Link: https://lore.kernel.org/r/20220215013735.358327-1-stephen.s.brennan@oracle.com
Signed-off-by: Wei Liu <wei.liu@kernel.org>
Diffstat (limited to 'net/dccp/ccid.c')
0 files changed, 0 insertions, 0 deletions