linux-kernel - Re: Off-by-one in both LIBATA and IDE drivers

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]

Date:	Thu, 12 Mar 2009 10:30:48 -0400
From:	Mark Lord <liml@....ca>
To:	Norman Diamond <n0diamond@...oo.co.jp>
Cc:	Jim Paris <jim@...n.com>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org, Robert Hancock <hancockrwd@...il.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Sergei Shtylyov <sshtylyov@...mvista.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Subject: Re: Off-by-one in both LIBATA and IDE drivers

Norman Diamond wrote:
> Jim Paris wrote:
>> Norman Diamond wrote:
>>>
>>> It looks like both LIBATA and the old IDE drivers have an off-by-one 
>>> error in deciding whether to use READ SECTOR(S) instead of READ 
>>> SECTOR(S) EXT.
>>
>> This was fixed here:
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=97b697a11b07e2ebfa69c488132596cc5eb24119 
>>
> 
> I'm still having trouble after applying the same patch to 2.6.24.3 
> (applying it three times in order to build Slax).  But now I wonder if 
> it's no longer the fault of drivers.
> 
> Does hdparm construct its own taskfiles for ATA and SATA in order to 
> produce an error trying to read sector number 0x0fffffff even after I 
> patched the kernel?
..

What, *exactly*, do you mean there.
Yes, hdparm constructs its own taskfiles for the --read-sector subcommand.
Are you hitting these errors with the latest hdparm (9.12)?

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