From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <gregkh@suse.de>
Cc: Tim Bird <tim.bird@am.sony.com>,
linux-embedded <linux-embedded@vger.kernel.org>,
linux kernel <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, john stultz <johnstul@us.ibm.com>,
Brian Swetland <swetland@google.com>,
Lennart Poettering <lennart@poettering.net>
Subject: Re: RFC: android logger feedback request
Date: Thu, 22 Dec 2011 03:34:16 +0100 [thread overview]
Message-ID: <CAPXgP120iT_MiUgP96nqXtTHbNut7852f+4FKLYVZXVLZGJBug@mail.gmail.com> (raw)
In-Reply-To: <20111222014718.GA13085@suse.de>
On Thu, Dec 22, 2011 at 02:47, Greg KH <gregkh@suse.de> wrote:
> On Wed, Dec 21, 2011 at 05:32:36PM -0800, Tim Bird wrote:
>> On 12/21/2011 04:51 PM, Greg KH wrote:
>> > On Wed, Dec 21, 2011 at 04:36:21PM -0800, Tim Bird wrote:
>> >> On 12/21/2011 03:19 PM, Greg KH wrote:
>>
>> > Huh, I'm not talking about syslogd, I'm talking about the syslog(2)
>> > syscall we have.
>>
>> OK - switching gears. Â Since the kernel log buffer isn't normally
>> used to store use-space messages, I thought you were referring
>> to syslog(3) and the associated (logger(1) and syslogd(8)).
>
> The kernel log buffer has been storing userspace messages for a while
> now, look at your boot log on the latest Fedora and openSUSE releases
> (or any other distro using systemd for booting).
Right, and the kernel's printk buffer support numbered facilities,
like the syslog protocol defines, just fine.
Stuff injected into the kernel from userspace can easily distinguished
from kernel generated messages when pulled out by userspace.
We use that currently to do early boot logging, when no syslog is running:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=9d90c8d9cde929cbc575098e825d7c29d9f45054
Kay
next prev parent reply other threads:[~2011-12-22 2:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 22:59 RFC: android logger feedback request Tim Bird
2011-12-21 23:19 ` Greg KH
2011-12-22 0:18 ` john stultz
2011-12-22 0:27 ` Greg KH
2011-12-22 0:47 ` john stultz
2011-12-22 1:09 ` john stultz
2011-12-22 0:42 ` Tim Bird
2011-12-22 0:49 ` john stultz
2011-12-22 1:00 ` john stultz
2011-12-22 0:36 ` Tim Bird
2011-12-22 0:51 ` Greg KH
2011-12-22 1:32 ` Tim Bird
2011-12-22 1:47 ` Greg KH
2011-12-22 2:12 ` Tim Bird
2011-12-22 3:44 ` Kay Sievers
2011-12-22 3:45 ` Greg KH
2011-12-22 3:47 ` Greg KH
2011-12-22 4:12 ` Kay Sievers
2011-12-22 4:22 ` Brian Swetland
2011-12-22 4:43 ` Kay Sievers
2011-12-22 4:47 ` david
2011-12-22 4:58 ` Brian Swetland
2011-12-22 5:07 ` david
2011-12-22 5:21 ` david
2011-12-22 13:40 ` Lennart Poettering
2011-12-22 4:49 ` david
2011-12-22 2:34 ` Kay Sievers [this message]
2011-12-22 1:20 ` NeilBrown
2011-12-22 1:49 ` Greg KH
2011-12-22 2:14 ` Tim Bird
2011-12-22 2:34 ` Brian Swetland
2011-12-22 3:49 ` Greg KH
2011-12-22 4:36 ` Kay Sievers
2011-12-22 5:01 ` david
2011-12-22 4:52 ` david
2011-12-22 5:06 ` Brian Swetland
2011-12-22 5:14 ` david
2011-12-22 5:25 ` Brian Swetland
2011-12-22 6:09 ` Greg KH
2011-12-23 15:22 ` Alan Cox
2011-12-23 16:29 ` Greg KH
2011-12-22 7:05 ` NeilBrown
2012-01-06 20:56 ` Tim Bird
2012-01-06 21:20 ` Greg KH
2012-01-06 22:41 ` Tim Bird
2012-01-06 23:17 ` Greg KH
2012-01-06 23:35 ` Greg KH
2011-12-22 14:59 ` Arnd Bergmann
2011-12-22 15:13 ` Kay Sievers
2011-12-22 4:42 ` david
2011-12-22 0:59 ` David Brown
2011-12-29 0:39 ` Andrew Morton
2012-01-04 15:34 ` Geunsik Lim
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=CAPXgP120iT_MiUgP96nqXtTHbNut7852f+4FKLYVZXVLZGJBug@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=arnd@arndb.de \
--cc=gregkh@suse.de \
--cc=johnstul@us.ibm.com \
--cc=lennart@poettering.net \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
--cc=tim.bird@am.sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).