netdev - Re: [PATCH 1/1] connector: Added coredumping event to the process connector

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-next>] [day] [month] [year] [list]

Message-ID: <20130316184036.GE24041@order.stressinduktion.org>
Date:	Sat, 16 Mar 2013 19:40:36 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Jesper Derehag <jderehag@...mail.com>
Cc:	Evgeniy Polyakov <zbr@...emap.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH 1/1] connector: Added coredumping event to the process connector

On Sat, Mar 16, 2013 at 05:57:20PM +0000, Jesper Derehag wrote:
> 
> 
> > Date: Sat, 16 Mar 2013 18:03:48 +0100
> > From: hannes@...essinduktion.org
> > To: jderehag@...mail.com
> > CC: zbr@...emap.net; netdev@...r.kernel.org
> > Subject: Re: [PATCH 1/1] connector: Added coredumping event to the process connector
> > 
> > On Sat, Mar 16, 2013 at 11:50:50AM +0100, Jesper Derehag wrote:
> > > +	ev->event_data.exit.exit_code = task->exit_code;
> > > +	ev->event_data.exit.exit_signal = task->exit_signal;
> > 
> > Do these already contain meaningful values?
> > 
> 
> I have to admit that they dont.And you are correct, I should add a new event struct specific for the coredump event instead of piggybacking on the exit struct.Will re-submit a patch..

Hm, I am still unsure if such a patch is needed. Couldn't you test for
coredump by inspecting exit_code on PROC_EVENT_EXIT?

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html