All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: hpa@zytor.com, bernd.schubert@itwm.fraunhofer.de,
	JBottomley@Parallels.com, LKML <linux-kernel@vger.kernel.org>,
	Kamal Mostafa <kamal.mostafa@canonical.com>,
	linux-scsi@vger.kernel.org,
	Luis Henriques <luis.henriques@canonical.com>
Subject: Re: Subject:  [v3.8][v3.11][Regression] [SCSI] sd: Update WRITE SAME heuristics
Date: Tue, 29 Oct 2013 15:41:58 -0400	[thread overview]
Message-ID: <52700F86.4010007@interlog.com> (raw)
In-Reply-To: <52700AD2.6000703@canonical.com>

On 13-10-29 03:21 PM, Joseph Salisbury wrote:
> Hi Martin,
>
> A bug was opened against the Ubuntu kernel[0].  After a kernel bisect,
> it was found that reverting the following commit resolved this bug:
>
> commit 66c28f97120e8a621afd5aa7a31c4b85c547d33d
> Author: Martin K. Petersen <martin.petersen@oracle.com>
> Date:   Thu Jun 6 22:15:55 2013 -0400
>
>      [SCSI] sd: Update WRITE SAME heuristics
>
>
> The regression was introduced as of v3.11-rc1, but it also made it's way
> into the stable trees.
>
> I see that you are the author of this patch, so I wanted to run this by
> you.  I was thinking of requesting a revert for v3.12, but I wanted to
> get your feedback first.
>
>
> Thanks,
>
> Joe
>
> [0] http://pad.lv/1237392

Tried the other approach?

 From your bug report: "Areca Raid Controller2: F/W v1.46 ...(etc)..."

Then see:
   http://www.areca.com.tw/support/main.htm

Doug Gilbert

  reply	other threads:[~2013-10-29 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 19:21 Subject: [v3.8][v3.11][Regression] [SCSI] sd: Update WRITE SAME heuristics Joseph Salisbury
2013-10-29 19:41 ` Douglas Gilbert [this message]
2013-10-29 19:53   ` Joseph Salisbury
2013-10-29 19:46 ` Bernd Schubert
2013-10-29 19:50   ` Joseph Salisbury
2013-10-30 19:28   ` Joseph Salisbury
2013-10-31  0:02     ` H. Peter Anvin

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=52700F86.4010007@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=JBottomley@Parallels.com \
    --cc=bernd.schubert@itwm.fraunhofer.de \
    --cc=hpa@zytor.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=kamal.mostafa@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.