From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Daniel Walker <dwalker@mvista.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -rt] scheduling while atomic in remove_proc_entry()
Date: Mon, 08 Jan 2007 13:20:02 +0100 [thread overview]
Message-ID: <1168258802.6235.18.camel@twins> (raw)
In-Reply-To: <20061229211237.690413000@mvista.com>
On Fri, 2006-12-29 at 13:12 -0800, Daniel Walker wrote:
>
> Signed-Off-By: Daniel Walker <dwalker@mvista.com>
>
> ---
> fs/proc/generic.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.19/fs/proc/generic.c
> ===================================================================
> --- linux-2.6.19.orig/fs/proc/generic.c
> +++ linux-2.6.19/fs/proc/generic.c
> @@ -555,7 +555,6 @@ static void proc_kill_inodes(struct proc
> /*
> * Actually it's a partial revoke().
> */
> - filevec_add_drain_all();
> lock_list_for_each_entry(filp, &sb->s_files, f_u.fu_llist) {
> struct dentry * dentry = filp->f_path.dentry;
> struct inode * inode;
> @@ -738,6 +737,8 @@ void remove_proc_entry(const char *name,
> break;
> }
> spin_unlock(&proc_subdir_lock);
> +
> + filevec_add_drain_all();
> out:
> return;
> }
Well, no. Draining after the inspect 'all' loop doesn't make sense, but
looking at 2.6.20-rc3-rt0 remove_proc_entry() looks sane.
next prev parent reply other threads:[~2007-01-08 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 21:12 [PATCH -rt] scheduling while atomic in remove_proc_entry() Daniel Walker
2007-01-08 12:20 ` Peter Zijlstra [this message]
2007-01-08 12:59 ` Daniel Walker
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=1168258802.6235.18.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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