[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A4B4E1B.6090900@in.ibm.com>
Date: Wed, 01 Jul 2009 17:22:59 +0530
From: Sachin Sant <sachinp@...ibm.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Eric Paris <eparis@...hat.com>, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: boot failure
Stephen Rothwell wrote:
> next-20090629 was fine. The commits in 0630 and not in 0629 (from the
> fsnotify tree) are:
>
> Audit: clean up the audit_watch split
> audit: convert audit watches to use fsnotify instead of inotify
> audit: redo audit watch locking and refcnt in light of fsnotify
> audit: do not get and put just to free a watch
> fsnotify: duplicate fsnotify_mark_entry data between 2 marks
> fsnotify: allow addition of duplicate fsnotify marks
> audit: reimplement audit_trees using fsnotify rather than inotify
> inotify: deprecate the inotify kernel interface
>
Stephen / Eric,
I too am facing similar issue on both Power and x86.
Culprit seems to be 2nd patch in the above list.
commit e1b79967e2b29839d16c12b534597a15d8630fc4
audit: convert audit watches to use fsnotify instead of inotify
I wasn't able to remove only patch 2 because of dependencies
on other patches. After i reverted patches 2 to 7 in the above
list, i was able to boot the machine. Then i applied patch 2
and the machine failed to boot.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists