Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754242Ab0LVAp0 (ORCPT ); Tue, 21 Dec 2010 19:45:26 -0500 Received: from mga11.intel.com ([192.55.52.93]:45464 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753874Ab0LVApX (ORCPT ); Tue, 21 Dec 2010 19:45:23 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.60,210,1291622400"; d="scan'208";a="639052699" Subject: Re: [concept & "good taste" review] persistent store From: Huang Ying To: David Howells Cc: "Luck, Tony" , Borislav Petkov , Tony Luck , Linus Torvalds , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" , "linux-arch@vger.kernel.org" , "tglx@linutronix.de" , "mingo@elte.hu" , "greg@kroah.com" , "akpm@linux-foundation.org" , David Miller , Alan Cox , Jim Keniston , Kyungmin Park , Geert Uytterhoeven In-Reply-To: <8362.1292977944@redhat.com> References: <1292977616.8743.87.camel@yhuang-dev> <1292892072.8743.70.camel@yhuang-dev> <1292813234.8743.66.camel@yhuang-dev> <4d0662e511688484b3@agluck-desktop.sc.intel.com> <4D0BEE1F.7020008@zytor.com> <20101219091752.GA16150@liondog.tnic> <17027.1292841992@redhat.com> <32058.1292926258@redhat.com> <8362.1292977944@redhat.com> Content-Type: text/plain; charset="UTF-8" Date: Wed, 22 Dec 2010 08:43:55 +0800 Message-ID: <1292978635.8743.96.camel@yhuang-dev> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 973 Lines: 24 On Wed, 2010-12-22 at 08:32 +0800, David Howells wrote: > Huang Ying 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/