The patch titled
     jbd: do not try lock_acquire after handle made invalid
has been added to the -mm tree.  Its filename is
     jbd-do-not-try-lock_acquire-after-handle-made-invalid.patch

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: jbd: do not try lock_acquire after handle made invalid
From: Jonas Bonn <[EMAIL PROTECTED]>

This likely fixes the oops in __lock_acquire reported as:

http://www.kerneloops.org/raw.php?rawid=2753&msgid=
http://www.kerneloops.org/raw.php?rawid=2749&msgid=

In these reported oopses, start_this_handle is returning -EROFS.

Signed-off-by: Jonas Bonn <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 fs/jbd/transaction.c |    2 ++
 1 file changed, 2 insertions(+)

diff -puN 
fs/jbd/transaction.c~jbd-do-not-try-lock_acquire-after-handle-made-invalid 
fs/jbd/transaction.c
--- a/fs/jbd/transaction.c~jbd-do-not-try-lock_acquire-after-handle-made-invalid
+++ a/fs/jbd/transaction.c
@@ -288,10 +288,12 @@ handle_t *journal_start(journal_t *journ
                jbd_free_handle(handle);
                current->journal_info = NULL;
                handle = ERR_PTR(err);
+               goto out;
        }
 
        lock_acquire(&handle->h_lockdep_map, 0, 0, 0, 2, _THIS_IP_);
 
+out:
        return handle;
 }
 
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

jbd-do-not-try-lock_acquire-after-handle-made-invalid.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to