public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John <linux.kernel@free.fr>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, tglx@timesys.com,
	John <linux.kernel@free.fr>
Subject: Re: 2.6.20-rt8 patch tweaked for 2.6.20.5
Date: Tue, 10 Apr 2007 16:18:14 +0200	[thread overview]
Message-ID: <461B9CA6.8030707@free.fr> (raw)
In-Reply-To: <20070410131724.GA18553@elte.hu>

Ingo Molnar wrote:

> John wrote:
> 
>> I'd be happy to generate a clean patch!
>> (Would you agree to host it in your directory?)
>> http://people.redhat.com/mingo/realtime-preempt/older/
> 
> sure, i can put it there.

Great! Can you tell me how you generate the original -rt patch, so I can 
provide an updated version when a new 2.6.20 kernel is released?

>> 3. linux/kernel/futex.c
>> [ I'm not sure I've made the appropriate changes here ]
>>
>> Basically, we want to replace
>>   spin_lock(&pi_state->pi_mutex.wait_lock);
>> with
>>   spin_lock_irqsave(&pi_state->pi_mutex.wait_lock, flags);
>>
>> and we want to replace
>>   spin_unlock(&pi_state->pi_mutex.wait_lock);
>> with
>>   spin_unlock_irqrestore(&pi_state->pi_mutex.wait_lock, flags);
>>
>> Is that correct?
> 
> yes.

OK.

>> 5. linux/net/xfrm/xfrm_user.c
>> [ I'm not sure I've made the appropriate changes here ]
>>
>> Remove a patch that was already applied to 2.6.20.2
>> cf. patch-2.6.20.2
>>
>> --- a/net/xfrm/xfrm_user.c
>> +++ b/net/xfrm/xfrm_user.c
>> @@ -1273,10 +1273,6 @@ static int xfrm_get_policy(struct sk_buff *skb, 
>> struct nlmsghdr *nlh,
>>  		xp = xfrm_policy_bysel_ctx(type, p->dir, &p->sel, 
>>  		tmp.security, delete);
>>  		security_xfrm_policy_free(&tmp);
>>  	}
>> -	if (delete)
>> -		xfrm_audit_log(NETLINK_CB(skb).loginuid, NETLINK_CB(skb).sid,
>> -			       AUDIT_MAC_IPSEC_DELSPD, (xp) ? 1 : 0, xp, 
>> NULL);
>> -
>>  	if (xp == NULL)
>>  		return -ENOENT;
>>
>> @@ -1292,8 +1288,14 @@ static int xfrm_get_policy(struct sk_buff *skb, 
>> struct nlmsghdr *nlh,
>>  					      MSG_DONTWAIT);
>>  		}
>>  	} else {
>> -		if ((err = security_xfrm_policy_delete(xp)) != 0)
>> +		err = security_xfrm_policy_delete(xp);
>> +
>> +		xfrm_audit_log(NETLINK_CB(skb).loginuid, NETLINK_CB(skb).sid,
>> +			       AUDIT_MAC_IPSEC_DELSPD, err ? 0 : 1, xp, 
>> NULL);
>> +
>> +		if (err != 0)
>>  			goto out;
>> +
>>  		c.data.byid = p->index;
>>  		c.event = nlh->nlmsg_type;
>>  		c.seq = nlh->nlmsg_seq;
>>
>>
>> As a side note, I find the expression
>>   err ? 0 : 1
>> suspect. Why not write !err ?
> 
> it was in the original code and i didn't want to change that. I've 
> attached the original patch below - the bug is probably fixed upstream 
> meanwhile (in a different way) so no need to do any change there.

If I understand correctly, removing that specific patch from 
patch-2.6.20-rt8 is the appropriate course of action then?

Regards.

  reply	other threads:[~2007-04-10 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06 16:18 2.6.20-rt8 patch tweaked for 2.6.20.5 John
2007-04-06 17:36 ` Ingo Molnar
2007-04-10  9:07   ` John
2007-04-10 13:17     ` Ingo Molnar
2007-04-10 14:18       ` John [this message]
2007-04-10 14:23         ` Ingo Molnar
2007-04-10 16:22           ` John

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=461B9CA6.8030707@free.fr \
    --to=linux.kernel@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@timesys.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