From: Russell Coker <russell@coker.com.au>
To: Chris PeBenito <pebenito@ieee.org>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH] rasdaemon (replacement for mcelog)
Date: Fri, 18 Feb 2022 11:25:55 +1100 [thread overview]
Message-ID: <18698496.iPHH8zDuP6@xev> (raw)
In-Reply-To: <cd3be651-38de-9998-7dc6-2c6f0f20277e@ieee.org>
On Saturday, 13 March 2021 02:03:48 AEDT Chris PeBenito wrote:
> On 3/8/21 3:59 AM, Dominick Grift wrote:
> > Dominick Grift <dominick.grift@defensec.nl> writes:
> >> Russell Coker <russell@coker.com.au> writes:
> >>> This is policy for rasdaemon, the new replacement for mcelog. The
> >>> /dev/mcelog device is now an obsolete kernel feature that can be enabled
> >>> for backward compatibility and rasdaeon with tracefs is the new way.
> >>>
> >>> I've tested this and it seems to work OK, but all my servers are working
> >>> well so I haven't been able to test the case of actually detecting an
> >>> error. It would be good if someone with a known damaged server could
> >>> give
> >>> it a go.
> >>>
> >>> I think this is ready for merging.
> >>>
> >>> Signed-off-by: Russell Coker <russell@coker.com.au>
>
> [...]
>
> >>> +++ refpolicy-2.20210203/policy/modules/services/rasdaemon.te
> >>> @@ -0,0 +1,49 @@
> >>> +policy_module(rasdaemon, 1.0.0)
> >>> +
> >>> +# rasdaemon is a RAS (Reliability, Availability and Serviceability)
> >>> logging +# tool. It currently records memory errors, using the EDAC
> >>> tracing events. +# EDAC are drivers in the Linux kernel that handle
> >>> detection of ECC errors +# from memory controllers for most chipsets on
> >>> x86 and ARM architectures. +#
> >>> +# https://git.infradead.org/users/mchehab/rasdaemon.git
> >>
> >> Please use the <summary></summary> for description. We have an api
> >> browser (make doc) and the description should end up there as well.
> >>
> >> <summary>Reliability, Availability and Serviceability (RAS) logging
> >> tool.</summary>
> >>
> >> I would omit the url because those are often subject to change anyway.
>
> I agree if we have this amount of description it should go in the XML, but
> the module level actually has a <desc> tag that goes after <summary>. I
> like Dominick's summary, but the Russel's comment can go in the module
> <desc>.
>
> The URL can remain. Yes, it can change, but at least there are some
> breadcrumbs if this program becomes obsolete or unmaintained.
So you mean having the following in rasdaemon.if ?
## <summary>RAS (Reliability, Availability and Serviceability) logging tool</
summary>
##
## <desc>
## rasdaemon is a RAS (Reliability, Availability and Serviceability) logging
## tool. It currently records memory errors, using the EDAC tracing events.
## EDAC are drivers in the Linux kernel that handle detection of ECC errors
## from memory controllers for most chipsets on x86 and ARM architectures.
##
## https://git.infradead.org/users/mchehab/rasdaemon.git
## </desc>
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2022-02-18 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 2:36 [PATCH] rasdaemon (replacement for mcelog) Russell Coker
2021-03-08 8:55 ` Dominick Grift
2021-03-08 8:59 ` Dominick Grift
2021-03-12 15:03 ` Chris PeBenito
2022-02-18 0:25 ` Russell Coker [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=18698496.iPHH8zDuP6@xev \
--to=russell@coker.com.au \
--cc=pebenito@ieee.org \
--cc=selinux-refpolicy@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