From: Earl Chew <earl_chew@agilent.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fs/pipe.c null pointer dereference
Date: Thu, 15 Oct 2009 21:27:31 -0700 [thread overview]
Message-ID: <4AD7F633.4070507@agilent.com> (raw)
In-Reply-To: <200910150211.43532.elendil@planet.nl>
Frans Pop wrote:
> Good luck with the hunt.
I've logged a defect:
http://bugzilla.kernel.org/show_bug.cgi?id=14416
which includes a proposed fix and script to reproduce.
Earl
next prev parent reply other threads:[~2009-10-16 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 13:39 fs/pipe.c null pointer dereference Earl Chew
2009-10-14 14:53 ` Frans Pop
2009-10-14 22:50 ` Earl Chew
2009-10-15 0:11 ` Frans Pop
2009-10-16 4:27 ` Earl Chew [this message]
2009-10-16 7:16 ` Pekka Enberg
2009-10-16 14:51 ` Earl Chew
2009-10-16 3:31 ` Earl Chew
2009-10-16 3:39 ` Earl Chew
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=4AD7F633.4070507@agilent.com \
--to=earl_chew@agilent.com \
--cc=elendil@planet.nl \
--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.