linux-kernel - Re: S3 with pata_via fails to resume, ide

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] [day] [month] [year] [list]

Message-ID: <20090102235034.5660b85a@neptune.home>
Date:	Fri, 2 Jan 2009 23:50:34 +0100
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Cc:	linux-ide@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org
Subject: Re: S3 with pata_via fails to resume, ide_via82Cxxx works

On Fri, 02 January 2009 Bartlomiej Zolnierkiewicz wrote:
-snip-
> > 
> > I guess the binfmt-0000 is cause by XFS reading at wrong location
> > on disc and kernel seeing random data as bin format signature.
> > 
> > 
> > On reboot no more bootloader.
> > hexdump with rescue system showed XFS magic in very first sector of
> > the disc, (rescuing the GPT worked - I assume parted used copy at
> > end of disc) though the first partition also got corrupted.
> > 
> > This looks like the scan is pretty dangerous in case anything has a
> > reference to a disc/partition on the scanned channel :(

That's fine with me - eventually it would even be worth adding a
printk() as reminder on code path for "scan" and "delete_devices"
triggered when there exists an active user of the bus/device being
probed.

This way there is at least a notice in case something goes wrong (and
when the locking is fixed a reminder to adjust the documentation)

> I'm really sorry to hear it but "delete_devices" / "scan" interfaces
> are currently not ready for use on actively used devices (there are
> still some locking issues with the core code that need to be
> addressed before this can be allowed).
> 
> Even though HOWTO only mentions use for replacing devices (not
> rescaning) I admit that it should be more clear about the above:
> 
> From: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
> Subject: [PATCH] ide: update warm-plug HOWTO
> 
> Reported-by: Bruno Prémont <bonbons@...ux-vserver.org>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
> ---
>  Documentation/ide/warm-plug-howto.txt |    5 +++++
>  1 file changed, 5 insertions(+)
> 
> Index: b/Documentation/ide/warm-plug-howto.txt
> ===================================================================
> --- a/Documentation/ide/warm-plug-howto.txt
> +++ b/Documentation/ide/warm-plug-howto.txt
> @@ -11,3 +11,8 @@ unplug old device(s) and plug new device
>  # echo -n "1" > /sys/class/ide_port/idex/scan
>  
>  done
> +
> +NOTE: please make sure that partitions are unmounted and that there
> are +no other active references to devices before doing
> "delete_devices" step, +also do not attempt "scan" step on devices
> currently in use -- otherwise +results may be unpredictable and lead
> to data loss if you're unlucky
> 
--
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/