From: Roman Mamedov <rm@romanrm.net>
To: Roman Mamedov <rm@romanrm.net>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Reproduced deadlock after upgrade from 3.18 to 4.1 or 4.3 (+ more info)
Date: Mon, 25 Jan 2016 20:53:21 +0500 [thread overview]
Message-ID: <20160125205321.51b002ba@natsu> (raw)
In-Reply-To: <20160110053119.45e05246@natsu>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
On Sun, 10 Jan 2016 05:31:19 +0500
Roman Mamedov <rm@romanrm.net> wrote:
> After this case I went back to 3.18.25, and the system worked fine for about 2
> weeks more. However now I decided to try upgrading again, this time to 4.3.3 -
> and hit the deadlock on the very first attempt to use the same script.
For the record, this does not happen after upgrade to 4.4.0.
It seems only 4.1 and 4.3 series are affected.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2016-01-25 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 2:00 Deadlock after upgrade to 4.1 Roman Mamedov
2015-12-26 4:04 ` Duncan
2015-12-26 4:34 ` Chris Murphy
2015-12-29 13:24 ` Rich Freeman
2016-01-10 0:31 ` Reproduced deadlock after upgrade from 3.18 to 4.1 or 4.3 (+ more info) Roman Mamedov
2016-01-25 15:53 ` Roman Mamedov [this message]
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=20160125205321.51b002ba@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).