[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1292978635.8743.96.camel@yhuang-dev>
Date: Wed, 22 Dec 2010 08:43:55 +0800
From: Huang Ying <ying.huang@...el.com>
To: David Howells <dhowells@...hat.com>
Cc: "Luck, Tony" <tony.luck@...el.com>, Borislav Petkov <bp@...en8.de>,
Tony Luck <tony.luck@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...e.hu" <mingo@...e.hu>, "greg@...ah.com" <greg@...ah.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Jim Keniston <jkenisto@...ux.vnet.ibm.com>,
Kyungmin Park <kmpark@...radead.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [concept & "good taste" review] persistent store
On Wed, 2010-12-22 at 08:32 +0800, David Howells wrote:
> Huang Ying <ying.huang@...el.com> wrote:
>
> > The user space program (syslogd) is in my big picture, it will guarantee
> > an oops meesage actually go to disk via something like fsync. After
> > doing that, the user space program can erase the corresponding record in
> > persistent storage to free the space. So all in all, oops messages not
> > causing system panic or disk error will go to disk eventually and being
> > freed and will not use up the persistent storage.
>
> I see. So you rely on fsync() to hang forever if the message can't be written
> to disk because an oops killed the write path?
Yes. Or fsync() report error.
Best Regards,
Huang Ying
--
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