public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: stable@kernel.org, chrisw@osdl.org, akpm@osdl.org,
	Simon.Derr@bull.net, linux-kernel@vger.kernel.org,
	torvalds@osdl.org
Subject: Re: [PATCH 2.6.13-stable] cpuset semaphore double trip fix
Date: Fri, 9 Sep 2005 19:31:00 -0700	[thread overview]
Message-ID: <20050909193100.068c6b22.pj@sgi.com> (raw)
In-Reply-To: <20050909185605.0f8e53e6.rdunlap@xenotime.net>

> Documentation/stable_kernel_rules.txt 

Aha - that's the stable documentation that I missed.  Thanks, Randy.

I figured that there was an explanation somewhere.  And there it is,
right in plain view.

Reading ...

My patch does pass the following criteria:

 - No "theoretical race condition" issues, unless an explanation of how
   the race can be exploited.

The conditions to trigger the race are too delicate to exploit
quickly.  I don't have a coded exploit.

Apparently I did the right thing by _not_ sending this patch to
stable@kernel.org <grin>.

This patch is dead.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  reply	other threads:[~2005-09-10  2:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10  0:44 [PATCH 2.6.13-stable] cpuset semaphore double trip fix Paul Jackson
2005-09-10  1:56 ` Randy.Dunlap
2005-09-10  2:31   ` Paul Jackson [this message]
2005-09-10  3:01 ` Chris Wright
2005-09-10  3:20   ` Paul Jackson
2005-09-10  3:28     ` Chris Wright
2005-09-10  3:40       ` Paul Jackson

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=20050909193100.068c6b22.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.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