From: Greg KH <gregkh@suse.de>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: INFO: task rcuc/0:7 blocked for more than 120 seconds.
Date: Tue, 3 Jan 2012 13:50:36 -0800 [thread overview]
Message-ID: <20120103215036.GA1347@suse.de> (raw)
In-Reply-To: <20120103213830.GG2376@linux.vnet.ibm.com>
On Tue, Jan 03, 2012 at 01:38:30PM -0800, Paul E. McKenney wrote:
> On Tue, Jan 03, 2012 at 12:37:17PM -0800, Greg KH wrote:
> > On Tue, Jan 03, 2012 at 12:27:16PM -0800, Paul E. McKenney wrote:
> > > On Tue, Dec 27, 2011 at 08:29:59PM -0800, Paul E. McKenney wrote:
> > > > On Tue, Dec 27, 2011 at 11:13:23AM +0200, Sasha Levin wrote:
> > > > > On Mon, 2011-12-26 at 08:31 -0800, Paul E. McKenney wrote:
> > > > > > Except that when I try looking for task_notify_func() in current mainline,
> > > > > > I get nothing.
> > > > > >
> > > > > > Where is task_notify_func() coming from?
> > > > >
> > > > > I was testing linux-next, it actually comes from the android tree:
> > > > > drivers/staging/android/lowmemorykiller.c
> > > >
> > > > That does sound familiar... I wonder if the stuff in staging is current
> > > > Android or historical stuff.
> > >
> > > And memory did serve for once. ;-)
> > >
> > > Current Android has the following for task_notify_func():
> > >
> > > static int
> > > task_notify_func(struct notifier_block *self, unsigned long val, void *data)
> > > {
> > > struct task_struct *task = data;
> > >
> > > if (task == lowmem_deathpending)
> > > lowmem_deathpending = NULL;
> > >
> > > return NOTIFY_OK;
> > > }
> > >
> > > This is from https://android.googlesource.com/kernel/common.git.
> > >
> > > Commit 5545554aac04918ece318270d63cbfcb015577a9 fixed this problem.
> > > The commit is shown below, FYI.
> > >
> > > Greg, would it be possible to pull in the current Android code? There
> > > have been a few fixes. ;-)
> >
> > I did base the stuff in staging on the common.git tree, but for some
> > reason this patch wasn't applied, odd, I'll go apply it now...
> >
> > Ah, I see, it didn't apply for various reasons:
> >
> > patching file drivers/staging/android/lowmemorykiller.c
> > Hunk #1 FAILED at 71.
> > Hunk #2 FAILED at 168.
> > Hunk #3 succeeded at 196 (offset 11 lines).
> > Hunk #4 succeeded at 204 (offset 11 lines).
> >
> > Care to rebase this patch and send it to me so that I can apply it? I
> > don't have the time to do it myself at the moment, sorry, lots of higher
> > priority items to get done this week, sorry.
>
> I will give it a shot. Working with linux-next -- if some other tree
> would be better for you, please let me know.
linux-next is great, thanks.
greg k-h
next prev parent reply other threads:[~2012-01-03 21:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 12:16 INFO: task rcuc/0:7 blocked for more than 120 seconds Sasha Levin
2011-12-26 16:31 ` Paul E. McKenney
2011-12-26 16:37 ` Frederic Weisbecker
2011-12-26 19:56 ` Paul E. McKenney
2012-01-04 19:03 ` [PATCH] rcu: Improve detection of illegal synchronize_rcu() call from RCU read side Frederic Weisbecker
2012-01-04 21:30 ` Paul E. McKenney
2012-01-05 1:45 ` Frederic Weisbecker
2012-01-05 2:01 ` Paul E. McKenney
2012-01-05 2:06 ` Frederic Weisbecker
2012-01-05 2:17 ` Paul E. McKenney
2011-12-27 9:13 ` INFO: task rcuc/0:7 blocked for more than 120 seconds Sasha Levin
2011-12-28 4:29 ` Paul E. McKenney
2012-01-03 20:27 ` Paul E. McKenney
2012-01-03 20:37 ` Greg KH
2012-01-03 21:38 ` Paul E. McKenney
2012-01-03 21:50 ` Greg KH [this message]
2012-01-03 22:26 ` Paul E. McKenney
2012-01-03 22:33 ` Paul E. McKenney
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=20120103215036.GA1347@suse.de \
--to=gregkh@suse.de \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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.