linux-kernel - Re: [PATCH 3/3] Fix copy_user on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:  <5dlk0mdbqd.fsf@Hurtta06k.keh.iki.fi>
Date:	30 Jun 2008 21:22:18 +0300
From:	Kari Hurtta <hurtta+gmane@...lo.fmi.fi>
To:	linux-kernel@...r.kernel.org
Subject:  Re: [PATCH 3/3] Fix copy_user on x86_64

Linus Torvalds <torvalds@...ux-foundation.org> writes:

> On Mon, 30 Jun 2008, Vitaly Mayatskikh wrote:
> > 
> > "For this reason, all patches should be submitting e-mail "inline".
> > WARNING:  Be wary of your editor's word-wrap corrupting your patch,
> > if you choose to cut-n-paste your patch."
> > 
> > My first thought was "should be attached inline".
> 
> Yeah, no, the "inline" there means literally as no attachment at all, but 
> inline in the normal mail.

And not as own mime body part with

Content-Disposition: inline


?


( As you see "inline" have several meanings. 

  yes. Some mail readers treats only first body part as 'inline'
  and other have 'attachments'.
)

/ Kari Hurtta


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/