public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Schmidt <list.lkml@jan-o-sch.net>
To: Kay Sievers <kay@vrfy.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: /proc/kmsg giving eof on blocking read
Date: Thu, 22 Nov 2012 14:20:46 +0100	[thread overview]
Message-ID: <50AE26AE.20704@jan-o-sch.net> (raw)
In-Reply-To: <CAPXgP13OyV-hT=D_-rOyuk2_4n1deQ57ZdRvooBS5Z=sHM_HuQ@mail.gmail.com>

On Thu, November 22, 2012 at 13:29 (+0100), Kay Sievers wrote:
> On Thu, Nov 22, 2012 at 11:44 AM, Jan Schmidt <list.lkml@jan-o-sch.net> wrote:
>> I'm currently debugging something in btrfs in good old printk style, generating
>> around 10MB/min. I'm seeing /proc/kmsg returning eof on a blocking read (and,
>> side note, syslog-ng won't reopen it, effectively stopping logging kernel
>> messages silently).
> 
> Are you sure there is not something else that opens the same file?

Those errors didn't happen on that machine ever before, and there should have
been no user land changes to it for quite a long time.

I'm tempted to say there is no other kmsg reader, but just to make it entirely
sure, how would I trace this? From a quick look at ftrace I don't see it would
output file names when tracing sys_open, unfortunately.

Thanks!
-Jan

      reply	other threads:[~2012-11-22 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 10:44 /proc/kmsg giving eof on blocking read Jan Schmidt
2012-11-22 12:29 ` Kay Sievers
2012-11-22 13:20   ` Jan Schmidt [this message]

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=50AE26AE.20704@jan-o-sch.net \
    --to=list.lkml@jan-o-sch.net \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox