From: Mathieu Segaud <matt@minas-morgul.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Christian Axelsson <smiler@lanil.mine.nu>, linux-kernel@vger.kernel.org
Subject: Re: [2.6.10-rc2-mm1] OOPS on boot (hotplug related?)
Date: Thu, 18 Nov 2004 04:02:02 +0100 [thread overview]
Message-ID: <87d5yb272t.fsf@barad-dur.crans.org> (raw)
In-Reply-To: <87hdno0xnf.fsf@barad-dur.crans.org> (Mathieu Segaud's message of "Thu, 18 Nov 2004 02:11:00 +0100")
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
Mathieu Segaud <matt@minas-morgul.org> disait dernièrement que :
> V. Saveliev provided the right fix shortly after I reported this oops.
>
> I attach the patch
>
> Regards,
correcting myself, the patch I gave was to apply in fs/reiser4...
by the way, thanks go to Vladimir Saveliev.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: reiser4-context-fix.patch --]
[-- Type: text/x-patch, Size: 623 bytes --]
--- a/fs/reiser4/plugin/file/file.c 2004-11-17 09:36:11 +03:00
+++ b/fs/reiser4/plugin/file/file.c 2004-11-17 09:36:11 +03:00
@@ -1961,8 +1961,10 @@
{
struct page *page;
struct inode *inode;
-
+ reiser4_context ctx;
+
inode = area->vm_file->f_dentry->d_inode;
+ init_context(&ctx, inode->i_sb);
/* block filemap_nopage if copy on capture is processing with a node of this file */
down_read(&reiser4_inode_data(inode)->coc_sem);
@@ -1972,6 +1974,8 @@
drop_nonexclusive_access(unix_file_inode_data(inode));
up_read(&reiser4_inode_data(inode)->coc_sem);
+
+ reiser4_exit_context(&ctx);
return page;
}
[-- Attachment #3: Type: text/plain, Size: 69 bytes --]
--
"Just wait. My crystal ball is infallible."
- Linus Torvalds
next prev parent reply other threads:[~2004-11-18 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 21:17 Christian Axelsson
2004-11-17 22:53 ` Andrew Morton
2004-11-18 1:11 ` Mathieu Segaud
2004-11-18 3:02 ` Mathieu Segaud [this message]
2004-11-17 23:12 Hanno Meyer-Thurow
2004-11-17 23:14 Hanno Meyer-Thurow
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=87d5yb272t.fsf@barad-dur.crans.org \
--to=matt@minas-morgul.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smiler@lanil.mine.nu \
/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®