public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
To: Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>
Cc: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Negative stats value
Date: Fri, 12 Jul 2013 10:20:22 +0200	[thread overview]
Message-ID: <51DFBC46.60906@profihost.ag> (raw)
In-Reply-To: <20130712081601.GA8339@kmo-pixel>

Am 12.07.2013 10:16, schrieb Kent Overstreet:
> On Fri, Jul 12, 2013 at 07:13:32AM +0200, Stefan Priebe - Profihost AG wrote:
>> Am 12.07.2013 um 03:28 schrieb Kent Overstreet <kmo-PEzghdH756F8UrSeD/g0lQ@public.gmane.org>:
>>
>>> On Thu, Jul 11, 2013 at 07:32:05AM +0200, Stefan Priebe - Profihost AG wrote:
>>>> I've seen negative dirty cache values several times. Is there a fix available?
>>>
>>> Yeah, this should be fixed in the bcache-for-3.11 branch - but it's
>>> harmless in the meantime.
>>
>> Any special fix I can apply on top of 3.10?
> 
> http://evilpiepirate.org/git/linux-bcache.git/commit/?h=bcache-for-3.11&id=444fc0b6b167ed164e7436621a9d095e042644dd

THX.

Stefan

      reply	other threads:[~2013-07-12  8:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  5:32 Negative stats value Stefan Priebe - Profihost AG
     [not found] ` <103FE78F-7B2E-4B2F-83E6-51D2DEE33BB3-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12  1:28   ` Kent Overstreet
2013-07-12  5:13     ` Stefan Priebe - Profihost AG
     [not found]       ` <4FAB0670-07BD-4E8F-AD0E-A4CA5572A7EC-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12  8:16         ` Kent Overstreet
2013-07-12  8:20           ` Stefan Priebe - Profihost AG [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=51DFBC46.60906@profihost.ag \
    --to=s.priebe-2lf/h1ldwehr5kwtpvns9a@public.gmane.org \
    --cc=kmo-PEzghdH756F8UrSeD/g0lQ@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