From: Willy Tarreau <w@1wt.eu>
To: Andrew Morton <akpm@osdl.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kirill Korotaev <dev@openvz.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Fernando Vazquez <fernando@oss.ntt.co.jp>,
"David S. Miller" <davem@davemloft.net>,
tony.luck@intel.com, linux-ia64@vger.kernel.org,
stable@kernel.org, xemul@openvz.org, devel@openvz.org
Subject: Re: [PATCH] IA64,sparc: local DoS with corrupted ELFs
Date: Fri, 8 Sep 2006 06:34:12 +0200 [thread overview]
Message-ID: <20060908043412.GA7470@1wt.eu> (raw)
In-Reply-To: <20060907164207.16745087.akpm@osdl.org>
On Thu, Sep 07, 2006 at 04:42:07PM -0700, Andrew Morton wrote:
> On Thu, 7 Sep 2006 22:07:14 +0200
> Willy Tarreau <w@1wt.eu> wrote:
>
> > On Thu, Sep 07, 2006 at 08:17:04AM -0700, Linus Torvalds wrote:
> > >
> > >
> > > On Thu, 7 Sep 2006, Kirill Korotaev wrote:
> > > >
> > > > Does the patch below looks better?
> > >
> > > Yes.
> > >
> > > Apart from the whitespace corruption, that is.
> > >
> > > I don't know how to get mozilla to not screw up whitespace.
>
> Me either. I've had a bug report in the mozilla system for maybe four
> years concerning space-stuffing. Occasionally it comes to life but afaict
> nothing ever changes.
>
> I expect it'd be pretty easy to undo the space-stuffing in git.
Perhaps, but it should not be up to the versionning system to decide to
change the contents of the patches which get merged. Otherwise, we will
not be able to trust it as much as today.
> In extremis I just do s/^ /^ / and it works. An automated solution would
> need to recognise the appropriate headers (Format=Flowed, iirc).
perhaps for this case, but then what will prevent us from trying to
implement dirtier features such as line un-wrapping ?
> > maybe by using it to download mutt or something saner ? :-)
> >
> > More seriously, while we don't like email attachments because they make
> > it impossible to comment on a patch, maybe we should encourage people
> > with broken mailers to post small patches in both forms :
> > - pure text for human review (spaces are not much of a problem here)
> > - MIME to apply the patch.
>
> argh. That means that email contains two copies of the patch. So it
> applies with `patch --dry-run' then causes havoc with `patch'
except if the text version is mangled in order not to be detected as
a patch. I suspect that inserting a space in front of "---" is enough
for patch not to find it. Don't get me wrong, I know this is dirty.
But as long as some people will use broken mailers, we'll get broken
patches. Some people occasionnaly switch to attachments stating they
have broken mailers, and others even post links to their patches,
which is annoying for potential reviewers. If we could give them
strict rules on how to proceed when they have such problems, it would
make the job easier for others.
willy
next prev parent reply other threads:[~2006-09-08 4:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 12:17 [PATCH] IA64,sparc: local DoS with corrupted ELFs Kirill Korotaev
2006-09-05 11:39 ` Kyle McMartin
2006-09-05 13:08 ` Kirill Korotaev
2006-09-06 18:24 ` Linus Torvalds
2006-09-06 18:27 ` Matthew Wilcox
2006-09-06 18:45 ` [stable] " Greg KH
2006-09-06 19:12 ` Matthew Wilcox
2006-09-06 19:17 ` Christoph Lameter
2006-09-06 19:25 ` Greg KH
2006-09-06 20:27 ` Willy Tarreau
2006-09-07 13:11 ` Marcel Holtmann
2006-09-07 15:37 ` Greg KH
2006-09-08 9:11 ` Jes Sorensen
2006-09-06 19:06 ` Arjan van de Ven
2006-09-08 9:12 ` Jes Sorensen
2006-09-07 10:17 ` Kirill Korotaev
2006-09-07 15:17 ` Linus Torvalds
2006-09-07 20:07 ` Willy Tarreau
2006-09-07 23:42 ` Andrew Morton
2006-09-08 4:34 ` Willy Tarreau [this message]
2006-09-08 15:15 ` Kirill Korotaev
2006-09-08 15:35 ` Linus Torvalds
2006-09-08 15:49 ` Dave Jones
2006-09-08 16:09 ` Kirill Korotaev
2006-09-13 15:46 ` Randy.Dunlap
2006-09-06 20:20 ` Linus Torvalds
2006-09-06 21:27 ` Luck, Tony
2006-09-06 23:23 ` Fernando Luis Vázquez Cao
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=20060908043412.GA7470@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=dev@openvz.org \
--cc=devel@openvz.org \
--cc=fernando@oss.ntt.co.jp \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@osdl.org \
--cc=xemul@openvz.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