Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Feb 2015 17:38:29 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        John Baldwin <jhb@FreeBSD.org>
Cc:        svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Rui Paulo <rpaulo@freebsd.org>
Subject:   Re: svn commit: r278479 - in head: etc sys/kern
Message-ID:  <F4F46967-BD88-41E3-9140-2DF83AF809F4@bsdimp.com>
In-Reply-To: <1516483.e0EXgdk9ur@ralph.baldwin.cx>
References:  <201502092313.t19NDpoS083043@svn.freebsd.org> <1516483.e0EXgdk9ur@ralph.baldwin.cx>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_C4BCE6EA-6C89-4D7F-8249-5F997F17975B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

[[ I know I=E2=80=99m a little behind=E2=80=A6 ]]

> On Feb 10, 2015, at 7:16 AM, John Baldwin <jhb@FreeBSD.org> wrote:
>=20
> On Monday, February 09, 2015 11:13:51 PM Rui Paulo wrote:
>> Author: rpaulo
>> Date: Mon Feb  9 23:13:50 2015
>> New Revision: 278479
>> URL: https://svnweb.freebsd.org/changeset/base/278479
>>=20
>> Log:
>>  Notify devd(8) when a process crashed.
>>=20
>>  This change implements a notification (via devctl) to userland when
>>  the kernel produces coredumps after a process has crashed.
>>  devd can then run a specific command to produce a human readable =
crash
>>  report.  The command is most usually a helper that runs gdb/lldb
>>  commands on the file/coredump pair.  It's possible to use this
>>  functionality for implementing automatic generation of crash =
reports.
>>=20
>>  devd(8) will be notified of the full path of the binary that crashed =
and
>>  the full path of the coredump file.
>=20
> I think this is a very useful feature and I think this is fine to be =
in the
> tree as-is for now.  My only note is that this is a bit of feature =
creep for
> devd (this isn't a device notification, this is a system event =
notification).

devd was always envisioned as being a system event notification thing.
It just started out life doing newbus events. It=E2=80=99s been growing =
these sorts
of notifications for quite some time.

> As such, I think it might be worth thinking if we (collectively) want =
to think
> about having a separate framework at all for system event =
notification.  You
> could possibly publish other interesting events this way.  For =
example, Isilon
> currently has a patch to log(9) Witness LORs.  I personally think it's =
a bit
> hackish and potentially unreliable.  A much nicer interface if you =
want to
> capture such things would be to publish an event for each logged LOR =
instead.
> Machine checks are another example of something that might be nice to =
publish
> (though you could possibly make the case that those would not be =
inappropriate
> to publish via devd since actual hardware is involved).  Disk and PCI =
errors
> are another class of thing that it would be nice to publish in an =
easier to
> programmaticaly parse manner.

I=E2=80=99d love to see this.

Though it might mean we=E2=80=99d need to implement some kind of =
filtering
for the redistribution port that devd has.

Warner

--Apple-Mail=_C4BCE6EA-6C89-4D7F-8249-5F997F17975B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJU8Q4FAAoJEGwc0Sh9sBEAypQP/iIz2IzrE2dSYGarwpW3Ge4E
mSOnlV6GcGPZ6azV8ZbcTwmVn6NxMOCN8xeJ1jwrk92Ol9WdSFtkmkq8htK6mcez
+6gESABhKe5j2G/dkNB5PZLnX26PjVs3A784zi9bFl0aLXpYI9wCnGzcEw20Fo6G
+KbcpFqKeTaU3bgtGKHgYSeQ1A6cB/CDrpWoEa5yNx3yCAqLkBlk3FTzm9QYpQZ9
rsAKf1RV3LKdGSJ7R+Qa2rqN9mlF2mInT4Avh/uuA4OjsXc8Nvz642yk22JWbAmn
Ykue70e6fDnI7VW4Ll9mbWP7n1f9BEMgomQNc0HLEWbi9w4dm2lPkKRDMWljULX8
zBE4eNeiZNcn8s6rgarARL6yCXYlg5SbdCTtj1ttiLENB4a1ofLlRv5FYTxUP1qQ
t4SPaghxkKHKr4fer9JIRsllrCzUE9gUSmEJ1K7gsuPfey9+4M6woPRzG1vCtbkq
hnweLPe3HXUtIgW+dPPlyTTRdCxIJ/vBJt5W8ylVT+jemh/8g543MMoeERlDksok
MvpsTvM4qLnS6FoUastGQNlwJRKLuoKslLCspVPaakAgt1zGoPmZDWnGIpbNtrWL
PYP0NvrevS1Ms0AUNBaJW5exGx0Mkutv0zhW1oE5Z1OLlVufYipRLO8963uXZN2r
SXcmKZ7mBMd4FoErf+dM
=+/rd
-----END PGP SIGNATURE-----

--Apple-Mail=_C4BCE6EA-6C89-4D7F-8249-5F997F17975B--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F4F46967-BD88-41E3-9140-2DF83AF809F4>