Linux EDAC development
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Shiju Jose <shiju.jose@huawei.com>
Cc: <linux-edac@vger.kernel.org>, <linuxarm@huawei.com>,
	<tanxiaofei@huawei.com>
Subject: Re: [PATCH 3/3] rasdaemon: ras-mc-ctl: Add exception handling
Date: Wed, 23 Dec 2020 11:03:36 +0100	[thread overview]
Message-ID: <20201223110336.3c14233c@coco.lan> (raw)
In-Reply-To: <20201103142258.1253-4-shiju.jose@huawei.com>

Em Tue, 3 Nov 2020 14:22:58 +0000
Shiju Jose <shiju.jose@huawei.com> escreveu:

> Add exception handling in the ras-mc-ctl.
> 
> For example, when an event's table is not present in the SQLite DB,
> then the DBI would detect exception and ras-mc-ctl exit without
> read and log remaining event's information. This would happen
> when an event is not enabled in the rasdaemon. Following is the
> error log when the devlink_event table is not present in the DB,
> "DBD::SQLite::db prepare failed: no such table: devlink_event at ./ras-mc-ctl line 1198.
> Can't call method "execute" on an undefined value at ./ras-mc-ctl line 1199"
> 
> Also disabled the DBI's automatic error logging by setting
> the $dbh->{PrintError} = 0 to avoid duplicate exception logs.

Hmm...


	$ ./util/ras-mc-ctl --summary
	No Memory errors.
	
	No PCIe AER errors.

	No ARM processor errors.
	
	No Extlog errors.
	
	No devlink errors.
	No disk errors.
	Exception: no such table: memory_failure_event

	No MCE errors.

While it sounds a good idea to catch such events, printing it as an
exception doesn't seem the right thing to me, at least for things 
like "no such table".

IMO, it should print something more intuitive, like:

	"Warning: Memory failure detection not enabled"

-

Yet, on a separate note, there's no memory_failure_event upstream.

Maybe I missed some prior patch to be applied before this one?


Thanks,
Mauro

  reply	other threads:[~2020-12-23 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 14:22 [PATCH 0/3] rasdaemon: ras-mc-ctl: Add exception handling and support memory_failure_event Shiju Jose
2020-11-03 14:22 ` [PATCH 1/3] rasdaemon: ras-mc-ctl: Modify ARM processor error summary log Shiju Jose
2020-11-03 14:22 ` [PATCH 2/3] rasdaemon: ras-mc-ctl: Add memory failure events Shiju Jose
2020-11-03 14:22 ` [PATCH 3/3] rasdaemon: ras-mc-ctl: Add exception handling Shiju Jose
2020-12-23 10:03   ` Mauro Carvalho Chehab [this message]
2021-01-04  9:35     ` Shiju Jose
2021-01-12 18:06       ` Shiju Jose

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=20201223110336.3c14233c@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=shiju.jose@huawei.com \
    --cc=tanxiaofei@huawei.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