linux-ext4 - [Bug 89511] USB-storage mount error

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: <bug-89511-13602-ZDnnGRHrS6@https.bugzilla.kernel.org/>
Date:	Sat, 10 Jan 2015 21:13:03 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 89511] USB-storage mount error

https://bugzilla.kernel.org/show_bug.cgi?id=89511

--- Comment #47 from Alan Stern <stern@...land.harvard.edu> ---
All of your tests show that fdisk and mount work okay when the cache type is
set to "write through", and they get errors when the cache type is set to
"write back".

You can see the difference between the two controllers when the drive is first
detected.  Your report_20150110_3.18.2_1.txt log contains:

[   13.637727] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA

whereas the report_20150110_3.18.2_2.txt log contains:

[  768.511250] sd 5:0:0:0: [sdc] No Caching mode page found
[  768.511380] sd 5:0:0:0: [sdc] Assuming drive cache: write through

Obviously the two controllers don't have the same behavior.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html