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-BSYVwiCLJC@https.bugzilla.kernel.org/>
Date:	Fri, 19 Dec 2014 18:51:29 +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 #15 from Alan Stern <stern@...land.harvard.edu> ---
You did not attach anything -- instead you copied & pasted the logs directly
into the bug report!  This makes the report very long and hard to read.  You
should have used the "add an attachment" button near the top of the bug report.

Also, I can't tell what you did here.  You posted several logs and several
usbmon traces, but you didn't say how they are related.  Also, the usbmon
traces don't show any errors!

Here's what you should do:

   Plug in the drive and check the kernel log to see which bus it is attached
to.

   Unplug the drive.

   Run "dmesg -C" to clear the kernel's log buffer

   Run "cat /sys/kernel/debug/usb/usbmon/1u >mon.txt", if the drive was
attached to bus 1.  If it was attached to bus 2, use "2u" instead of "1u".

   Plug in the drive and wait for the error messages to appear.

   Unplug the drive.

   Use ^C to kill the "cat" program above.

   Run "dmesg >log.txt"

Finally, _attach_ (don't copy & paste!) the log.txt and mon.txt files to this
bug report.

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