From: Mikulas Patocka <mpatocka@redhat.com>
To: Valerie Aurora <val@vaaconsulting.com>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
dm-devel@redhat.com,
Christopher Chaltain <christopher.chaltain@canonical.com>
Subject: Re: [PATCH] deadlock with suspend and quotas
Date: Mon, 28 Nov 2011 16:14:05 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.1111281612030.11895@hs20-bc2-1.build.redhat.com> (raw)
In-Reply-To: <CAD-XujnH1UJXrEbYAKOSjvdwVnehj4_owuduhjR0RCUBqfrg0w@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1077 bytes --]
> >> The following patch fixes the deadlock. When the quota subsystem takes s_umount,
> >> it checks if the filesystem is frozen. If it is, we drop s_umount, wait for
> >> the filesystem to resume and retry.
> > Thanks for the patch. I'm aware of the deadlock and Val Henson is working
> > on resolving these types of deadlocks more systematically. But since I
> > haven't heard from her for a while, I guess I'll merge your fix and she'll
> > update her series to reflect your change since those patches are going to
> > go in at earliest in the next merge window.
> > To sum up: I've merged your patch.
>
> FYI, I no longer have time to consult in addition to my full-time job.
> Canonical is taking over this patch set.
>
> -VAL
Hi
Where can I get that patch set?
We are experiencing other similar deadlocks on RHEL-6, caused by sync or
background writeback (these code paths take s_umount and wait trying to do
I/O), but I wasn't able to reproduce these deadlocks on upstream kernel?
Are there other known deadlock possibilities?
Mikulas
next prev parent reply other threads:[~2011-11-28 21:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 20:25 [PATCH] deadlock with suspend and quotas Mikulas Patocka
2011-11-28 15:04 ` Jan Kara
2011-11-28 21:00 ` Valerie Aurora
2011-11-28 21:14 ` Mikulas Patocka [this message]
2011-11-28 23:32 ` Mikulas Patocka
2011-11-29 10:19 ` Jan Kara
2011-11-29 10:21 ` Jan Kara
2011-11-29 11:06 ` Mikulas Patocka
2011-11-29 11:11 ` Jan Kara
2011-11-29 12:54 ` Mikulas Patocka
2011-11-29 13:09 ` Jan Kara
2011-11-29 13:18 ` [dm-devel] " Alasdair G Kergon
2011-11-29 13:32 ` Jan Kara
2011-11-29 16:33 ` Eric Sandeen
2011-11-30 6:52 ` Mikulas Patocka
2011-11-30 11:16 ` Jan Kara
2011-11-30 12:14 ` Mikulas Patocka
2011-11-30 13:05 ` Alasdair G Kergon
2011-11-30 16:53 ` Jan Kara
2011-11-30 17:09 ` Mikulas Patocka
2011-11-30 13:33 ` Alasdair G Kergon
2011-11-30 13:48 ` Alasdair G Kergon
2011-11-30 16:36 ` Mikulas Patocka
2011-11-30 16:34 ` Mikulas Patocka
2011-12-01 0:34 ` Jan Kara
2011-11-30 14:09 ` Alasdair G Kergon
2011-11-30 16:53 ` Mikulas Patocka
2011-12-01 0:03 ` Jan Kara
2011-11-30 17:03 ` Mikulas Patocka
2011-11-29 20:00 ` Kamal Mostafa
2012-01-03 3:30 ` Al Viro
2012-01-03 18:22 ` Mikulas Patocka
2012-01-03 18:35 ` Mikulas Patocka
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=Pine.LNX.4.64.1111281612030.11895@hs20-bc2-1.build.redhat.com \
--to=mpatocka@redhat.com \
--cc=christopher.chaltain@canonical.com \
--cc=dm-devel@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=val@vaaconsulting.com \
/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).