From owner-freebsd-amd64@freebsd.org  Wed Mar 30 14:00:13 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D9B2AE382A
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed, 30 Mar 2016 14:00:13 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5ECB91471
 for <freebsd-amd64@FreeBSD.org>; Wed, 30 Mar 2016 14:00:13 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2UE0D6a065723
 for <freebsd-amd64@FreeBSD.org>; Wed, 30 Mar 2016 14:00:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 208365] [umass] Cannot fsck 3TB USB disk
Date: Wed, 30 Mar 2016 14:00:13 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: royger@freebsd.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: royger@freebsd.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-208365-6-QzVXtVBwDW@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-208365-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-208365-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 30 Mar 2016 14:38:01 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2016 14:00:13 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208365

--- Comment #16 from Roger Pau Monn=C3=83=C2=A9 <royger@freebsd.org> ---
(In reply to Hans Petter Selasky from comment #15)

Yes, there are several optimizations that can be applied in order to improve
the patch. As I've noted in the comment, this is just an initial approach to
make sure the problem is caused by not bouncing the whole region (and then =
the
offsets don't match anymore).

Regarding the "again" label, I'm not really sure we can get rid of it, for =
the
mapped case (_bus_dmamap_count_pages) it looks like we can remove it, but f=
or
the other cases it depends on whether maxsegsz is a multiple of a PAGE_SIZE=
, or
else we might end up with segments that don't have consecutive offsets AFAI=
CT.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=