Messages in this thread | | | From | Nick Piggin <> | Subject | Re: inotify fixes in stable | Date | Tue, 11 Mar 2008 15:12:37 +1100 |
| |
On Tuesday 11 March 2008 08:13, Greg KH wrote: > On Mon, Mar 10, 2008 at 09:57:55PM +0100, Pierre Ossman wrote: > > On Mon, 10 Mar 2008 13:31:16 -0700 > > > > Greg KH <greg@kroah.com> wrote: > > > On Mon, Mar 10, 2008 at 08:36:58PM +0100, Pierre Ossman wrote: > > > > The system is an OpenSuse 10.3 system, so 2.6.22.y would be the > > > > interesting one. I'll see if I can get a custom kernel in there (I've > > > > been unable to reproduce the problem outside a production > > > > environment). > > > > > > 2.6.22.y is no longer being released by me, so it isn't interesting to > > > me at all :) > > > > Oh? You made a release just 13 days ago, so I figured you were still > > giving it some love. > > In that release, I said it was going to be my last. > > > > What about 2.6.24? Is this still an issue there? > > > > Judging from the kernel bugzilla, it would seem so. > > > > But in my specific case, the guy on site was going to try an updated > > kernel from Suse's build system. I'll probably now the results > > tomorrow or the day after that. > > Please let us know.
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...
| |