[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1244186723.11597.111.camel@localhost.localdomain>
Date: Fri, 05 Jun 2009 03:25:22 -0400
From: Jon Masters <jonathan@...masters.org>
To: Kay Sievers <kay.sievers@...y.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Denis Karpov <ext-denis.2.karpov@...ia.com>, axboe@...nel.dk,
hirofumi@...l.parknet.co.jp, linux-ext4@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
adrian.hunter@...ia.com, artem.bityutskiy@...ia.com
Subject: Re: [PATCH 0/4] FS: userspace notification of errors
On Thu, 2009-06-04 at 14:53 +0200, Kay Sievers wrote:
> On Wed, Jun 3, 2009 at 20:56, Andrew Morton <akpm@...ux-foundation.org> wrote:
> > On Wed, 3 Jun 2009 18:05:14 +0300 Denis Karpov <ext-denis.2.karpov@...ia.com> wrote:
>
> > hm, I'm uncertain on the desirability or otherwise of the
> > overall feature.
I think the idea is a good one. It allows a distribution to take more
proactive measures before services just start dying randomly later. I
could see this nicely wrapped up with some kind of GUI dialog presented
to the desktop user announcing impending doom, too.
> Uevents should not be used for error reporting
Not as currently implemented - but I think the idea of having kernel
events for this kind of thing isn't a bad one, nor is the idea of
listening on a netlink socket for news about them rather than writing
library code to poll whatever procfs file and parse its content.
Jon.
--
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/
Powered by blists - more mailing lists