mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Joseph Salisbury <joseph.salisbury@canonical.com>, hch@lst.de
Cc: jejb@linux.vnet.ibm.com, martin.petersen@oracle.com,
	jthumshirn@suse.de, bart.vanassche@wdc.com,
	bblock@linux.vnet.ibm.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, jth@kernel.org,
	stable@vger.kernel.org, gregkh@linuxfoundation.org,
	1726519@bugs.launchpad.net
Subject: Re: [REGRESSION][v4.13.y][v4.14.y] scsi: libsas: allow async aborts
Date: Fri, 17 Nov 2017 15:09:37 +0100	[thread overview]
Message-ID: <100fda00-3da4-1bf1-eaf2-fc0b4fb4fe37@suse.de> (raw)
In-Reply-To: <27d1c9b1-9a80-4982-290b-3916d6e5c80f@canonical.com>

On 11/16/2017 11:08 PM, Joseph Salisbury wrote:
> Hi Christoph,
> 
> A kernel bug report was opened against Ubuntu [0].  After a kernel
> bisect, it was found that reverting the following commit resolved this bug:
> 
> 909657615d9b ("scsi: libsas: allow async aborts")
> 
>      
> The regression was introduced as of v4.12-rc1, and it still exists in
> 4.14 mainline.
> 
> I was hoping to get your feedback, since you are the patch author.  Do
> you think gathering any additional data will help diagnose this issue,
> or would it be best to submit a revert request?
> 
I'll be checking what's going on there.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		   Teamlead Storage & Networking
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

  reply	other threads:[~2017-11-17 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 22:08 Joseph Salisbury
2017-11-17 14:09 ` Hannes Reinecke [this message]
2017-12-05  8:57   ` Fabian Grünbichler

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=100fda00-3da4-1bf1-eaf2-fc0b4fb4fe37@suse.de \
    --to=hare@suse.de \
    --cc=1726519@bugs.launchpad.net \
    --cc=bart.vanassche@wdc.com \
    --cc=bblock@linux.vnet.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=jth@kernel.org \
    --cc=jthumshirn@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stable@vger.kernel.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

all inboxes | Powered by JetHome®