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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061006210721.GC31233@harddisk-recovery.nl>
Date:	Fri, 6 Oct 2006 23:07:22 +0200
From:	Erik Mouw <erik@...ddisk-recovery.com>
To:	Suzuki K P <suzuki@...ibm.com>
Cc:	lkml <linux-kernel@...r.kernel.org>, linux-fsdevel@...r.kernel.org,
	Andrew Morton <akpm@...l.org>, andmike@...ibm.com
Subject: Re: [RFC] PATCH to fix rescan_partitions to return errors properly - take 2

On Fri, Oct 06, 2006 at 10:43:42AM -0700, Suzuki K P wrote:
> Erik Mouw wrote:
> >I think it's best not to change the current behaviour and let all
> >partition checkers run, even if one of them failed due to device
> >errors. I wouldn't mind if the behaviour changed like you propose,
> >though.
> >
> At present, the partition checkers doesn't run, if one of the preceeding 
> checker has reported an error ! *But*, some of the checkers doesn't 
> report the I/O error which they came across! So, this may let others 
> run. Thats not we want, right. We would like them to return I/O errors, 
> and and the check_partition should let other partition checkers continue.

Indeed, we want them to behave the same. I.e.: a partition checker
should tell when it encounters an I/O error.


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.nl -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ