From: Neil Horman <nhorman@tuxdriver.com>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>, Ingo Molnar <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>,
Roland McGrath <roland@redhat.com>,
Jason Baron <jbaron@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [PATCH -tip v5] tracepoint: Add signal coredump tracepoint
Date: Fri, 19 Mar 2010 14:18:00 -0000 [thread overview]
Message-ID: <20100319141825.GA3530@hmsreliant.think-freely.org> (raw)
In-Reply-To: <4BA385CB.9080706@redhat.com>
On Fri, Mar 19, 2010 at 10:10:19AM -0400, Masami Hiramatsu wrote:
> Oleg Nesterov wrote:
> > (add Neil)
> >
> > On 03/19, Masami Hiramatsu wrote:
> >>
> >> void do_coredump(long signr, int exit_code, struct pt_regs *regs)
> >> {
> >> struct core_state core_state;
> >> - char corename[CORENAME_MAX_SIZE + 1];
> >> + char corename[CORENAME_MAX_SIZE + 1] = "";
> >> struct mm_struct *mm = current->mm;
> >> struct linux_binfmt * binfmt;
> >> struct inode * inode;
> >> @@ -1802,6 +1803,7 @@ void do_coredump(long signr, int exit_code, struct pt_regs *regs)
> >> static atomic_t core_dump_count = ATOMIC_INIT(0);
> >> struct coredump_params cprm = {
> >> .signr = signr,
> >> + .file = NULL,
> >> .regs = regs,
> >> .limit = rlimit(RLIMIT_CORE),
> >> /*
> >> @@ -1815,8 +1817,10 @@ void do_coredump(long signr, int exit_code, struct pt_regs *regs)
> >> audit_core_dumps(signr);
> >>
> >> binfmt = mm->binfmt;
> >> - if (!binfmt || !binfmt->core_dump)
> >> + if (!binfmt || !binfmt->core_dump) {
> >> + retval = -ENOSYS;
> >> goto fail;
> >> + }
> >
> > Oh.
> >
> > Masami, may I ask you to delay these changes a bit?
> >
> > This patch conflicts very much with other changes (hopefully in -mm soon)
> > we are doing.
> >
> > If your patch comes first, we have to redo 12 patches. Besides, this patch
> > complicates do_coredump() even more while it really needs the cleanups.
>
> Ah, that's a big conflict :O
> Yes, sure, I can wait for your commits. I'll update this patch on yours.
>
> > Please see
> > http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/96f01d85034ca029/3b6bcb9b2d756dbc
> > I can send you these patches privately if you wish.
>
> OK, I can pick them up from the thread:)
>
> Thank you!
>
Yes, thank you. I think you may find if you put them on top of the changes Oleg
and I have made, you'll find this one will be alot cleaner as well.
Thanks!
Neil
> --
> Masami Hiramatsu
> e-mail: mhiramat@redhat.com
>
prev parent reply other threads:[~2010-03-19 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 13:15 Masami Hiramatsu
2010-03-19 13:35 ` Oleg Nesterov
2010-03-19 14:10 ` Masami Hiramatsu
2010-03-19 14:15 ` Oleg Nesterov
2010-03-19 14:18 ` Neil Horman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100319141825.GA3530@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=dle-develop@lists.sourceforge.net \
--cc=jbaron@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).