From: "Justin P. Mattock" <justinmattock@gmail.com>
To: James Morris <jmorris@namei.org>
Cc: David Howells <dhowells@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
Subject: Re: linux-next: manual merge of the security-testing tree with Linus' tree
Date: Thu, 06 May 2010 16:24:21 -0700 [thread overview]
Message-ID: <4BE34FA5.8070906@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1005070908230.31779@tundra.namei.org>
On 05/06/2010 04:10 PM, James Morris wrote:
> On Thu, 6 May 2010, David Howells wrote:
>
>>
>> Stephen Rothwell<sfr@canb.auug.org.au> wrote:
>>
>>> I just used the version from Linus' tree.
>>
>> Okay.
>>
>> However, I'd like to NAK some bits of c5b60b5e67af8be4c58d3ffcc36894f69c4fbdc1
>> now that I see it...
>
> Will a patch -R of below be correct enough for you? Otherwise, please
> send me a new patch.
>
> (This is one of the reasons why I'm not so keen on whitespace fixes, also
> having to resolve merge conflicts, peturbing the history of the code etc.)
>
>
>>
>> @@ -1282,16 +1282,16 @@ long keyctl_session_to_parent(void)
>>
>> /* the parent must have the same effective ownership and mustn't be
>> * SUID/SGID */
>> - if (pcred-> uid != mycred->euid ||
>> + if (pcred->uid != mycred->euid ||
>> pcred->euid != mycred->euid ||
>> pcred->suid != mycred->euid ||
>> - pcred-> gid != mycred->egid ||
>> + pcred->gid != mycred->egid ||
>> pcred->egid != mycred->egid ||
>> pcred->sgid != mycred->egid)
>> goto not_permitted;
>>
>> /* the keyrings must have the same UID */
>> - if (pcred ->tgcred->session_keyring->uid != mycred->euid ||
>> + if (pcred->tgcred->session_keyring->uid != mycred->euid ||
>> mycred->tgcred->session_keyring->uid != mycred->euid)
>> goto not_permitted;
>>
>> _Please_ don't do either of these. The whole point is to line stuff up so
>> that as the eye scans down the lines, it can easily pick out the differences
>> in stuff that's otherwise greatly repetitive.
>>
>> David
>>
>
I never would of thought this. So the != has to be lined
up so things don't break?!
Justin P. Mattock
next prev parent reply other threads:[~2010-05-06 23:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 2:30 linux-next: manual merge of the security-testing tree with Linus' tree Stephen Rothwell
2010-05-06 10:49 ` David Howells
2010-05-06 23:10 ` James Morris
2010-05-06 23:24 ` Justin P. Mattock [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-16 3:02 Stephen Rothwell
2011-05-16 14:13 ` Serge Hallyn
2011-05-16 14:52 ` Stephen Rothwell
2009-05-22 5:29 Stephen Rothwell
2009-05-22 5:35 ` Al Viro
2009-05-22 9:04 ` James Morris
2009-02-06 7:23 Stephen Rothwell
2009-02-06 8:12 ` James Morris
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=4BE34FA5.8070906@gmail.com \
--to=justinmattock@gmail.com \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=toshi.okajima@jp.fujitsu.com \
/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