From: Tyler Hicks <tyhicks@canonical.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
dustin.kirkland@gazzang.com, Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
ecryptfs@vger.kernel.org
Subject: Re: ecryptfs: Kernel BUG when closing device
Date: Thu, 3 May 2012 16:44:39 -0500 [thread overview]
Message-ID: <20120503214439.GC16993@boyd> (raw)
In-Reply-To: <CA+1xoqeVHH_8MezKFX=gB9o5zFMjajHAVai3SxGpzZpvQ5uUHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On 2012-05-03 18:22:01, Sasha Levin wrote:
> On Thu, May 3, 2012 at 6:17 PM, Tyler Hicks <tyhicks@canonical.com> wrote:
> > On 2012-05-03 08:00:03, Sasha Levin wrote:
> >> Hi all,
> >>
> >> After some fuzzing using trinity inside a KVM guest, I've stumbled on the following:
> >
> > Hi Sasha - Thanks for reporting this issue. Is there any way to get
> > trinity to reproduce this fuzzing sequence?
>
> Hi Tyler,
>
> Not really, since it's not the result of a single command it can't
> recreate it easily.
>
> On the other hand, I'd be happy to add any debugging ideas you have
> into the tested kernel and attempt to recreate the issue.
I appreciate the offer, but I was able to reproduce the issue pretty
easily. Inherited and passed file descriptors of /dev/ecryptfs are not
handled properly. I've opened this bug to track the resolution:
https://launchpad.net/bugs/994247
Tyler
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-05-03 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 6:00 ecryptfs: Kernel BUG when closing device Sasha Levin
2012-05-03 16:17 ` Tyler Hicks
2012-05-03 16:22 ` Sasha Levin
2012-05-03 21:44 ` Tyler Hicks [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=20120503214439.GC16993@boyd \
--to=tyhicks@canonical.com \
--cc=davej@redhat.com \
--cc=dustin.kirkland@gazzang.com \
--cc=ecryptfs@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.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 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.