From: Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>
To: linux-kernel@vger.kernel.org
Cc: alexl@redhat.com, ebiederm@xmission.com, viro@zeniv.linux.org.uk,
serge.hallyn@ubuntu.com, luto@amacapital.net, mszeredi@suse.cz
Subject: PROBLEM: Kernel null pointer dereference when sandboxing
Date: Mon, 01 Jun 2015 19:18:34 +0000 (GMT) [thread overview]
Message-ID: <fad4b5172c59b.556cb00a@langara.bc.ca> (raw)
Hello,
I wasn't finding any responses or interest on the Bugzilla on a bug of
mine at https://bugzilla.kernel.org/show_bug.cgi?id=98301 for the last
little while. I think the same or a similar bug has been reported at
http://permalink.gmane.org/gmane.linux.kernel.containers/29340. I
would love to run any tests or help any way I can to fix this bug. I
understand if maintainers are too busy to reply or fix this bug.
Thank you,
Steven Stewart-Gallus
next reply other threads:[~2015-06-01 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 19:18 Steven Stewart-Gallus [this message]
2015-06-01 19:19 ` PROBLEM: Kernel null pointer dereference when sandboxing Andy Lutomirski
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=fad4b5172c59b.556cb00a@langara.bc.ca \
--to=sstewartgallus00@mylangara.bc.ca \
--cc=alexl@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mszeredi@suse.cz \
--cc=serge.hallyn@ubuntu.com \
--cc=viro@zeniv.linux.org.uk \
/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