mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Suzuki Kp <suzuki@in.ibm.com>
Cc: Erik Mouw <erik@harddisk-recovery.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, andmike@us.ibm.com
Subject: Re: [RFC] PATCH to fix rescan_partitions to return errors properly - take 2
Date: Thu, 5 Oct 2006 15:07:29 -0700	[thread overview]
Message-ID: <20061005150729.170e41c4.akpm@osdl.org> (raw)
In-Reply-To: <45256BE2.5040702@in.ibm.com>

On Thu, 05 Oct 2006 13:32:34 -0700
Suzuki Kp <suzuki@in.ibm.com> wrote:

> Erik,
> 
> 
> Erik Mouw wrote:
> > On Wed, Oct 04, 2006 at 10:37:49AM -0700, Suzuki Kp wrote:
> > 
> >>Erik Mouw wrote:
> >>
> >>>I disagree. It's perfectly valid for a disk not to have a partition
> >>>table (for example: components of a RAID5 MD device) and we shouldn't
> >>>scare users about that. Also an unrecognised partition table format
> >>>(DEC VMS, Novell Netware, etc.) is not a reason to throw an error, it's
> >>>just unrecognised and as far as the kernel knows it's unpartioned.
> >>
> 
> [...]
> 
> 
> Thank you very much for the inputs.
> 
> As per the discussion I have made the changes to the patch.
> 
> This change needs to be implemented in some of the partition checkers 
> which doesn't do that already.
> 
> Btw, do you think it is a good idea to let the other partition checkers 
> run, even if one of them has failed ?
> 
> Right now, the check_partition runs the partition checkers in a 
> sequential manner, until it finds a success or an error.

This is all important information to capture in the patch changelog: it
covers user-visible changes, it covers user-affecting problems with the
present kernel, it describes the implications of making this change to the
kernel, etc.  All important stuff.  So could you please send a complete
changelog for this patch?


>
> * Fix rescan_partition to propagate the low level I/O error.
>

Not enough ;)
 
> 
> 
> Signed Off by: Suzuki K P <suzuki@in.ibm.com>
> 

Please use "Signed-off-by:"

This patch had tabs replaced with spaces, despite the fact that it was an
attachment - that's a new one.  Please get that fixed up for future
patches, thanks.


  reply	other threads:[~2006-10-05 22:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04  1:00 [RFC] PATCH to fix rescan_partitions to return errors properly Suzuki Kp
2006-10-04 13:09 ` Erik Mouw
2006-10-04 16:50   ` Suzuki Kp
2006-10-04 17:08     ` Erik Mouw
2006-10-04 17:37       ` Suzuki Kp
2006-10-05 10:40         ` Erik Mouw
2006-10-05 20:32           ` [RFC] PATCH to fix rescan_partitions to return errors properly - take 2 Suzuki Kp
2006-10-05 22:07             ` Andrew Morton [this message]
2006-10-06 12:53             ` Erik Mouw
2006-10-06 17:43               ` Suzuki K P
2006-10-06 21:07                 ` Erik Mouw
2006-10-07  1:46                   ` [RFC] Fix check_partition routines ( was Re: [RFC] PATCH to fix rescan_partitions to return errors properly - take 2) Suzuki K P
2006-10-07  2:45                     ` 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=20061005150729.170e41c4.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=andmike@us.ibm.com \
    --cc=erik@harddisk-recovery.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suzuki@in.ibm.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

Powered by JetHome