public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Cc: Rene <kaos@intet.dk>
Subject: Re: 2.4.5 + ReiserFS + SMP + umount = oops
Date: Sun, 27 May 2001 13:38:00 -0400	[thread overview]
Message-ID: <01052713380000.19585@oscar> (raw)

Hi,

This was reported on the reiserfs list yesterday.  Seems that the cleanup
applied late in  2.4.5-pre affected the locking of the umount process.  This
was posted to fix the problem.

Ed Tomlinson

-----------------------

"Vladimir V. Saveliev" wrote:
> 
> Hi
> 
> Gergely Tamas wrote:
> > 
> > Hi!
> > 
> > Kernel is 2.4.5
> > 
> > I've tried to unmount a reiserfs device (/uu.new) and got a segfault.
>
> Well, sys_umount in 2.4.5 changed to not lock_kernel() at the beginning and to not unlock_kernel() at the end correspondingly.
> journal_begin expectes kernel locked and it oopses when it is not. Maybe reiserfs_put_super should lock_kernel () itself?
> 


Hi,

You are right.
It seems, the next patch can fix umount reiserfs bug in linux-2.4.5 :

diff -urN v2.4.5/fs/reiserfs/super.c linux/fs/reiserfs/super.c
--- v2.4.5/fs/reiserfs/super.c   Sun Apr 29 16:02:25 2001
+++ linux/fs/reiserfs/super.c    Sat May 26 19:10:16 2001
@@ -104,7 +104,8 @@
 {
   int i;
   struct reiserfs_transaction_handle th ;
-  
+
+  lock_kernel() ;  
   /* change file system state to current state if it was mounted with
read-write permissions */
   if (!(s->s_flags & MS_RDONLY)) {
     journal_begin(&th, s, 10) ;
@@ -117,6 +118,7 @@
   ** to do a journal_end
   */
   journal_release(&th, s) ;
+  unlock_kernel() ;
 
   for (i = 0; i < SB_BMAP_NR (s); i ++)
     brelse (SB_AP_BITMAP (s)[i]);



Thanks,
Yura.

             reply	other threads:[~2001-05-27 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-27 17:38 Ed Tomlinson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-27  3:10 2.4.5 + ReiserFS + SMP + umount = oops Rene
2001-05-27  3:44 ` Keith Owens
2001-05-27  4:04   ` Rene
2001-05-27  4:11     ` Keith Owens
2001-05-27  4:28       ` Rene

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=01052713380000.19585@oscar \
    --to=tomlins@cam.org \
    --cc=kaos@intet.dk \
    --cc=linux-kernel@vger.kernel.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