From: James Bottomley <James.Bottomley@steeleye.com>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Hugh Dickins <hugh@veritas.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] kernel/fork.c is broken by the new rmap
Date: 23 May 2004 15:54:31 -0500 [thread overview]
Message-ID: <1085345676.10930.38.camel@mulgrave> (raw)
If your architecture makes use of flush_dcache_mm_lock() then you get
this:
kernel/fork.c: In function `dup_mmap':
kernel/fork.c:336: `mapping' undeclared (first use in this function)
kernel/fork.c:336: (Each undeclared identifier is reported only once
kernel/fork.c:336: for each function it appears in.)
James
===== kernel/fork.c 1.181 vs edited =====
--- 1.181/kernel/fork.c Sat May 22 16:56:30 2004
+++ edited/kernel/fork.c Sun May 23 15:27:29 2004
@@ -333,9 +333,9 @@
/* insert tmp into the share list, just after mpnt */
spin_lock(&file->f_mapping->i_mmap_lock);
- flush_dcache_mmap_lock(mapping);
+ flush_dcache_mmap_lock(file->f_mapping);
vma_prio_tree_add(tmp, mpnt);
- flush_dcache_mmap_unlock(mapping);
+ flush_dcache_mmap_unlock(file->f_mapping);
spin_unlock(&file->f_mapping->i_mmap_lock);
}
reply other threads:[~2004-05-23 20:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1085345676.10930.38.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®