public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Hannemann <arnd@arndnet.de>
To: Tyler Hicks <tyhicks@canonical.com>
Cc: linux-kernel@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: Re: 3.2.0-rc2: kernel BUG at fs/ecryptfs/crypto.c:348! regression?
Date: Tue, 22 Nov 2011 21:26:08 +0100	[thread overview]
Message-ID: <4ECC0560.7010502@arndnet.de> (raw)
In-Reply-To: <20111122155149.GB6006@boyd>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Am 22.11.2011 16:51, schrieb Tyler Hicks:
> On 2011-11-22 09:53:08, Arnd Hannemann wrote:

>> 
>> I'm regularly hitting below BUG (also with yesterdays Linus git): 3.1.1 is working.
> 
> Please give this patch a try:
> 
> http://article.gmane.org/gmane.comp.file-systems.ecryptfs.general/18
> 
> Here's a link directly to the patch in the eCryptfs git tree but the link might not stay around for much longer:
> 
> http://git.kernel.org/?p=linux/kernel/git/tyhicks/ecryptfs.git;a=patch;h=45608c8eb41a6deab47876ae2679117820006d25
> 
> I plan on upstreaming this patch in the next day or two, so please let me know whether or not it fixes your problem.

until now its looking good. No BUG hit with recent linus git and above patch applied.

Best regards
Arnd
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7MBVQACgkQZyJJMjKQIYQizACguX3yXPXG3x61gOZ9uDCRsGd2
YD8AoLBdedR33cxKbaSmH76kCr/J7GKn
=Exjt
-----END PGP SIGNATURE-----

      reply	other threads:[~2011-11-22 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22  8:53 3.2.0-rc2: kernel BUG at fs/ecryptfs/crypto.c:348! regression? Arnd Hannemann
2011-11-22 15:51 ` Tyler Hicks
2011-11-22 20:26   ` Arnd Hannemann [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=4ECC0560.7010502@arndnet.de \
    --to=arnd@arndnet.de \
    --cc=ecryptfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tyhicks@canonical.com \
    /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