linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: reiserfs-devel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/4] Fix reiserfs deadlocks with quotas
Date: Fri, 16 Nov 2012 12:33:36 +0100	[thread overview]
Message-ID: <1353065620-27279-1-git-send-email-jack@suse.cz> (raw)


  Hello,

  recent user report brought to my attention that quota on reiserfs is
rather easy to deadlock. This is a fallout from BKL conversion. This
series should fix the issue (at least fsstress runs now on reiserfs with
quotas enabled without any lockdep warnings and reported deadlocks are
solved as well). I'll push these patches to Linus soon if noone complains.

								Honza

             reply	other threads:[~2012-11-16 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 11:33 Jan Kara [this message]
2012-11-16 11:33 ` [PATCH 1/4] reiserfs: Fix lock ordering during remount Jan Kara
2012-11-16 11:33 ` [PATCH 2/4] reiserfs: Protect reiserfs_quota_on() with write lock Jan Kara
2012-11-16 11:33 ` [PATCH 3/4] reiserfs: Protect reiserfs_quota_write() " Jan Kara
2012-11-16 11:33 ` [PATCH 4/4] reiserfs: Move quota calls out of " Jan Kara

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=1353065620-27279-1-git-send-email-jack@suse.cz \
    --to=jack@suse.cz \
    --cc=linux-fsdevel@vger.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).