[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1259576847.19465.376.camel@macbook.infradead.org>
Date: Mon, 30 Nov 2009 10:27:27 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: dedekind1@...il.com
Cc: Jörn Engel <joern@...fs.org>,
Simon Kagstrom <simon.kagstrom@...insight.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-mtd <linux-mtd@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>,
"Koskinen Aaro (Nokia-D/Helsinki)" <aaro.koskinen@...ia.com>,
Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH/RFC v5 4/5]: core: Add dump device to call on oopses
and panics
On Mon, 2009-11-30 at 10:23 +0000, David Woodhouse wrote:
> + /* Theoretically, the log could move on after we do this, but
> + there's not a log we can do about that. The new messages
> + will overwrite the start of what we dump. */
> + spin_lock_irqsave(&logbuf_lock, flags);
> + end = log_end & LOG_BUF_MASK;
> + chars = logged_chars;
> + spin_unlock_irqrestore(&logbuf_lock, flags);
Actually that's not true -- we _could_ hold the logbuf_lock until the
end of the function. Not entirely sure we _want_ to though...
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@...el.com Intel Corporation
--
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