Thread (9 messages) flat view 9 messages, 5 authors, 2008-07-21

Re: [PATCH] Don't panic when EEH_MAX_FAILS is exceeded

From: "Linas Vepstas" <linasvepstas@gmail.com>
Date: 2008-07-20 23:19:38

2008/7/20 Nathan Lynch [off-list ref]:
Mike Mason wrote:
quoted
This patch changes the EEH_MAX_FAILS action from panic to printing
an error message.  Panicking under under this condition is too
harsh.
quoted
                      /* re-read the slot reset state */
                      if (read_slot_reset_state(pdn, rets) != 0)
                              rets[0] = -1;   /* reset state unknown */
While I tend to agree that panic() is unnecessary, don't we want a
stack dump unconditionally (i.e. not bracketed in #ifdef DEBUG)?
Probably. This stack trace would reveal a point inside the
inf loop, which can then be analyzed and fixed.
I'd prefer just removing the code instead of adding #ifdef's in the
middle of this function.  eeh.c needs less #ifdef DEBUG, not more :)
I didn't know that there was a lot of ifdef DEBUG in there.
Yes, we don't need an ifdef DEBUG for this.

Pending these changes, I'd happily add:

Acked-by: Linas Vepstas <linasvepstas@gmail.com>

--linas
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help