lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+8MBb+E462CVOe+5FQb62Tdi5R6cBYgFZUW7sxWDDh2QTaxxA@mail.gmail.com>
Date:	Fri, 22 Jul 2011 16:21:14 -0700
From:	Tony Luck <tony.luck@...el.com>
To:	Don Zickus <dzickus@...hat.com>,
	"Huang, Ying" <ying.huang@...el.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pstore: change mutex locking to spin_locks

On Fri, Jul 22, 2011 at 3:39 PM, Luck, Tony <tony.luck@...el.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ