mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Chr <chunkeey@web.de>
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: Mon, 24 Mar 2008 17:42:33 -0700	[thread overview]
Message-ID: <20080325004233.GN23462@sequoia.sous-sol.org> (raw)
In-Reply-To: <200803242333.30200.chunkeey@web.de>

* Chr (chunkeey@web.de) wrote:
> On Tuesday 11 March 2008 05:12:37 Nick Piggin wrote:
> >
> > The messages should actually be harmless. There is a race in the debug
> > code that can trigger them. But I wouldn't object to the patches going
> > to -stable...
> >
> let me guess... the patch didn't get into 2.6.24.4, right? because I still
> get these noisy "WARNING: at fs/inotify.c:172 set_dentry_child_flags()"
> and probably alot of other kde4 users too?!

a) doesn't appear to have been Cc'd to stable@kernel.org until now
(fell through one crack)
b) there was outstanding request from greg for clarification of the
issue for 2.6.24 (fell through another crack)

Please just explicitly send the fixes to stable@kernel.org and Cc Nick.

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.

thanks,
-chris

  reply	other threads:[~2008-03-25  0:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10  8:11 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 [this message]
2008-03-25 13:15                 ` Chr

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=20080325004233.GN23462@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=chunkeey@web.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®