All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Eric Paris <eparis@redhat.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: boot failure
Date: Wed, 01 Jul 2009 17:22:59 +0530	[thread overview]
Message-ID: <4A4B4E1B.6090900@in.ibm.com> (raw)
In-Reply-To: <20090701160014.595e1338.sfr@canb.auug.org.au>

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
---------------------------------

  reply	other threads:[~2009-07-01 11:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01  6:00 linux-next: boot failure Stephen Rothwell
2009-07-01 11:52 ` Sachin Sant [this message]
2009-07-01 12:20   ` Stephen Rothwell
2009-07-01 12:35 ` Eric Paris
2009-07-01 14:46   ` Sachin Sant
  -- strict thread matches above, loose matches on Subject: below --
2011-03-20 20:16 linux-next " John David Anglin
2011-03-21 16:37 ` James Bottomley

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=4A4B4E1B.6090900@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.