All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH blktests] Add use of logger so that syslog files show when each test starts
Date: Mon, 26 Nov 2018 10:37:23 -0800	[thread overview]
Message-ID: <20181126183723.GB30411@vader> (raw)
In-Reply-To: <20181126183211.GA31885@thunk.org>

On Mon, Nov 26, 2018 at 01:32:11PM -0500, Theodore Y. Ts'o wrote:
> On Mon, Nov 26, 2018 at 09:50:57AM -0800, Omar Sandoval wrote:
> > 
> > Hey, Ted, sorry, I meant to ask you about this in person at LPC but
> > forgot to. Forgive my ignorance about syslog, but does syslog not pick
> > up the line we write to dmesg?
> 
> Unfortunately, it does not.
> 
> root@xfstests-ltm:~# echo foo testing >> /dev/kmsg 
> root@xfstests-ltm:~# dmesg | tail
> [    7.103899] random: crng init done
> [    7.104759] random: 7 urandom warning(s) missed due to ratelimiting
> [    7.154525] EDAC MC: Ver: 3.0.0
> [    7.221973] EDAC sbridge: Seeking for: PCI ID 8086:2fa0
> [    7.221977] EDAC sbridge:  Ver: 1.1.1 
> [    7.259154] device-mapper: uevent: version 1.0.3
> [    7.267252] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23) initialised: dm-devel@redhat.com
> [    7.762306] EXT4-fs (sda1): resizing filesystem from 2620928 to 13106683 blocks
> [    8.541258] EXT4-fs (sda1): resized filesystem to 13106683
> [840160.646340] foo testing
> root@xfstests-ltm:~# tail /var/log/kern.log
> root@xfstests-ltm:~# grep kern.log /etc/rsyslog.conf 
> kern.*				-/var/log/kern.log
> 
> So as you can see nothing written to kern.log, even though we wrote to
> /dev/kmsg.
> 
> To prove that kern.log will get kernel messages:
> 
> root@xfstests-ltm:~# mke2fs -t ext4 -Fq /tmp/foo.img 8M
> root@xfstests-ltm:~# mount -t ext4 /tmp/foo.img /mnt
> root@xfstests-ltm:~# echo testing > /sys/fs/ext4/loop0/trigger_fs_error 
> root@xfstests-ltm:~# tail /var/log/kern.log
> Nov 26 13:30:22 xfstests-ltm kernel: [840286.728296] loop: module loaded
> Nov 26 13:30:22 xfstests-ltm kernel: [840286.752181] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
> Nov 26 13:30:41 xfstests-ltm kernel: [840305.773418] EXT4-fs error (device loop0): trigger_test_error:123: comm bash: testing
> root@xfstests-ltm:~# 

Hm, what if we output it as KERN_INFO?

diff --git a/check b/check
index f6c3537..9b4765f 100755
--- a/check
+++ b/check
@@ -314,7 +314,7 @@ _call_test() {
 
 	if [[ -w /dev/kmsg ]]; then
 		local dmesg_marker="run blktests $TEST_NAME at ${TEST_RUN["date"]}"
-		echo "$dmesg_marker" >> /dev/kmsg
+		echo "<6>$dmesg_marker" >> /dev/kmsg
 	else
 		local dmesg_marker=""
 		CHECK_DMESG=0

  reply	other threads:[~2018-11-26 18:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 16:15 [PATCH blktests] Add use of logger so that syslog files show when each test starts Theodore Ts'o
2018-11-23  1:02 ` Theodore Y. Ts'o
2018-11-26 17:50   ` Omar Sandoval
2018-11-26 18:32     ` Theodore Y. Ts'o
2018-11-26 18:37       ` Omar Sandoval [this message]
2018-11-26 19:31         ` Theodore Y. Ts'o
2018-11-26 19:37           ` Omar Sandoval

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=20181126183723.GB30411@vader \
    --to=osandov@osandov.com \
    --cc=linux-block@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.