linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Pyrgiotis <apyrgio-Hpc4xzY4zrDSDkk6z29a7FAUjnlXr6A1@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Did I hear anyone say "deadlock"?
Date: Sat, 08 Sep 2012 22:04:51 +0300	[thread overview]
Message-ID: <504B96D3.9020802@cslab.ece.ntua.gr> (raw)

Hi Kent and list,

I may have stumbled upon a deadlock in the latest code for bcache. Since 
I see this is a hot issue between you and the guys working on dm, you 
might want to take a look.

I have compiled your latest commit in master branch 
(66f5a1f7311d5cc24bdff876ca2cfed88a3cc5d1) and running it raw on my home 
laptop - not using a VM or something.
For benchmarking reasons, I'm using a RAMdisk (brd module) as a cache 
set for an HDD disk. These are the steps that I take:

# Load ramdisks with max size 2.5GB (/dev/ram[0-15])
modprobe brd rd_size=2621440

#Format ramdisk as bcache cache set
make-bcache -C /dev/ram0

#Register the cache set
echo /dev/ram0 > /sys/fs/bcache/register

The last command fails to finish. The system hangs and nothing gets to 
be written in kern.log.
On the other hand, on another bcache kernel that is installed in the 
same system, everything runs smoothly. This kernel was taken from the 
bcache-dev branch and based on linux kernel version 3.5.0 rc2.

It is probably not a big issue, but i thought it'd be helpful to share it.
So, is the proposed code somewhere in your git tree? In this case, I 
could try it out and check if this problem is solved.

Thanks,
Alex

                 reply	other threads:[~2012-09-08 19:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=504B96D3.9020802@cslab.ece.ntua.gr \
    --to=apyrgio-hpc4xzy4zrdsdkk6z29a7faujnlxr6a1@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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).