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: <49F5F57D.3010700@damore.org>
Date:	Mon, 27 Apr 2009 11:12:13 -0700
From:	Garrett D'Amore <garrett@...ore.org>
To:	Maxim Levitsky <maximlevitsky@...il.com>
CC:	Robert Hancock <hancockrwd@...il.com>, pierre@...man.eu,
	sdhci-devel@...ts.ossman.eu,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Sdhci-devel] SDHCI driver runnining in aspire one, allows to
 write to R/O SD cards

As an extra data point, my sdhost driver in OpenSolaris works fine on 
the AA1.. it does see that the cards are locked, and refuses to allow 
them to be mounted read/write.

This leads me to believe that the original linux problem is one of two 
things:

* either a bug in the linux code, or
* busted circuit/hardware on a specific unit (i.e. a damaged unit)

I believe that if the Linux code was buggy here, the problem would be 
reproducible on all platforms, not just the AA1.  So my inclination, 
barring independent confirmation, is that most likely there are one ore 
more defective units out there.

Note that the AA1 also has buggy BIOS -- OpenSolaris can't "see" the 
cards (registers aren't properly initialized) unless they are present 
when the unit first powers up.

    -- Garrett

Maxim Levitsky wrote:
> On Fri, 2009-04-24 at 01:10 +0300, Maxim Levitsky wrote:
>   
>> On Mon, 2009-04-20 at 17:42 -0600, Robert Hancock wrote:
>>     
>>> Maxim Levitsky wrote:
>>>       
>>>> Hi,
>>>>
>>>> I am an owner of aspire one, and it has a card reader.
>>>> when I take a sd card, and pull down the protection tab, it still allows
>>>> to write to the card (I tested with my main notebook that indeed, it did
>>>> write there).
>>>>
>>>> My main notebook, acer aspire 5720, doesn't have this problem.
>>>> Kernel version in use is 2.6.28 vanilla, but this did happen in former
>>>> version as well.
>>>>
>>>>
>>>> Attached lspci, on acer one.
>>>>         
>>> Do you know if it worked in any kernel version or OS? It's known that 
>>> some SD card readers are too cheap to actually implement the 
>>> write-protect detection.
>>>       
>> I'll test in windows, but in linux it never did work.
>>
>> Best regards,
>> 	Maxim Levitsky
>>
>>     
> Yep, works fine in windows.
> Tested with and without lock tab.
>
>
> Best regards,
> 	Maxim Levitsky
>
> _______________________________________________
> sdhci-devel mailing list
> sdhci-devel@...ts.ossman.eu
> http://list.drzeus.cx/mailman/listinfo/sdhci-devel
>   

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