linux-kernel - Re: it821x trouble since 2.6.18

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: <20070114232219.3038987e@localhost.localdomain>
Date:	Sun, 14 Jan 2007 23:22:19 +0000
From:	Alan <alan@...rguk.ukuu.org.uk>
To:	Christoph Biedl <linux-kernel.bfrz@...chmal.in-ulm.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: it821x trouble since 2.6.18

> 2. Trying to understand what has happened I found the main difference
> is not in the driver but in ide-dma.c:
> 
> --- linux-2.6.17.14/drivers/ide/ide-dma.c   2006-06-18 01:49:35.000000000 +0000
> +++ linux-2.6.18.6/drivers/ide/ide-dma.c    2006-09-20 03:42:06.000000000 +0000
> @@ -752,7 +750,7 @@
>                         goto bug_dma_off;
>                 printk(", DMA");
>         } else if (id->field_valid & 1) {
> -               printk(", BUG");
> +               goto bug_dma_off;
>         }
>         return;
>  bug_dma_off:
> 
> 
> and reverting that change returns the old transfer rates. But that is
> probably not a good idea.

It should be just fine. 

> So I tried this again:

This is complete bogus. You simply poked random incorrect registers and
happened not to crash the chip, or confuse it, and since you have the
IT821x bios enabled it happened to have roughly valid configuration.

> and disabled CONFIG_BLK_DEV_IT821X - and now the disk is even faster
> than before:

For all the wrong reasons I would add.

-
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/