From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16278] lvm snapshot causes deadlock in 2.6.35
Date: Thu, 24 Jun 2010 15:28:00 GMT [thread overview]
Message-ID: <201006241528.o5OFS0wa016781@demeter.kernel.org> (raw)
In-Reply-To: <bug-16278-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16278
--- Comment #1 from Eric Sandeen <sandeen@redhat.com> 2010-06-24 15:27:57 ---
Created an attachment (id=26933)
--> (https://bugzilla.kernel.org/attachment.cgi?id=26933)
Proposed patch
I've sent this patch upstream, I think it should solve the most egregious
problem here, though I think other deadlocks remain (looking as if they are
unrelated to the commit mentioned in the original comment)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-06-24 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 16:55 [Bug 16278] New: lvm snapshot causes deadlock in 2.6.35 bugzilla-daemon
2010-06-24 15:28 ` bugzilla-daemon [this message]
2010-06-24 15:28 ` [Bug 16278] " bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2010-07-08 23:33 2.6.35-rc4-git3: Reported regressions from 2.6.34 Rafael J. Wysocki
2010-07-08 23:41 ` [Bug #16278] lvm snapshot causes deadlock in 2.6.35 Rafael J. Wysocki
2010-07-23 11:42 2.6.35-rc6: Reported regressions from 2.6.34 Rafael J. Wysocki
2010-07-23 11:47 ` [Bug #16278] lvm snapshot causes deadlock in 2.6.35 Rafael J. Wysocki
2010-07-23 11:47 ` Rafael J. Wysocki
2010-08-01 13:46 2.6.35-rc6-git6: Reported regressions from 2.6.34 Rafael J. Wysocki
2010-08-01 13:52 ` [Bug #16278] lvm snapshot causes deadlock in 2.6.35 Rafael J. Wysocki
2010-08-01 13:52 ` Rafael J. Wysocki
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=201006241528.o5OFS0wa016781@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.