linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Alex Kelly <eshink@gmail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alex Kelly <alex.page.kelly@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] Moved core dump functionality into its own file
Date: Sat, 4 Aug 2012 08:43:04 +0200	[thread overview]
Message-ID: <20120804064304.GA5195@gmail.com> (raw)
In-Reply-To: <1344027800-8270-1-git-send-email-eshink@gmail.com>


* Alex Kelly <eshink@gmail.com> wrote:

> From: Alex Kelly <alex.page.kelly@gmail.com>
> 
> This was done in preparation for making core dump functionality optional.

Please use present tense and a sane title, something like:

  fs: Move core dump functionality into its own file
  fs: Make core dump functionality optional

While looking at that code, there's also a few uglies in it, 
like:

> +	return nr;
> +}
> +
> +
> +/*

> +
> +	/* Repeat as long as we have more pattern to process and more output
> +	   space */

> +}
> +
> +
> +void do_coredump(long signr, int exit_code, struct pt_regs *regs)

> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -413,6 +413,7 @@ static inline void arch_pick_mmap_layout(struct mm_struct *mm) {}
>  
>  extern void set_dumpable(struct mm_struct *mm, int value);
>  extern int get_dumpable(struct mm_struct *mm);
> +extern int __get_dumpable(unsigned long mm_flags);

These prototypes should move out of sched.h and into a 
coredump.h header or so.

If we are touching this code lets use the opportunity and do 
this right.

Note, I'd suggest to put any such further changes into separate, 
additional patches at the end: a cleanup patch, a header file 
introduction patch, etc. - and keep the "dumb code movement" 
chnage in the initial patch. This will make it all much easier 
to review.

Please also review the code for more uglies, the above was just 
a very quick stylistic scan.

Thanks,

	Ingo

  parent reply	other threads:[~2012-08-04  6:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 21:03 [PATCH 1/2] Moved core dump functionality into its own file Alex Kelly
2012-08-03 21:03 ` [PATCH 2/2] Made core dump functionality optional Alex Kelly
2012-08-04  6:43 ` Ingo Molnar [this message]
2012-08-05  8:28 ` [PATCH 1/4] fs: Move core dump functionality into its own file eshink
2012-08-05  8:28   ` [PATCH 2/4] fs: Make core dump functionality optional eshink
2012-08-05  8:28   ` [PATCH 3/4] fs: Clean up some artifacts in coredump.c eshink
2012-08-05  8:28   ` [PATCH 4/4] fs: Update coredump-related headers eshink
2012-08-05 11:18 ` [PATCHv3 1/4] fs: Move core dump functionality into its own file Alex Kelly
2012-08-05 11:18   ` [PATCHv3 2/4] fs: Make core dump functionality optional Alex Kelly
2012-08-05 11:18   ` [PATCHv3 3/4] fs: Clean up some artifacts in coredump.c Alex Kelly
2012-08-05 11:18   ` [PATCHv3 4/4] fs: Update coredump-related headers Alex Kelly
2012-08-05 18:39   ` [NAK] Re: [PATCHv3 1/4] fs: Move core dump functionality into its own file Kees Cook
  -- strict thread matches above, loose matches on Subject: below --
2012-08-01  2:23 [PATCH 1/2] Moved " Alex Kelly
2012-08-01 21:54 ` Andrew Morton
2012-07-03  0:38 Alex Kelly
2012-07-03  4:53 ` Cong Wang
2012-07-13 22:02   ` Andrew Morton

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=20120804064304.GA5195@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex.page.kelly@gmail.com \
    --cc=eshink@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 NNTP newsgroup(s).