Messages in this thread | | | From | "Luck, Tony" <> | Date | Mon, 17 Oct 2011 09:56:50 -0700 | Subject | RE: [RFC][PATCH -next] make pstore/kmsg_dump run after stopping other cpus in panic path |
| |
> All this lock busting probably isn't pretty and causes one to reflect what > is going on here. But as long as we are going to keep the kmsg_dump > design, changes like this seem necessary to make sure the locking stays > sane(r) for now.
So should we let the back-end know that locks have been busted? I worry that we'll get through the pstore layer by blasting away at any locks that get in our way - but then the backend (which may well have been written on the assumption that pstore serialized calls to it) will not do anything useful (and may cause its own hang).
-Tony
| |