All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chr <chunkeey@web.de>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, Greg KH <greg@kroah.com>,
	Pierre Ossman <drzeus-list@drzeus.cx>,
	LKML <linux-kernel@vger.kernel.org>,
	Nick Piggin <npiggin@suse.de>,
	stable@kernel.org
Subject: Re: inotify fixes in stable
Date: Tue, 25 Mar 2008 14:15:37 +0100	[thread overview]
Message-ID: <200803251415.38235.chunkeey@web.de> (raw)
In-Reply-To: <20080325004233.GN23462@sequoia.sous-sol.org>

On Tuesday 25 March 2008 01:42:33 Chris Wright wrote:
> * Chr (chunkeey@web.de) wrote:
>
> [...]
>
> Please just explicitly send the fixes to stable@kernel.org and Cc Nick.
Done...! I took both patches from the current git-tree.
but forgot to add a tested-by flag... well, but I added the patches, right?!

>
> I'm actually disinclined to take 0d71bd5993b630a989d15adc2562a9ffe41cd26d
> which seems to primarily just remove the WARN_ON(), although that is
> assuming it is indeed no longer triggered with just the race fix,
> d599e36a9ea85432587f4550acc113cd7549d12a.
hmm, Nick said that the debug code is racy and "not very good at finding 
problems" either... But as long as the real fix has a _real_ change to get 
merged in 2.6.24.5, I'm happy ;-)

>
> thanks,
> -chris

Regards,
	Christian

      reply	other threads:[~2008-03-25 13:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10  8:11 inotify fixes in stable Pierre Ossman
2008-03-10 16:03 ` Greg KH
2008-03-10 19:36   ` Pierre Ossman
2008-03-10 20:31     ` Greg KH
2008-03-10 20:57       ` Pierre Ossman
2008-03-10 21:13         ` Greg KH
2008-03-11  4:12           ` Nick Piggin
2008-03-24 22:33             ` Chr
2008-03-25  0:42               ` Chris Wright
2008-03-25 13:15                 ` Chr [this message]

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=200803251415.38235.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=chrisw@sous-sol.org \
    --cc=drzeus-list@drzeus.cx \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=npiggin@suse.de \
    --cc=stable@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.