From: Torben Viets <Viets@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: XFS dm_crypt BUG?
Date: Sun, 13 Mar 2005 15:24:15 +0100 [thread overview]
Message-ID: <42344D0F.8050900@web.de> (raw)
In-Reply-To: <20050307080929.B2751595@wobbly.melbourne.sgi.com>
Hello,
it works with Kernel 2.6.11, probably the problem was that I had used 4
kb stacks and now I use the 8kb, but I'm not sure whether this was the
problem.
greetings
Torben Viets
Nathan Scott schrieb:
>On Sun, Mar 06, 2005 at 09:31:01PM +0100, Torben Viets wrote:
>
>
>>hello,
>>
>>I tried to reproduced the bug with the newest kernel and but it works
>>perfectly :D
>>
>>thnk you for fixing it.
>>
>>
>
>No problem, thanks for checking - could you send a note to the
>list(s) saying its resolved for you with that kernel version, in
>case others have also been seeing the problem.
>
>cheers.
>
>
>
prev parent reply other threads:[~2005-03-13 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 18:43 XFS dm_crypt BUG? Torben Viets
2005-02-27 19:34 ` Stephen Lord
2005-02-27 22:22 ` Nathan Scott
[not found] ` <422B6885.7090908@web.de>
[not found] ` <20050307080929.B2751595@wobbly.melbourne.sgi.com>
2005-03-13 14:24 ` Torben Viets [this message]
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=42344D0F.8050900@web.de \
--to=viets@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox