From: Earl Chew <earl_chew@agilent.com>
To: dwalker@fifo99.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1]: fs: pipe.c null pointer dereference + sign off
Date: Mon, 19 Oct 2009 14:29:19 -0700 [thread overview]
Message-ID: <4ADCDA2F.1090209@agilent.com> (raw)
In-Reply-To: <1255981395.23353.46.camel@desktop>
Daniel Walker wrote:
> You patch looks like it might be line wrapped .. Sometimes mailers will
> do that if you don't tell them the content is already formatted.
Arghhh ... struck by Thunderbirditis.
Apparently mailnews.send_plaintext_flowed=false is the key to
preserving tabs, and the Toggle Word Wrap extension is useful
for to avoid inserting additional newlines:
https://addons.mozilla.org/en-US/thunderbird/addon/2351
As you can see, I'm new to this game. Your patience is appreciated.
I'll repost.
> Also I see your using a MontaVista kernel, which is older than current
> mainline .. I would assume you tested this on a recent kernel also?
I don't have immediate access to a more recent kernel.
The changes are fairly straightforward and I have added extensive
documentation on how to reproduce and verify the defect.
Is anyone interested in helping out here by verifying on a
more recent kernel?
Earl
next prev parent reply other threads:[~2009-10-19 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 14:37 [PATCH v1 1/1]: fs: pipe.c null pointer dereference Earl Chew
2009-10-16 21:50 ` Jiri Kosina
2009-10-19 18:13 ` [PATCH v2 1/1]: fs: pipe.c null pointer dereference + sign off Earl Chew
2009-10-19 19:43 ` Daniel Walker
2009-10-19 21:29 ` Earl Chew [this message]
2009-10-19 21:35 ` [PATCH v3 1/1]: fs: pipe.c null pointer dereference + sign off + unmangled diffs Earl Chew
2009-10-19 22:55 ` [PATCH v4 1/1]: fs: pipe.c null pointer dereference + really " Earl Chew
2009-10-21 9:38 ` Américo Wang
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=4ADCDA2F.1090209@agilent.com \
--to=earl_chew@agilent.com \
--cc=dwalker@fifo99.com \
--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
Powered by JetHome