From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 29162] Reiserfs hang with dataloss sometimes
Date: Mon, 06 Jan 2014 16:05:36 +0000 [thread overview]
Message-ID: <bug-29162-695-OHdAbdnAbt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-29162-695@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=29162
--- Comment #59 from Jeff Mahoney <jeffm@suse.com> ---
(In reply to D.K. from comment #58)
> I just pulled git from torvalds tree and the changes listed by Jeff Mahoney
> are not in there. Also the patches do not apply cleanly.
Yeah they are:
d2d0395fd1778d4bf714adc5bfd23a5d748d7802 reiserfs: locking, release lock around
quota operations
278f6679f454bf185a07d9a4ca355b153482d17a reiserfs: locking, handle nested locks
properly
4c05141df57f4ffc1a9a28f1925434924179bfe4 reiserfs: locking, push write lock out
of xattr code
a1457c0ce976bad1356b9b0437f2a5c3ab8a9cfc reiserfs: fix deadlock with nfs racing
on create/lookup
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-01-06 16:05 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 9:36 [Bug 29162] New: Reiserfs hang with dataloss sometimes bugzilla-daemon
2011-02-15 9:38 ` [Bug 29162] " bugzilla-daemon
2011-02-15 9:39 ` bugzilla-daemon
2011-02-15 9:39 ` bugzilla-daemon
2011-02-15 9:41 ` bugzilla-daemon
2011-02-15 9:44 ` bugzilla-daemon
2011-02-15 9:45 ` bugzilla-daemon
2011-02-15 9:47 ` bugzilla-daemon
2011-03-08 20:44 ` bugzilla-daemon
2011-03-15 3:13 ` bugzilla-daemon
2011-03-15 22:03 ` bugzilla-daemon
2011-03-28 9:33 ` bugzilla-daemon
2011-04-17 18:08 ` bugzilla-daemon
2011-05-02 16:11 ` bugzilla-daemon
2011-05-11 14:54 ` bugzilla-daemon
2011-05-13 13:09 ` bugzilla-daemon
2011-05-17 7:16 ` bugzilla-daemon
2011-05-17 9:19 ` bugzilla-daemon
2011-05-17 13:15 ` bugzilla-daemon
2011-05-21 14:37 ` bugzilla-daemon
2011-05-21 14:38 ` bugzilla-daemon
2011-05-22 11:06 ` bugzilla-daemon
2011-05-23 13:06 ` bugzilla-daemon
2011-05-23 13:11 ` bugzilla-daemon
2011-05-23 16:33 ` bugzilla-daemon
2011-05-23 16:35 ` bugzilla-daemon
2011-05-23 16:38 ` bugzilla-daemon
2011-05-23 18:54 ` bugzilla-daemon
2011-05-23 20:02 ` bugzilla-daemon
2011-06-07 14:23 ` bugzilla-daemon
2011-06-10 12:41 ` bugzilla-daemon
2011-06-11 17:29 ` bugzilla-daemon
2011-06-11 17:32 ` bugzilla-daemon
2011-06-13 15:10 ` bugzilla-daemon
2011-06-13 21:37 ` bugzilla-daemon
2011-06-14 9:14 ` bugzilla-daemon
2011-06-14 9:16 ` bugzilla-daemon
2011-06-20 7:38 ` bugzilla-daemon
2011-08-21 13:00 ` bugzilla-daemon
2011-08-21 14:11 ` bugzilla-daemon
2011-08-21 15:18 ` bugzilla-daemon
2011-08-22 12:34 ` bugzilla-daemon
2011-09-08 12:48 ` bugzilla-daemon
2012-02-06 18:57 ` bugzilla-daemon
2012-04-12 11:32 ` bugzilla-daemon
2012-06-06 8:32 ` bugzilla-daemon
2013-02-11 22:17 ` bugzilla-daemon
2013-02-18 19:45 ` bugzilla-daemon
2013-02-27 9:27 ` bugzilla-daemon
2013-03-02 10:36 ` bugzilla-daemon
2013-04-17 12:17 ` bugzilla-daemon
2013-05-11 15:03 ` bugzilla-daemon
2013-05-11 15:23 ` bugzilla-daemon
2013-05-11 15:51 ` bugzilla-daemon
2013-05-11 16:11 ` bugzilla-daemon
2013-05-30 21:54 ` bugzilla-daemon
2013-05-30 21:55 ` bugzilla-daemon
2013-09-20 19:23 ` bugzilla-daemon
2013-09-21 23:39 ` bugzilla-daemon
2013-12-18 21:01 ` bugzilla-daemon
2013-12-18 21:08 ` bugzilla-daemon
2013-12-20 22:41 ` bugzilla-daemon
2013-12-20 22:44 ` bugzilla-daemon
2014-01-05 19:47 ` bugzilla-daemon
2014-01-05 22:02 ` bugzilla-daemon
2014-01-06 16:05 ` bugzilla-daemon [this message]
2014-01-06 16:07 ` bugzilla-daemon
2014-01-06 18:45 ` bugzilla-daemon
2014-01-28 21:45 ` bugzilla-daemon
2014-02-04 20:20 ` bugzilla-daemon
2014-02-04 20:21 ` bugzilla-daemon
2014-02-04 20:22 ` bugzilla-daemon
2015-02-25 21:22 ` bugzilla-daemon
2015-04-07 10:05 ` bugzilla-daemon
2015-04-07 16:03 ` bugzilla-daemon
2016-02-16 22:05 ` 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=bug-29162-695-OHdAbdnAbt@https.bugzilla.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 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.