public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Vineet Agarwal <checkout.vineet@gmail.com>,
	James Bottomley <James.Bottomley@suse.de>
Cc: linux-scsi <linux-scsi@vger.kernel.org>, open-osd <osd-dev@open-osd.org>
Subject: Re: [PATCH 0/1] libosd bug fixing
Date: Wed, 02 Dec 2009 19:16:10 +0200	[thread overview]
Message-ID: <4B16A0DA.5080205@panasas.com> (raw)
In-Reply-To: <425904320912020131k46b34cdfmfa64a25196a5b44e@mail.gmail.com>

On 12/02/2009 11:31 AM, Vineet Agarwal wrote:
> Hi Boaz,
> 
> On Tue, Dec 1, 2009 at 9:00 PM, Boaz Harrosh <bharrosh@panasas.com
> <mailto:bharrosh@panasas.com>> wrote:
> 
>     James hi.
> 
>     Users have found an annoying bug in latest osd/exofs code. Actually this
>     deficiency exists for a long time, but only most recent exofs code has
>     exposed it.
> 
>     Please include the fix to the patches queued for 2.6.33. No need for it
>     to go into stable as current users will not hit it.
> 
>     [PATCH 1/1] libosd: Fix blk_put_request locking again
> 
>     Vineet Please test this new patch, the previous fix was crap
> 
> I applied the patch and it's working at my end.
> 

Thank you Vineet for testing. I was also able to reproduce the same problem
you had, and now it runs smoothly.

James please submit for 2.6.33. It is an important bug fix for the exofs code
that I want to push for next merge window.

Boaz
>     Thanks
>     Boaz
> 
> Regards:
> Vineet Agarwal
> 


      parent reply	other threads:[~2009-12-02 17:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 15:30 [PATCH 0/1] libosd bug fixing Boaz Harrosh
2009-12-01 15:36 ` [PATCH 1/1] libosd: Fix blk_put_request locking again Boaz Harrosh
2009-12-03  8:59   ` Boaz Harrosh
2009-12-10 11:53     ` Boaz Harrosh
     [not found] ` <425904320912020131k46b34cdfmfa64a25196a5b44e@mail.gmail.com>
2009-12-02  9:35   ` [PATCH 0/1] libosd bug fixing Vineet Agarwal
2009-12-02 17:16   ` Boaz Harrosh [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=4B16A0DA.5080205@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@suse.de \
    --cc=checkout.vineet@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=osd-dev@open-osd.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