linux-kernel - Re: GFS2: Add LED support to GFS2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Jul 2009 16:02:31 +0100
From:	Steven Whitehouse <swhiteho@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	cluster-devel@...hat.com, linux-kernel@...r.kernel.org,
	rpurdie@...ys.net
Subject: Re: GFS2: Add LED support to GFS2

Hi,

On Wed, 2009-07-22 at 16:55 +0200, Andi Kleen wrote:
> > It would be difficult to make that generic since the errors and the
> > resulting actions which can be taken vary from fs to fs. The main reason
> > that I didn't do it at this point in time is that the GFS2 error
> > handling needs revising anyway, and once that is done (probably with an
> > errors= option similar to ext2/3/4) it might be possible to think about
> > LED support for that,
> 
> I was thinking to have a couple of generic functions like:
> 
> log_activity()
> error_happened() 
> 
> ...
> 
> that everyone could call.
> 
> -Andi
> 
> 
Indeed, but we'd need to allow for different classes of activity or
errors, and then filtering them per-LED. With my proposed patch that is
avoided due to having a small number of triggers on the different
events, so selecting the trigger acts as a filter on the event type.

So I guess what I'm really getting at, is what would the user interface
be for this scheme to set up the LEDs?

I did consider adding a feature to filter events on a per superblock
basis, but I decided against it in the end, as it seemed to be making
things too complicated (how should we specify the superblock? what
should the user interface be?).

Maybe there is an easy way to do that which I've not spotted...

Steve.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/