From: Maximilian Mehnert <mmehnert@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.0-test9, deadlock using usb-storage, eventually memory allocation bug
Date: Mon, 17 Nov 2003 20:25:45 +0100 [thread overview]
Message-ID: <1069097145.3fb920b9a10b1@fvs.dnsalias.net> (raw)
Hello, everybody!
So far I have spoken to Jari Ruusu <jariruusu@users.sourceforge.net> who
is maintaining loop-AES and to Matthew Dharm <mdharm-usb@one-eyed-alien.net>
who
seems to be maintaining usb-storage at the moment.
Jari Ruusu helped me by locating the whereabouts of the following bug by
reading
my syslogs with debugging output from usb-storage and by providing some kernel
patches to isolate the error:
I am using a harddisk attached via a cardbus usb 2.0 card. On it I have an
encrypted partition which I access via loop-AES.
I can easily reproduce a complete deadlock in the usb-storage system by
mounting
my encrypted partition or copying files to or from it (depends on
configuration).
That's what Jari Ruusu wrote on Sun, 09 Nov 2003:
> It was very similar memory allocation failure again: usb storage RAM alloc
> waited for pages to be freed, and all freeable pages were waiting to be
> written out to your usb device. Same thing, just different place.
On Sun, Nov 16, 2003 at 12:48:42PM -0800, Matthew Dharm wrote:
> You should take this up with linux-kernel@vger.kernel.org -- it's a memory
> allocation problem, not a usb-storage problem. I can't fix it.
I did without posting my kernel config and my syslog files with the usb-storage
messages as according to the FAQ this would be overkill.
If anybody is willing to help me I would gratefully send her/him all my logs
and my previous correspondence on this topic :)
Greetings from Berlin && excuses for my bad English,
Maximilian
--
Maximilian Mehnert <mmehnert at gmx dot net>
http://members.lycos.co.uk/endofuniverse/gpg.html
Fingerprint: 387F 5AA6 5856 2A49 C88C DA86 FBA8 5122 817B C60E
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
next reply other threads:[~2003-11-17 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 19:25 Maximilian Mehnert [this message]
2003-11-17 20:28 ` Kernel 2.6.0-test9, deadlock using usb-storage, eventually memory allocation bug Vedran Rodic
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 21:35 Maximilian Mehnert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1069097145.3fb920b9a10b1@fvs.dnsalias.net \
--to=mmehnert@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.