linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ewan Milne <emilne@redhat.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Laurence Oberman <loberman@redhat.com>,
	Eyal Ben David <bdeyal@gmail.com>,
	dgilbert@interlog.com, linux-scsi@vger.kernel.org
Subject: Re: SG does not ignore dxferp (direct io + mmap)
Date: Fri, 25 Nov 2016 12:56:16 -0500 (EST)	[thread overview]
Message-ID: <1194718949.74785.1480096576577.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20161125080758.5bh5jkcgvhw3xuvb@linux-x5ow.site>

>> ---
>> 
>> In other words, this commit made the bad behavior go away in 4.8.
>> Need to look at this in more detail, it doesn't appear as if this patch
>> was intended to fix such a problem.
>> 
>> -Ewan
>
>Are you sure it did? I can repropduce copy_to_user() errors with 4.8 as well.
>Using the very same reproducer. On 4.8 it's just harder to trigger and
>doesn't trigger on AHCI as fas as I can telli (maybe I just haven't hit
>it hard enough). I can trigger it on QEMUs SCSI CDROM emulation and hpsa
>though. I cannot however trigger this with a minimal config inside an initrd.

It did for Eyal's supplied test case on my machine, but that was not an
exhaustive test, and I am a little suspicious that the behavior change was
due to a side-effect of the patch rather than actually fixing something.

I think what we need to understand is what caused the regression in the
first place, I probably should have been bisecting the original failure
rather than trying to find where it started working.

I was running against an internal (physical) drive.

-Ewan

  parent reply	other threads:[~2016-11-25 17:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-20 16:02 SG does not ignore dxferp (direct io + mmap) Eyal Ben David
2016-11-21  0:04 ` Laurence Oberman
2016-11-21  9:23   ` Eyal Ben David
2016-11-21 14:24     ` Ewan D. Milne
2016-11-21 14:54       ` Laurence Oberman
2016-11-21 14:55       ` Eyal Ben David
2016-11-21 15:12         ` Laurence Oberman
2016-11-21 15:15         ` Johannes Thumshirn
2016-11-21 15:44           ` Johannes Thumshirn
2016-11-21 16:04             ` Eyal Ben David
2016-11-21 16:25           ` Ewan D. Milne
2016-11-21 17:34       ` Douglas Gilbert
2016-11-21 18:24         ` Ewan D. Milne
2016-11-22  8:37           ` Johannes Thumshirn
2016-11-22 13:48             ` Eyal Ben David
2016-11-22 15:31               ` Laurence Oberman
2016-11-22 16:00                 ` Johannes Thumshirn
2016-11-22 16:28                   ` Eyal Ben David
2016-11-22 18:30             ` Ewan D. Milne
2016-11-22 18:46               ` Laurence Oberman
2016-11-22 20:55               ` Eyal Ben David
2016-11-23 18:55                 ` Laurence Oberman
2016-11-23 20:22                   ` Ewan D. Milne
2016-11-25  8:07                     ` Johannes Thumshirn
2016-11-25 11:20                       ` Eyal Ben David
2016-11-25 11:53                         ` Johannes Thumshirn
2016-11-25 12:28                           ` Johannes Thumshirn
2016-11-25 12:36                           ` Eyal Ben David
2016-11-25 14:46                             ` Laurence Oberman
2016-11-28 10:30                               ` Johannes Thumshirn
2016-11-25 17:56                       ` Ewan Milne [this message]
2016-11-25 18:01                         ` Laurence Oberman
2016-11-30 16:26                         ` Ewan D. Milne
2016-12-01 13:40                           ` Martin K. Petersen
2016-12-02 12:21                             ` Christoph Hellwig
2016-12-02 13:29                               ` Ewan D. Milne
2016-12-02 14:10                                 ` Hannes Reinecke
2016-12-02 14:17                                   ` Laurence Oberman
2016-12-02 19:29                                   ` Ewan D. Milne
2016-12-02 20:37                             ` Ewan D. Milne

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=1194718949.74785.1480096576577.JavaMail.zimbra@redhat.com \
    --to=emilne@redhat.com \
    --cc=bdeyal@gmail.com \
    --cc=dgilbert@interlog.com \
    --cc=jthumshirn@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=loberman@redhat.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 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).