mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 02:11:00 +0100	[thread overview]
Message-ID: <87hdno0xnf.fsf@barad-dur.crans.org> (raw)
In-Reply-To: <20041117145359.4f017ed1.akpm@osdl.org> (Andrew Morton's message of "Wed, 17 Nov 2004 14:53:59 -0800")

[-- Attachment #1: Type: text/plain, Size: 533 bytes --]

Andrew Morton <akpm@osdl.org> disait dernièrement que :

> Christian Axelsson <smiler@lanil.mine.nu> wrote:
>>
>> I'm getting OOPSes on boot on my laptop. Output is copied by hand and Ive 
>> only included the parts that I *think* are useful:
>> 
>> ...
>> EIP is at get_nonexclusive_access+0x13/0x40
>
> Yup, seems that reiser4 broke.  I've forwarded a copy of an earlier report
> to reiserfs-dev@namesys.com.

V. Saveliev provided the right fix shortly after I reported this oops.

I attach the patch

Regards,


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: reiser4-context-fix.patch --]
[-- Type: text/x-patch, Size: 994 bytes --]

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2004/11/15 16:23:47+03:00 vs@tribesman.namesys.com 
#   unix_file_filemap_nopage: missing context creation is added
# 
# plugin/file/file.c
#   2004/11/15 16:23:45+03:00 vs@tribesman.namesys.com +5 -1
#   unix_file_filemap_nopage: missing context creation is added
# 
diff -Nru a/plugin/file/file.c b/plugin/file/file.c
--- a/plugin/file/file.c	2004-11-17 09:36:11 +03:00
+++ b/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: 131 bytes --]



-- 
Lisa R. Nelson wrote:
> So much for a friendly group.

You really have seen nothing yet :-)

	- Bas Mevissen on linux-kernel

  reply	other threads:[~2004-11-18  1:15 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 [this message]
2004-11-18  3:02     ` Mathieu Segaud
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=87hdno0xnf.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®