| 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
| ||
|
Message-ID: <20091114000234.GA24738@elte.hu> Date: Sat, 14 Nov 2009 01:02:34 +0100 From: Ingo Molnar <mingo@...e.hu> To: Roland McGrath <roland@...hat.com> Cc: Masami Hiramatsu <mhiramat@...hat.com>, lkml <linux-kernel@...r.kernel.org>, systemtap <systemtap@...rces.redhat.com>, DLE <dle-develop@...ts.sourceforge.net> Subject: Re: [PATCH -tip 2/3] Add coredump tracepoint * Roland McGrath <roland@...hat.com> wrote: > I can't really see what this has to do with "sched" to warrant that > name. But, whatever. That's a misnomer indeed. I'd suggest to introduce a separate 'signal' subsystem category. > Note that you put the tracepoint where it won't get called in the > various cases where no dump is really being made because of > RLIMIT_CORE or file failures. I suspect you would like to get those > reported. (Perhaps especially so, since there won't be any file > around to notice later.) Yeah, good point. > Also, it seems nice to give the tracepoint the chance to look at the > actual open file in case a fancy one wants to do that. Oh, so SystemTap is the motivator of these tracepoints? Do you know about exact usecases where these tracepoints would be utilized? Would be interesting (and relevant) to list them. Ingo -- 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