All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: dhowells@redhat.com, "Luck, Tony" <tony.luck@intel.com>,
	Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"greg@kroah.com" <greg@kroah.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	Kyungmin Park <kmpark@infradead.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [concept & "good taste" review] persistent store
Date: Wed, 22 Dec 2010 00:32:24 +0000	[thread overview]
Message-ID: <8362.1292977944@redhat.com> (raw)
In-Reply-To: <1292977616.8743.87.camel@yhuang-dev>

Huang Ying <ying.huang@intel.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?

David

WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: dhowells@redhat.com, "Luck, Tony" <tony.luck@intel.com>,
	Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"greg@kroah.com" <greg@kroah.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	Kyungmin Park <kmpark@infradead.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [concept & "good taste" review] persistent store
Date: Wed, 22 Dec 2010 00:32:24 +0000	[thread overview]
Message-ID: <8362.1292977944@redhat.com> (raw)
In-Reply-To: <1292977616.8743.87.camel@yhuang-dev>

Huang Ying <ying.huang@intel.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?

David

  parent reply	other threads:[~2010-12-22  0:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 18:16 [concept & "good taste" review] persistent store Luck, Tony
2010-12-17  1:57 ` Linus Torvalds
2010-12-17  6:28   ` Tony Luck
2010-12-17 18:09     ` Tony Luck
2010-12-17 18:19       ` James Bottomley
2010-12-17 21:38       ` Linus Torvalds
2010-12-17 23:08         ` Tony Luck
2010-12-17 23:11           ` H. Peter Anvin
2010-12-17 23:53             ` Tony Luck
2010-12-18 18:23               ` Linus Torvalds
2010-12-18 23:06                 ` Tony Luck
2010-12-19  9:17                   ` Borislav Petkov
2010-12-19 17:01                     ` Florian Mickler
2010-12-19 20:17                     ` Tony Luck
2010-12-19 20:17                       ` Tony Luck
2010-12-20  2:47                       ` Huang Ying
2010-12-20 17:19                         ` Tony Luck
2010-12-21  0:48                           ` Huang Ying
2010-12-21  5:13                             ` Tony Luck
2010-12-21  7:42                               ` Borislav Petkov
2010-12-20  7:26                       ` Borislav Petkov
2010-12-20 17:18                         ` Linus Torvalds
2010-12-20 17:18                           ` Linus Torvalds
2010-12-20 18:58                           ` Borislav Petkov
2010-12-20 21:09                             ` Tony Luck
2010-12-20 21:09                               ` Tony Luck
2010-12-20 10:46                       ` David Howells
2010-12-21  0:41                         ` Huang Ying
2010-12-21 10:10                         ` David Howells
2010-12-22  0:26                           ` Huang Ying
2010-12-22  0:53                             ` david
2010-12-22  7:34                               ` Tony Luck
2010-12-22  0:32                           ` David Howells [this message]
2010-12-22  0:32                             ` David Howells
2010-12-22  0:43                             ` Huang Ying
2010-12-20 10:49                     ` David Howells
2010-12-20 16:52                       ` Tony Luck

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=8362.1292977944@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bp@alien8.de \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=kmpark@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@gmail.com \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.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.