public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alex Villací­s Lasso" <a_villacis@palosanto.com>
To: Seth Jennings <sjenning@linux.vnet.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dan Magenheimer <dan.magenheimer@oracle.com>
Subject: Re: Fwd: Deadlock warning in 3.3-rc4 in zcache code when running transmission-gtk
Date: Thu, 23 Feb 2012 10:04:27 -0500	[thread overview]
Message-ID: <4F46557B.9080901@palosanto.com> (raw)
In-Reply-To: <4F451B02.8030201@linux.vnet.ibm.com>

El 22/02/12 11:42, Seth Jennings escribió:
> On 02/22/2012 10:20 AM, Alex Villací­s Lasso wrote:
>> I am getting (potential?) deadlock warnings in zcache code shortly after
>> running transmission-gtk, the bittorrent client. My / partition is ext4,
>> and /home and /DATA (where some torrents are stored) are ext3 mounted
>> with ext4 subsystem. The warning has triggered twice so far, always
>> after running transmission-gtk.
>>
>> Fedora 16 x86_64, vanilla linux 3.3-rc4.
>> Deadlock warning did not appear in 3.3-rc3.
> This may have already been identified and fixed by this patch:
> https://lkml.org/lkml/2012/2/20/155
>
> Let me know if that doesn't fix it.
>
> --
> Seth
>
The patch indeed fixes the bug.

      reply	other threads:[~2012-02-23 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-21  1:27 Deadlock warning in 3.3-rc4 in zcache code when running transmission-gtk Alex Villacís Lasso
     [not found] ` <4F4515EA.2090909@palosanto.com>
2012-02-22 16:42   ` Fwd: " Seth Jennings
2012-02-23 15:04     ` Alex Villací­s Lasso [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=4F46557B.9080901@palosanto.com \
    --to=a_villacis@palosanto.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sjenning@linux.vnet.ibm.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