All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Luck <tony.luck@intel.com>
To: Don Zickus <dzickus@redhat.com>, "Huang, Ying" <ying.huang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pstore: change mutex locking to spin_locks
Date: Fri, 22 Jul 2011 16:21:14 -0700	[thread overview]
Message-ID: <CA+8MBb+E462CVOe+5FQb62Tdi5R6cBYgFZUW7sxWDDh2QTaxxA@mail.gmail.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D5301E9FA0EE5@orsmsx505.amr.corp.intel.com>

On Fri, Jul 22, 2011 at 3:39 PM, Luck, Tony <tony.luck@intel.com> wrote:
> Yup - oops is the only one where the current kernel continues - all the
> others (halt, reboot, kexec, panic) lead to the termination of the
> current kernel - and thus no user processes that would be able to
> see the shiny new entry in the pstore file system.

Doh - I went to look at what it would take to fix this - and found that
I'd already implemented it:


                if (reason == KMSG_DUMP_OOPS && pstore_is_mounted())
                        pstore_mkfile(PSTORE_TYPE_DMESG, psinfo->name, id,
                                      psinfo->buf, hsize + l1_cpy + l2_cpy,
                                      CURRENT_TIME, psinfo);

-Tony

  reply	other threads:[~2011-07-22 23:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 20:56 [PATCH] pstore: change mutex locking to spin_locks Don Zickus
2011-07-21  0:40 ` Huang Ying
2011-07-21 12:27   ` Don Zickus
2011-07-21 17:57     ` Luck, Tony
2011-07-22  0:33       ` Huang Ying
2011-07-22 12:13         ` Don Zickus
2011-07-22 13:03           ` huang ying
2011-07-22 22:39           ` Luck, Tony
2011-07-22 23:21             ` Tony Luck [this message]
2011-07-25 12:47               ` Don Zickus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+8MBb+E462CVOe+5FQb62Tdi5R6cBYgFZUW7sxWDDh2QTaxxA@mail.gmail.com \
    --to=tony.luck@intel.com \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.