reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 21092] Kernel 2.6.36 Bug during quotaon on reiserfs
Date: Wed, 27 Oct 2010 21:55:30 GMT	[thread overview]
Message-ID: <201010272155.o9RLtUqb021637@demeter2.kernel.org> (raw)
In-Reply-To: <bug-21092-695@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=21092


Jan Kara <jack@suse.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jack@suse.cz




--- Comment #1 from Jan Kara <jack@suse.cz>  2010-10-27 21:55:24 ---
This looks like a fallout of the BKL conversion in reiserfs. After the
conversion, it is expected that reiserfs_unpack will be called with write_lock
held but that's not the case for the call from reiserfs_quota_on.

The easiest is probably to just acquire write_lock before calling
reiserfs_unpack. The attached patch does this and don't see the BUG with it.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-10-27 21:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-24 16:57 [Bug 21092] New: Kernel 2.6.36 Bug during quotaon on reiserfs bugzilla-daemon
2010-10-25 22:54 ` [Bug 21092] " bugzilla-daemon
2010-10-27 21:55 ` bugzilla-daemon [this message]
2010-10-27 21:58 ` bugzilla-daemon
2010-10-27 23:04 ` bugzilla-daemon
2010-10-29  6:52 ` bugzilla-daemon
2010-11-18 23:46 ` bugzilla-daemon
2011-01-06 15:39 ` bugzilla-daemon
2011-01-06 15:40 ` bugzilla-daemon

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=201010272155.o9RLtUqb021637@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).