From owner-freebsd-testing@freebsd.org Tue May 9 21:21:16 2017 Return-Path: Delivered-To: freebsd-testing@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 B3650D664F9 for ; Tue, 9 May 2017 21:21:16 +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 A273A7D7 for ; Tue, 9 May 2017 21:21:16 +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 v49LLF7a030474 for ; Tue, 9 May 2017 21:21:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-testing@freebsd.org Subject: [Bug 217261] sys/aio/aio_test:aio_md_test fails semi-frequently with Jenkins with "aio_write failed: Operation not supported" Date: Tue, 09 May 2017 21:21:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: tests X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-testing@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 May 2017 21:21:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217261 --- Comment #6 from John Baldwin --- (In reply to Ngie Cooper from comment #4) Block devices don't exist in FreeBSD. VSOCK would not show up here either = as those would use a socket fileops which has a custom fo_aio_queue method. Character devices that are disks (like /dev/mdX) are handled in aio_qphysio= ().=20 If you hit a resource limit on the number of "physio" requests queued (the check against 'kaio_ballowed_count' e.g.) then request will fall through and trigger the unsafe check. Arguably we should be failing with EAGAIN from aio_qphysio() and then flipping the '#if 0' in aio_queue_file() so that err= or gets returned directly rather than trying to re-queue the request via the helper kprocs. All other VCHR are considered unsafe. We could at some point provide a way= for character devices to claim AIO requests via something like fo_aio_queue. N= ote that ptys already have their own 'struct fileops' and could easily provide a custom f_aio_queue() along with custom AIO handling to make them "safe". I'm not sure why kib@ added the VDIR check as I'm not sure any of the curre= nt AIO operations (fsync, read, write) make any sense on directories. However, this probably just means that they are allowed to fail with EISDIR rather t= han EOPNOTSUPP. --=20 You are receiving this mail because: You are the assignee for the bug.=