From: Suzuki Kp <suzuki@in.ibm.com>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
andmike@us.ibm.com
Subject: Re: [RFC] PATCH to fix rescan_partitions to return errors properly
Date: Wed, 04 Oct 2006 10:37:49 -0700 [thread overview]
Message-ID: <4523F16D.5060808@in.ibm.com> (raw)
In-Reply-To: <20061004170827.GE18800@harddisk-recovery.nl>
Erik Mouw wrote:
> On Wed, Oct 04, 2006 at 09:50:51AM -0700, Suzuki Kp wrote:
>
>>Erik Mouw wrote:
>>
>>>On Tue, Oct 03, 2006 at 06:00:36PM -0700, Suzuki Kp wrote:
>>>
>>>
>>>>Currently the rescan_partition returns 0 (success), even if it is unable
>>>>to rescan the partition information ( may be due to disks offline, I/O
>>>>error reading the table or unknown partition ). This would make ioctl()
>>>>calls succeed for BLKRRPART requests even if partitions were not scanned
>>>>properly, which is not a good thing to do.
>>>>
>>>>Attached here is patch to fix the issue. The patch makes
>>>>rescan_partition to return -EINVAL for unknown partitions and -EIO for
>>>>disk I/O errors ( or when disks are offline ).
>>>
>>>I don't think it's a good idea to return an error when there's an
>>>unknown partition table. How do you differentiate between a device that
>>>isn't partitioned at all and a device with an unknown partition table?
>>
>>Returning -EINVAL in both the above cases would inform the user that,
>>the partition table was not read properly due to an invalid arguemnt
>>(the disk) passed, which holds good for both the above cases.
>>
>>What do you think ?
>
>
> 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.
Erik,
Thank you very much for the clarification.
But don't you think that, we should let know the user that he/she is
trying to re-read a partition table from a device, which doesn't have it
or is not useful for the kernel or to him, rather than making him happy
with a success ?
>
> It's OK to tell the user that there was some kind of device error when
> scanning the partition table but IMHO an unpartitioned disk is not a
> device error.
>
>
> Erik
>
Thanks,
Suzuki
next prev parent reply other threads:[~2006-10-04 17:42 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 [this message]
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
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=4523F16D.5060808@in.ibm.com \
--to=suzuki@in.ibm.com \
--cc=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 \
/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