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:	Sun, 07 Jun 2015 10:22:22 +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 #52 from Markus Rathgeb <maggu2810@...il.com> ---
> This is up to the SCSI developers.

So, could we CC someone?

So, if we keep the current situation everyone who ones such a buggy hardware
have the following options (IMHO):
1. create a udev rule, that sets "write through" for this hardware
2. using non-journal filesystems only
3. do not use this hardware anymore

But I think all that options are not good ones.

The udev rule will work on my machines then, but a USB drive is designed to be
mobile. And a mobile storage will be used on other machines, too, without
change some system stuff on that (missing permissions, ...).

I could understand if someone states that the hardware is buggy and there is
nothing to do. But I think this does not fit to the Linux Kernel. The kernel is
filled with a lot workarounds for hardware / implementations that is not
correct.

Could someone contact a SCSI developer, perhaps that stuff could comment their
ideas (e.g. for "if SYNCHRONIZE CACHE command is not working, fallback to write
through" and "what should happen when a drive really does have a write cache
but doesn't recognize the SYNCHRONIZE CACHE command").

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ