From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 01:10:14 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3337D10656CD for ; Sat, 1 Jan 2011 01:10:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0358FC37 for ; Sat, 1 Jan 2011 01:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p011ACrG012306 for ; Sat, 1 Jan 2011 01:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p011AC4T012305; Sat, 1 Jan 2011 01:10:12 GMT (envelope-from gnats) Resent-Date: Sat, 1 Jan 2011 01:10:12 GMT Resent-Message-Id: <201101010110.p011AC4T012305@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Raphael Kubo da Costa Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1EFC106564A for ; Sat, 1 Jan 2011 01:02:23 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (unknown [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id A12548FC12 for ; Sat, 1 Jan 2011 01:02:23 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p0112NVM063555 for ; Sat, 1 Jan 2011 01:02:23 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p0112NJf063554; Sat, 1 Jan 2011 01:02:23 GMT (envelope-from nobody) Message-Id: <201101010102.p0112NJf063554@red.freebsd.org> Date: Sat, 1 Jan 2011 01:02:23 GMT From: Raphael Kubo da Costa To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/153594: iwn: Network keeps disconnecting when /etc/rc.d/netif restart is run X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 01:10:14 -0000 >Number: 153594 >Category: kern >Synopsis: iwn: Network keeps disconnecting when /etc/rc.d/netif restart is run >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 01 01:10:12 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Raphael Kubo da Costa >Release: FreeBSD 8.2-PRERELEASE >Organization: >Environment: FreeBSD gibbon 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #23: Wed Dec 29 01:41:46 BRST 2010 root@gibbon:/usr/obj/usr/src/sys/GIBBON amd64 >Description: My wireless network card is an Intel PRO/Wireless 5100, and I'm using the iwn driver. /etc/rc.conf contains the following: wlans_iwn0="wlan0" ifconfig_wlan0="WPA SYNCDHCP" And /etc/wpa_supplicat.conf has the appropriate settings for some access points. When the system boots, the network is established correctly, but whenever I need to restart it via '/etc/rc.d/netif restart', when I ping my access point around 10 packets are sent before the network goes down and 'ifconfig wlan0' shows it is looking for different APs (or even the same AP in diverse channels, for example). When a connection is established to the AP again, it goes down after a few seconds again. If I do '/etc/rc.d/netif restart' again, the connection stops dropping. >How-To-Repeat: /etc/rc.d/netif restart >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 16:00:21 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92905106566C for ; Sat, 1 Jan 2011 16:00:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4A3E38FC0A for ; Sat, 1 Jan 2011 16:00:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01G0LRV095066 for ; Sat, 1 Jan 2011 16:00:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01G0LH3095065; Sat, 1 Jan 2011 16:00:21 GMT (envelope-from gnats) Resent-Date: Sat, 1 Jan 2011 16:00:21 GMT Resent-Message-Id: <201101011600.p01G0LH3095065@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, CyberLeo Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4998106564A for ; Sat, 1 Jan 2011 15:51:38 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (unknown [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id B962F8FC0A for ; Sat, 1 Jan 2011 15:51:38 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p01FpcED023768 for ; Sat, 1 Jan 2011 15:51:38 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p01Fpc7w023767; Sat, 1 Jan 2011 15:51:38 GMT (envelope-from nobody) Message-Id: <201101011551.p01Fpc7w023767@red.freebsd.org> Date: Sat, 1 Jan 2011 15:51:38 GMT From: CyberLeo To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: misc/153599: Feiya Elango USB MicroSD reader synchronize cache quirk X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 16:00:21 -0000 >Number: 153599 >Category: misc >Synopsis: Feiya Elango USB MicroSD reader synchronize cache quirk >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 01 16:00:20 UTC 2011 >Closed-Date: >Last-Modified: >Originator: CyberLeo >Release: 8.2-RC1 >Organization: CyberLeo.Net >Environment: FreeBSD albanew.cyberleo.net 8.2-RC1 FreeBSD 8.2-RC1 #0 r216852+4500366: Sat Jan 1 05:20:15 UTC 2011 cyberleo@albanew.cyberleo.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: A Feyia Elango USB2.0 MicroSDHC reader, when attached to a FreeBSD machine, spills this into the kernel log: ugen0.2: at usbus0 uplcom0: on usbus0 umass0:10:0:-1: Attached to scbus10 Trying to mount root from zfs:alba/root da0 at umass-sim0 bus 0 scbus10 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 59MB (122624 512 byte sectors: 64H 32S/T 59C) (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): SCSI sense: Error code 0x52 (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): SCSI sense: Error code 0x52 .. followed by 11 more of the same error. Included patch silences the errors. >How-To-Repeat: >Fix: Date: Sat, 1 Jan 2011 03:56:16 +0000 Subject: [PATCH] [CDN-Patch] Add Feiya Elango no_synchronize_cache quirk --- sys/dev/usb/quirk/usb_quirk.c | 1 + sys/dev/usb/usbdevs | 1 + 2 files changed, 2 insertions(+), 0 deletions(-) diff --git a/sys/dev/usb/quirk/usb_quirk.c b/sys/dev/usb/quirk/usb_quirk.c index 6691538..d24ae71 100644 --- a/sys/dev/usb/quirk/usb_quirk.c +++ b/sys/dev/usb/quirk/usb_quirk.c @@ -458,6 +458,7 @@ static struct usb_quirk_entry usb_quirks[USB_DEV_QUIRKS_MAX] = { USB_QUIRK(CHIPSBANK, USBMEMSTICK, 0x0000, 0xffff, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(CHIPSBANK, USBMEMSTICK1, 0x0000, 0xffff, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(NEWLINK, USB2IDEBRIDGE, 0x0000, 0xffff, UQ_MSC_NO_SYNC_CACHE), + USB_QUIRK(FEIYA, ELANGO, 0x0000, 0xffff, UQ_MSC_NO_SYNC_CACHE), }; #undef USB_QUIRK_VP #undef USB_QUIRK diff --git a/sys/dev/usb/usbdevs b/sys/dev/usb/usbdevs index 46cf139..6af5b26 100644 --- a/sys/dev/usb/usbdevs +++ b/sys/dev/usb/usbdevs @@ -1563,6 +1563,7 @@ product EXTENDED XTNDACCESS 0x0100 XTNDAccess IrDA /* FEIYA products */ product FEIYA 5IN1 0x1132 5-in-1 Card Reader +product FEIYA ELANGO 0x6200 MicroSDHC Card Reader /* Fiberline */ product FIBERLINE WL430U 0x6003 WL-430U -- 1.7.3.3 >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 17:00:25 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0219610656B1 for ; Sat, 1 Jan 2011 17:00:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CAA418FC1D for ; Sat, 1 Jan 2011 17:00:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01H0OcT062661 for ; Sat, 1 Jan 2011 17:00:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01H0OAP062652; Sat, 1 Jan 2011 17:00:24 GMT (envelope-from gnats) Date: Sat, 1 Jan 2011 17:00:24 GMT Message-Id: <201101011700.p01H0OAP062652@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/133170: commit references a PR X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 17:00:25 -0000 The following reply was made to PR kern/133170; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/133170: commit references a PR Date: Sat, 1 Jan 2011 16:59:12 +0000 (UTC) Author: brucec Date: Sat Jan 1 16:59:05 2011 New Revision: 216873 URL: http://svn.freebsd.org/changeset/base/216873 Log: There can be more than 0x20000000 swap meta blocks allocated if a swap-backed md(4) device is used. Don't panic when deallocating such a device if swap has been used. PR: kern/133170 Discussed with: kib MFC after: 3 days Modified: head/sys/vm/swap_pager.c Modified: head/sys/vm/swap_pager.c ============================================================================== --- head/sys/vm/swap_pager.c Sat Jan 1 16:47:12 2011 (r216872) +++ head/sys/vm/swap_pager.c Sat Jan 1 16:59:05 2011 (r216873) @@ -1679,8 +1679,6 @@ swap_pager_isswapped(vm_object_t object, } } index += SWAP_META_PAGES; - if (index > 0x20000000) - panic("swap_pager_isswapped: failed to locate all swap meta blocks"); } mtx_unlock(&swhash_mtx); return (0); @@ -1995,8 +1993,6 @@ swp_pager_meta_free_all(vm_object_t obje } mtx_unlock(&swhash_mtx); index += SWAP_META_PAGES; - if (index > 0x20000000) - panic("swp_pager_meta_free_all: failed to locate all swap meta blocks"); } } _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 17:21:16 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C95D31065675; Sat, 1 Jan 2011 17:21:16 +0000 (UTC) (envelope-from brucec@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 582608FC1E; Sat, 1 Jan 2011 17:21:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01HLG5k094913; Sat, 1 Jan 2011 17:21:16 GMT (envelope-from brucec@freefall.freebsd.org) Received: (from brucec@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01HLGDB094900; Sat, 1 Jan 2011 17:21:16 GMT (envelope-from brucec) Date: Sat, 1 Jan 2011 17:21:16 GMT Message-Id: <201101011721.p01HLGDB094900@freefall.freebsd.org> To: bruce@cran.org.uk, brucec@FreeBSD.org, freebsd-bugs@FreeBSD.org, brucec@FreeBSD.org From: brucec@FreeBSD.org Cc: Subject: Re: kern/133170: [md] [panic] panic when detaching swap-backed md(4) disk which has gone into swap X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 17:21:16 -0000 Synopsis: [md] [panic] panic when detaching swap-backed md(4) disk which has gone into swap State-Changed-From-To: open->patched State-Changed-By: brucec State-Changed-When: Sat Jan 1 17:20:48 UTC 2011 State-Changed-Why: Fixed in HEAD. Responsible-Changed-From-To: freebsd-bugs->brucec Responsible-Changed-By: brucec Responsible-Changed-When: Sat Jan 1 17:20:48 UTC 2011 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=133170 From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 17:50:11 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7647310656A3 for ; Sat, 1 Jan 2011 17:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 375EB8FC1D for ; Sat, 1 Jan 2011 17:50:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01HoBUx016586 for ; Sat, 1 Jan 2011 17:50:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01HoB1j016585; Sat, 1 Jan 2011 17:50:11 GMT (envelope-from gnats) Resent-Date: Sat, 1 Jan 2011 17:50:11 GMT Resent-Message-Id: <201101011750.p01HoB1j016585@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Roger Leigh Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABFE1106564A for ; Sat, 1 Jan 2011 17:46:05 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (unknown [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 993F38FC08 for ; Sat, 1 Jan 2011 17:46:05 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p01Hk5SS008491 for ; Sat, 1 Jan 2011 17:46:05 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p01Hk5UQ008490; Sat, 1 Jan 2011 17:46:05 GMT (envelope-from nobody) Message-Id: <201101011746.p01Hk5UQ008490@red.freebsd.org> Date: Sat, 1 Jan 2011 17:46:05 GMT From: Roger Leigh To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: bin/153600: Path length restrictions in mount/umount tools prevent filesystem mount/unmount X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 17:50:11 -0000 >Number: 153600 >Category: bin >Synopsis: Path length restrictions in mount/umount tools prevent filesystem mount/unmount >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 01 17:50:10 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Roger Leigh >Release: 8.2-RC1 >Organization: Debian Project >Environment: FreeBSD freebsd 8.2-RC1 FreeBSD 8.2-RC1 #0: Wed Dec 22 17:34:20 UTC 2010 roo t@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: When mount is asked to mount a filesystem on a node whose absolute path is longer than 85 characters in length, the mount fails. Umount also fails under some circumstances, though the testcase attached below doesn't show this. Please also see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608428 In the Debian report, you'll see that on kfreebsd-amd64 there is some odd behaviour between 80-85 character lengths. Not seen on freebsd 82-RC1, maybe due to version differences, but the main problem is still reproducible on freebsd. The program causing the failures in Debian is schroot, a tool to set up and access chroot environments. This mounts and bind mounts a large number of filesystems in a deep hierarchy which commonly exceeds the 80-85 character limit at which point the freebsd mount/umount start failing. While this tool initially triggered the failures, it's apparently a fundamental flaw in the FreeBSD mount/umount [we've never encountered the issue with the Linux equivalents] >How-To-Repeat: Simple shell script to demonstrate issue: #!/bin/sh chrs="0 1 2 3 4 5 6 7 8 9 a b c d e f 0 1 2 3 4 5 6 7 8 9 a b c d e f 0 1 2 3 4 5 6 7 8 9 a b c d e f 0 1 2 3 4 5 6 7 8 9 a b c d e f 0 1 2 3 4 5 6 7 8 9 a b c d e f 0 1 2 3 4 5 6 7 8 9 a b c d e f 0 1 2 3 4 5 6 7 8 9 a b c d e f 0 1 2 3 4 5 6 7 8 9 a b c d e f" for c in $chrs; do cs="$cs$c" dir="/tmp/$cs" echo "Testing $cs ($(echo -n "$dir" | wc -c) chars)" mkdir "$dir" mount -v -t linprocfs linprocfs "$dir" umount -v "$dir" rmdir "$dir" done Output of script follows. Note mount/umount failure starting at 85 character path length. freebsd# /root/test.sh Testing 0 ( 6 chars) linprocfs on /tmp/0 (linprocfs, local, fsid 51ff000707000000) linprocfs: unmount from /tmp/0 Testing 01 ( 7 chars) linprocfs on /tmp/01 (linprocfs, local, fsid 52ff000707000000) linprocfs: unmount from /tmp/01 Testing 012 ( 8 chars) linprocfs on /tmp/012 (linprocfs, local, fsid 53ff000707000000) linprocfs: unmount from /tmp/012 Testing 0123 ( 9 chars) linprocfs on /tmp/0123 (linprocfs, local, fsid 54ff000707000000) linprocfs: unmount from /tmp/0123 Testing 01234 ( 10 chars) linprocfs on /tmp/01234 (linprocfs, local, fsid 55ff000707000000) linprocfs: unmount from /tmp/01234 Testing 012345 ( 11 chars) linprocfs on /tmp/012345 (linprocfs, local, fsid 56ff000707000000) linprocfs: unmount from /tmp/012345 Testing 0123456 ( 12 chars) linprocfs on /tmp/0123456 (linprocfs, local, fsid 57ff000707000000) linprocfs: unmount from /tmp/0123456 Testing 01234567 ( 13 chars) linprocfs on /tmp/01234567 (linprocfs, local, fsid 58ff000707000000) linprocfs: unmount from /tmp/01234567 Testing 012345678 ( 14 chars) linprocfs on /tmp/012345678 (linprocfs, local, fsid 59ff000707000000) linprocfs: unmount from /tmp/012345678 Testing 0123456789 ( 15 chars) linprocfs on /tmp/0123456789 (linprocfs, local, fsid 5aff000707000000) linprocfs: unmount from /tmp/0123456789 Testing 0123456789a ( 16 chars) linprocfs on /tmp/0123456789a (linprocfs, local, fsid 5bff000707000000) linprocfs: unmount from /tmp/0123456789a Testing 0123456789ab ( 17 chars) linprocfs on /tmp/0123456789ab (linprocfs, local, fsid 5cff000707000000) linprocfs: unmount from /tmp/0123456789ab Testing 0123456789abc ( 18 chars) linprocfs on /tmp/0123456789abc (linprocfs, local, fsid 5dff000707000000) linprocfs: unmount from /tmp/0123456789abc Testing 0123456789abcd ( 19 chars) linprocfs on /tmp/0123456789abcd (linprocfs, local, fsid 5eff000707000000) linprocfs: unmount from /tmp/0123456789abcd Testing 0123456789abcde ( 20 chars) linprocfs on /tmp/0123456789abcde (linprocfs, local, fsid 5fff000707000000) linprocfs: unmount from /tmp/0123456789abcde Testing 0123456789abcdef ( 21 chars) linprocfs on /tmp/0123456789abcdef (linprocfs, local, fsid 60ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef Testing 0123456789abcdef0 ( 22 chars) linprocfs on /tmp/0123456789abcdef0 (linprocfs, local, fsid 61ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0 Testing 0123456789abcdef01 ( 23 chars) linprocfs on /tmp/0123456789abcdef01 (linprocfs, local, fsid 62ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef01 Testing 0123456789abcdef012 ( 24 chars) linprocfs on /tmp/0123456789abcdef012 (linprocfs, local, fsid 63ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef012 Testing 0123456789abcdef0123 ( 25 chars) linprocfs on /tmp/0123456789abcdef0123 (linprocfs, local, fsid 64ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123 Testing 0123456789abcdef01234 ( 26 chars) linprocfs on /tmp/0123456789abcdef01234 (linprocfs, local, fsid 65ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef01234 Testing 0123456789abcdef012345 ( 27 chars) linprocfs on /tmp/0123456789abcdef012345 (linprocfs, local, fsid 66ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef012345 Testing 0123456789abcdef0123456 ( 28 chars) linprocfs on /tmp/0123456789abcdef0123456 (linprocfs, local, fsid 67ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456 Testing 0123456789abcdef01234567 ( 29 chars) linprocfs on /tmp/0123456789abcdef01234567 (linprocfs, local, fsid 68ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef01234567 Testing 0123456789abcdef012345678 ( 30 chars) linprocfs on /tmp/0123456789abcdef012345678 (linprocfs, local, fsid 69ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef012345678 Testing 0123456789abcdef0123456789 ( 31 chars) linprocfs on /tmp/0123456789abcdef0123456789 (linprocfs, local, fsid 6aff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789 Testing 0123456789abcdef0123456789a ( 32 chars) linprocfs on /tmp/0123456789abcdef0123456789a (linprocfs, local, fsid 6bff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789a Testing 0123456789abcdef0123456789ab ( 33 chars) linprocfs on /tmp/0123456789abcdef0123456789ab (linprocfs, local, fsid 6cff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789ab Testing 0123456789abcdef0123456789abc ( 34 chars) linprocfs on /tmp/0123456789abcdef0123456789abc (linprocfs, local, fsid 6dff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abc Testing 0123456789abcdef0123456789abcd ( 35 chars) linprocfs on /tmp/0123456789abcdef0123456789abcd (linprocfs, local, fsid 6eff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcd Testing 0123456789abcdef0123456789abcde ( 36 chars) linprocfs on /tmp/0123456789abcdef0123456789abcde (linprocfs, local, fsid 6fff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcde Testing 0123456789abcdef0123456789abcdef ( 37 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef (linprocfs, local, fsid 70ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef Testing 0123456789abcdef0123456789abcdef0 ( 38 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0 (linprocfs, local, fsid 71ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0 Testing 0123456789abcdef0123456789abcdef01 ( 39 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef01 (linprocfs, local, fsid 72ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef01 Testing 0123456789abcdef0123456789abcdef012 ( 40 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef012 (linprocfs, local, fsid 73ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef012 Testing 0123456789abcdef0123456789abcdef0123 ( 41 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123 (linprocfs, local, fsid 74ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123 Testing 0123456789abcdef0123456789abcdef01234 ( 42 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef01234 (linprocfs, local, fsid 75ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef01234 Testing 0123456789abcdef0123456789abcdef012345 ( 43 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef012345 (linprocfs, local, fsid 76ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef012345 Testing 0123456789abcdef0123456789abcdef0123456 ( 44 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456 (linprocfs, local, fsid 77ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456 Testing 0123456789abcdef0123456789abcdef01234567 ( 45 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef01234567 (linprocfs, local, fsid 78ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef01234567 Testing 0123456789abcdef0123456789abcdef012345678 ( 46 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef012345678 (linprocfs, local, fsid 79ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef012345678 Testing 0123456789abcdef0123456789abcdef0123456789 ( 47 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789 (linprocfs, local, fsid 7aff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789 Testing 0123456789abcdef0123456789abcdef0123456789a ( 48 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789a (linprocfs, local, fsid 7bff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789a Testing 0123456789abcdef0123456789abcdef0123456789ab ( 49 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789ab (linprocfs, local, fsid 7cff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789ab Testing 0123456789abcdef0123456789abcdef0123456789abc ( 50 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abc (linprocfs, local, fsid 7dff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abc Testing 0123456789abcdef0123456789abcdef0123456789abcd ( 51 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcd (linprocfs, local, fsid 7eff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcd Testing 0123456789abcdef0123456789abcdef0123456789abcde ( 52 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcde (linprocfs, local, fsid 7fff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcde Testing 0123456789abcdef0123456789abcdef0123456789abcdef ( 53 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef (linprocfs, local, fsid 80ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef Testing 0123456789abcdef0123456789abcdef0123456789abcdef0 ( 54 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0 (linprocfs, local, fsid 81ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0 Testing 0123456789abcdef0123456789abcdef0123456789abcdef01 ( 55 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef01 (linprocfs, local, fsid 82ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef01 Testing 0123456789abcdef0123456789abcdef0123456789abcdef012 ( 56 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef012 (linprocfs, local, fsid 83ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef012 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123 ( 57 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123 (linprocfs, local, fsid 84ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123 Testing 0123456789abcdef0123456789abcdef0123456789abcdef01234 ( 58 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef01234 (linprocfs, local, fsid 85ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef01234 Testing 0123456789abcdef0123456789abcdef0123456789abcdef012345 ( 59 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef012345 (linprocfs, local, fsid 86ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef012345 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456 ( 60 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456 (linprocfs, local, fsid 87ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456 Testing 0123456789abcdef0123456789abcdef0123456789abcdef01234567 ( 61 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef01234567 (linprocfs, local, fsid 88ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef01234567 Testing 0123456789abcdef0123456789abcdef0123456789abcdef012345678 ( 62 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef012345678 (linprocfs, local, fsid 89ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef012345678 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789 ( 63 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789 (linprocfs, local, fsid 8aff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789a ( 64 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789a (linprocfs, local, fsid 8bff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789a Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab ( 65 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab (linprocfs, local, fsid 8cff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc ( 66 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc (linprocfs, local, fsid 8dff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd ( 67 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd (linprocfs, local, fsid 8eff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde ( 68 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde (linprocfs, local, fsid 8fff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef ( 69 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef (linprocfs, local, fsid 90ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0 ( 70 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0 (linprocfs, local, fsid 91ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01 ( 71 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01 (linprocfs, local, fsid 92ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012 ( 72 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012 (linprocfs, local, fsid 93ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123 ( 73 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123 (linprocfs, local, fsid 94ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234 ( 74 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234 (linprocfs, local, fsid 95ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345 ( 75 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345 (linprocfs, local, fsid 96ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456 ( 76 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456 (linprocfs, local, fsid 97ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234567 ( 77 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234567 (linprocfs, local, fsid 98ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234567 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345678 ( 78 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345678 (linprocfs, local, fsid 99ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345678 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789 ( 79 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789 (linprocfs, local, fsid 9aff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789 Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789a ( 80 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789a (linprocfs, local, fsid 9bff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789a Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab ( 81 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab (linprocfs, local, fsid 9cff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc ( 82 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc (linprocfs, local, fsid 9dff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd ( 83 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd (linprocfs, local, fsid 9eff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde ( 84 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde (linprocfs, local, fsid 9fff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef ( 85 chars) linprocfs on /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef (linprocfs, local, fsid a0ff000707000000) linprocfs: unmount from /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0 ( 86 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01 ( 87 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012 ( 88 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123 ( 89 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234 ( 90 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345 ( 91 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456 ( 92 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234567 ( 93 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234567: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345678 ( 94 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345678: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789 ( 95 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789a ( 96 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789a: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab ( 97 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc ( 98 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd ( 99 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde ( 100 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef ( 101 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0 ( 102 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01 ( 103 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012 ( 104 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123 ( 105 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234 ( 106 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345 ( 107 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456 ( 108 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234567 ( 109 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234567: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345678 ( 110 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345678: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789 ( 111 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789a ( 112 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789a: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab ( 113 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc ( 114 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd ( 115 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde ( 116 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef ( 117 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0 ( 118 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01 ( 119 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012 ( 120 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123 ( 121 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234 ( 122 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345 ( 123 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456 ( 124 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234567 ( 125 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef01234567: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345678 ( 126 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef012345678: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789 ( 127 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789a ( 128 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789a: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab ( 129 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789ab: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc ( 130 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abc: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd ( 131 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcd: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde ( 132 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcde: not a file system root directory Testing 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef ( 133 chars) mount: linprocfs : File name too long umount: /tmp/0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef: not a file system root directory >Fix: I suspect that the mount/umount tools are using a fixed-length buffer and/or are truncating the path at some point. The mount(2) manual page documents the max path length at 1023 characters, and the maximum length of any single component at 255 characters. These limits have not been exceeded, unless the documentation is incorrect. The practical upper limit of 80-85 characters demonstrated in this bug report is very low. The documented [ENAMETOOLONG] limit in mount(2) is sensible, but does not appear to reflect the practical reality at the present time. If the 80-85 character limit could be eliminated to allow this to work as documented, this would remove a significant limitation in the FreeBSD system which is breaking software which requires longer paths to function. Many thanks, Roger Leigh >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 18:13:27 2011 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEE4A106564A; Sat, 1 Jan 2011 18:13:26 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7B88A8FC0C; Sat, 1 Jan 2011 18:13:26 +0000 (UTC) Received: from c122-106-165-206.carlnfd1.nsw.optusnet.com.au (c122-106-165-206.carlnfd1.nsw.optusnet.com.au [122.106.165.206]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p01IDGlM008415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Jan 2011 05:13:19 +1100 Date: Sun, 2 Jan 2011 05:13:16 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Roger Leigh In-Reply-To: <201101011746.p01Hk5UQ008490@red.freebsd.org> Message-ID: <20110102050301.B1641@besplex.bde.org> References: <201101011746.p01Hk5UQ008490@red.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-bugs@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: bin/153600: Path length restrictions in mount/umount tools prevent filesystem mount/unmount X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 18:13:27 -0000 On Sat, 1 Jan 2011, Roger Leigh wrote: > t@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >> Description: > When mount is asked to mount a filesystem on a node whose absolute path is longer than 85 characters in length, the mount fails. Umount also fails under some circumstances, though the testcase attached below doesn't show this. > ... >> Fix: > I suspect that the mount/umount tools are using a fixed-length buffer and/or are truncating the path at some point. > > The mount(2) manual page documents the max path length at 1023 characters, and the maximum length of any single component at 255 characters. These limits have not been exceeded, unless the documentation is incorrect. > > The practical upper limit of 80-85 characters demonstrated in this bug report is very low. The documented [ENAMETOOLONG] limit in mount(2) is sensible, but does not appear to reflect the practical reality at the present time. If the 80-85 character limit could be eliminated to allow this to work as documented, this would remove a significant limitation in the FreeBSD system which is breaking software which requires longer paths to function. Mount name lengths are in practice limited to (MNAMELEN - 1) = 87. See . This isn't easy to fix, since MNAMELEN is in critical APIs (mainly struct statfs). struct statfs has already been changed once too often. MNAMELEN used to be (80 - 2 * sizeof(long)), which is 80 or 72, but was changed to 88. MNAMELEN is of course mentioned in statfs(2), but it isn't mentioned in mount(2) because it doesn't apply to the actual mount operation but only to determining what is mounted using statfs(2). The buffer gets truncated at mount time by mount in the kernel copying the file name to the statfs buffer with blind truncation. In practice, this means that you should never use the feature of mounting pathnames with length between MNAMELEN and (PATH_MAX - 1), since it is too hard to manage the resulting mountpoints. Bruce From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 18:20:13 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B500D106564A for ; Sat, 1 Jan 2011 18:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 885CF8FC14 for ; Sat, 1 Jan 2011 18:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01IKDG8049837 for ; Sat, 1 Jan 2011 18:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01IKDoU049836; Sat, 1 Jan 2011 18:20:13 GMT (envelope-from gnats) Date: Sat, 1 Jan 2011 18:20:13 GMT Message-Id: <201101011820.p01IKDoU049836@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Bruce Evans Cc: Subject: Re: bin/153600: Path length restrictions in mount/umount tools prevent filesystem mount/unmount X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Evans List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 18:20:13 -0000 The following reply was made to PR bin/153600; it has been noted by GNATS. From: Bruce Evans To: Roger Leigh Cc: freebsd-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: bin/153600: Path length restrictions in mount/umount tools prevent filesystem mount/unmount Date: Sun, 2 Jan 2011 05:13:16 +1100 (EST) On Sat, 1 Jan 2011, Roger Leigh wrote: > t@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >> Description: > When mount is asked to mount a filesystem on a node whose absolute path is longer than 85 characters in length, the mount fails. Umount also fails under some circumstances, though the testcase attached below doesn't show this. > ... >> Fix: > I suspect that the mount/umount tools are using a fixed-length buffer and/or are truncating the path at some point. > > The mount(2) manual page documents the max path length at 1023 characters, and the maximum length of any single component at 255 characters. These limits have not been exceeded, unless the documentation is incorrect. > > The practical upper limit of 80-85 characters demonstrated in this bug report is very low. The documented [ENAMETOOLONG] limit in mount(2) is sensible, but does not appear to reflect the practical reality at the present time. If the 80-85 character limit could be eliminated to allow this to work as documented, this would remove a significant limitation in the FreeBSD system which is breaking software which requires longer paths to function. Mount name lengths are in practice limited to (MNAMELEN - 1) = 87. See . This isn't easy to fix, since MNAMELEN is in critical APIs (mainly struct statfs). struct statfs has already been changed once too often. MNAMELEN used to be (80 - 2 * sizeof(long)), which is 80 or 72, but was changed to 88. MNAMELEN is of course mentioned in statfs(2), but it isn't mentioned in mount(2) because it doesn't apply to the actual mount operation but only to determining what is mounted using statfs(2). The buffer gets truncated at mount time by mount in the kernel copying the file name to the statfs buffer with blind truncation. In practice, this means that you should never use the feature of mounting pathnames with length between MNAMELEN and (PATH_MAX - 1), since it is too hard to manage the resulting mountpoints. Bruce From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 18:30:16 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 760F8106564A for ; Sat, 1 Jan 2011 18:30:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 645398FC13 for ; Sat, 1 Jan 2011 18:30:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01IUG7i059323 for ; Sat, 1 Jan 2011 18:30:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01IUG2w059319; Sat, 1 Jan 2011 18:30:16 GMT (envelope-from gnats) Date: Sat, 1 Jan 2011 18:30:16 GMT Message-Id: <201101011830.p01IUG2w059319@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Sergey Kandaurov Cc: Subject: Re: bin/30360: vmstat(8) returns impossible data X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sergey Kandaurov List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 18:30:16 -0000 The following reply was made to PR bin/30360; it has been noted by GNATS. From: Sergey Kandaurov To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/30360: vmstat(8) returns impossible data Date: Sat, 1 Jan 2011 21:23:24 +0300 That's a type overflow bug which I think isn't easy to fix, b.c. it breaks cp_time ABI. cp_time is (roughly) an array[CPUSTATES] of longs. long type is 4-bytes on i386, and 8-bytes on amd64. That's why I don't see this bug on amd64 boxes. Sometimes the bug might not manifest on i386 sysctl kern.cp_time, but generally it does. That's because the exported cp_time[] fmt (used by /sbin/sysctl) is different ("UL"), and that gives extended type capacity (for a while) by casting signed to unsigned. In this example bug manifests for `id' as well with /sbin/sysctl on i386 (uptime 597 days): # sysctl kern.cp_time kern.cp_time: 4021277307 75175092 2025746497 49748493 2746074583 # vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr da0 da1 in sy cs us sy id 1 5 0 93720 458992 14 0 0 3 53 1 0 0 37 1 5 -61 633 -472 Both boxes, hub and freefall, reported by arundel@ are i386. In this example /sbin/sysctl abuses "UL" fmt, but it doesn't work for vmstat which uses libdevstat which in turn properly uses cp_time[] as long signed. # sysctl kern.cp_time kern.cp_time: 795491304 5844771 246148418 43709451 2752874123 # ./test printf("%lu\n", l): 2752874123 printf("%ld\n", l): -1542093173 [compare] # ./vmstat procs memory page disk faults cpu r b w avm fre flt re pi po fr sr aa0 in sy cs us sy id 3 3 0 5776M 172M 173 39 22 5 617 444 0 743 193 60 cpustats(): before 'total += cur.cp_time[state]': cp_time[]: 795758944 cpustats(): before 'total += cur.cp_time[state]': total: 0.000000 cpustats(): after 'total += cur.cp_time[state]': cp_time[]: 795758944 cpustats(): after 'total += cur.cp_time[state]': total: 795758944.000000 cpustats(): before 'total += cur.cp_time[state]': cp_time[]: 5844771 cpustats(): before 'total += cur.cp_time[state]': total: 795758944.000000 cpustats(): after 'total += cur.cp_time[state]': cp_time[]: 5844771 cpustats(): after 'total += cur.cp_time[state]': total: 801603715.000000 cpustats(): before 'total += cur.cp_time[state]': cp_time[]: 246218512 cpustats(): before 'total += cur.cp_time[state]': total: 801603715.000000 cpustats(): after 'total += cur.cp_time[state]': cp_time[]: 246218512 cpustats(): after 'total += cur.cp_time[state]': total: 1047822227.000000 cpustats(): before 'total += cur.cp_time[state]': cp_time[]: 43723365 cpustats(): before 'total += cur.cp_time[state]': total: 1047822227.000000 cpustats(): after 'total += cur.cp_time[state]': cp_time[]: 43723365 cpustats(): after 'total += cur.cp_time[state]': total: 1091545592.000000 cpustats(): before 'total += cur.cp_time[state]': cp_time[]: -1541158615 [compare] cpustats(): before 'total += cur.cp_time[state]': total: 1091545592.000000 cpustats(): after 'total += cur.cp_time[state]': cp_time[]: -1541158615 cpustats(): after 'total += cur.cp_time[state]': total: -449613023.000000 -178 -64 343 ^^1 ^^2 ^^3 (1) and (2) is negative b.c. both multiplied by neg. total cp_time index; (3) is positive b.c. it's neg. cp_time[CP_IDLE] multiplied by neg. total cp_time index After summation, total has wrong sign and wrong value hence high pct. values. -- wbr, pluknet From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 18:54:08 2011 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7606610656A6; Sat, 1 Jan 2011 18:54:08 +0000 (UTC) (envelope-from rleigh@codelibre.net) Received: from nagini.codelibre.net (nagini.codelibre.net [IPv6:2001:41c8:1:5750::2]) by mx1.freebsd.org (Postfix) with ESMTP id B54B98FC13; Sat, 1 Jan 2011 18:54:07 +0000 (UTC) Received: by nagini.codelibre.net (Postfix, from userid 1000) id A384818431; Sat, 1 Jan 2011 18:54:04 +0000 (GMT) Date: Sat, 1 Jan 2011 18:54:04 +0000 From: Roger Leigh To: Bruce Evans Message-ID: <20110101185404.GH11671@codelibre.net> References: <201101011746.p01Hk5UQ008490@red.freebsd.org> <20110102050301.B1641@besplex.bde.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="to+bXLvrczl8f0V1" Content-Disposition: inline In-Reply-To: <20110102050301.B1641@besplex.bde.org> X-GPG-Key: 0x25BFB848 X-Debian: testing/unstable X-OS-Uptime: 20:35:25 up 32 days, 10:21, 7 users, load average: 0.01, 0.02, 0.00 User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-bugs@freebsd.org, freebsd-gnats-submit@freebsd.org Subject: Re: bin/153600: Path length restrictions in mount/umount tools prevent filesystem mount/unmount X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 18:54:08 -0000 --to+bXLvrczl8f0V1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 02, 2011 at 05:13:16AM +1100, Bruce Evans wrote: > On Sat, 1 Jan 2011, Roger Leigh wrote: > >> t@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >>> Description: >> When mount is asked to mount a filesystem on a node whose absolute path = is longer than 85 characters in length, the mount fails. Umount also fails= under some circumstances, though the testcase attached below doesn't show = this. >> ... >>> Fix: >> I suspect that the mount/umount tools are using a fixed-length buffer an= d/or are truncating the path at some point. >> >> The mount(2) manual page documents the max path length at 1023 character= s, and the maximum length of any single component at 255 characters. These= limits have not been exceeded, unless the documentation is incorrect. >> >> The practical upper limit of 80-85 characters demonstrated in this bug r= eport is very low. The documented [ENAMETOOLONG] limit in mount(2) is sens= ible, but does not appear to reflect the practical reality at the present t= ime. If the 80-85 character limit could be eliminated to allow this to wor= k as documented, this would remove a significant limitation in the FreeBSD = system which is breaking software which requires longer paths to function. > > Mount name lengths are in practice limited to (MNAMELEN - 1) =3D 87. See > . This isn't easy to fix, since MNAMELEN is in critical APIs > (mainly struct statfs). struct statfs has already been changed once too > often. MNAMELEN used to be (80 - 2 * sizeof(long)), which is 80 or 72, > but was changed to 88. MNAMELEN is of course mentioned in statfs(2), but > it isn't mentioned in mount(2) because it doesn't apply to the actual mou= nt > operation but only to determining what is mounted using statfs(2). The > buffer gets truncated at mount time by mount in the kernel copying the > file name to the statfs buffer with blind truncation. > > In practice, this means that you should never use the feature of mounting > pathnames with length between MNAMELEN and (PATH_MAX - 1), since it is too > hard to manage the resulting mountpoints. I see, thanks. This does make things somewhat more complex to fix. As a longer term (rather than immediate) solution, could I suggest taking a look at the GNU libc/linux versions of the statfs structure in ? In this version, the fixed-length fields are entirely absent, and so the length limitations are a non-issue here. Of course, the structures are not compatible, and the missing information would need to be obtained via other means such as getmntent of /proc/mounts (for example). But, the getmntent interface is also equally unrestricted, so in practice on GNU/Linux this problem does not exist. Kind regards, Roger --=20 .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail. --to+bXLvrczl8f0V1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAk0feEwACgkQVcFcaSW/uEhzKgCfRUHtNiwnSjHt//aTpbXqQNSY AUEAoM+ODWdhnvMlyk6RMRMAXSKwfpIq =bMeU -----END PGP SIGNATURE----- --to+bXLvrczl8f0V1-- From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 19:00:30 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ABE5106564A for ; Sat, 1 Jan 2011 19:00:30 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 379D18FC19 for ; Sat, 1 Jan 2011 19:00:30 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01J0Sbg090882 for ; Sat, 1 Jan 2011 19:00:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01J0Sn9090867; Sat, 1 Jan 2011 19:00:28 GMT (envelope-from gnats) Date: Sat, 1 Jan 2011 19:00:28 GMT Message-Id: <201101011900.p01J0Sn9090867@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Roger Leigh Cc: Subject: Re: bin/153600: Path length restrictions in mount/umount tools prevent filesystem mount/unmount X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Roger Leigh List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 19:00:30 -0000 The following reply was made to PR bin/153600; it has been noted by GNATS. From: Roger Leigh To: Bruce Evans Cc: freebsd-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: bin/153600: Path length restrictions in mount/umount tools prevent filesystem mount/unmount Date: Sat, 1 Jan 2011 18:54:04 +0000 --to+bXLvrczl8f0V1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 02, 2011 at 05:13:16AM +1100, Bruce Evans wrote: > On Sat, 1 Jan 2011, Roger Leigh wrote: > >> t@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >>> Description: >> When mount is asked to mount a filesystem on a node whose absolute path = is longer than 85 characters in length, the mount fails. Umount also fails= under some circumstances, though the testcase attached below doesn't show = this. >> ... >>> Fix: >> I suspect that the mount/umount tools are using a fixed-length buffer an= d/or are truncating the path at some point. >> >> The mount(2) manual page documents the max path length at 1023 character= s, and the maximum length of any single component at 255 characters. These= limits have not been exceeded, unless the documentation is incorrect. >> >> The practical upper limit of 80-85 characters demonstrated in this bug r= eport is very low. The documented [ENAMETOOLONG] limit in mount(2) is sens= ible, but does not appear to reflect the practical reality at the present t= ime. If the 80-85 character limit could be eliminated to allow this to wor= k as documented, this would remove a significant limitation in the FreeBSD = system which is breaking software which requires longer paths to function. > > Mount name lengths are in practice limited to (MNAMELEN - 1) =3D 87. See > . This isn't easy to fix, since MNAMELEN is in critical APIs > (mainly struct statfs). struct statfs has already been changed once too > often. MNAMELEN used to be (80 - 2 * sizeof(long)), which is 80 or 72, > but was changed to 88. MNAMELEN is of course mentioned in statfs(2), but > it isn't mentioned in mount(2) because it doesn't apply to the actual mou= nt > operation but only to determining what is mounted using statfs(2). The > buffer gets truncated at mount time by mount in the kernel copying the > file name to the statfs buffer with blind truncation. > > In practice, this means that you should never use the feature of mounting > pathnames with length between MNAMELEN and (PATH_MAX - 1), since it is too > hard to manage the resulting mountpoints. I see, thanks. This does make things somewhat more complex to fix. As a longer term (rather than immediate) solution, could I suggest taking a look at the GNU libc/linux versions of the statfs structure in ? In this version, the fixed-length fields are entirely absent, and so the length limitations are a non-issue here. Of course, the structures are not compatible, and the missing information would need to be obtained via other means such as getmntent of /proc/mounts (for example). But, the getmntent interface is also equally unrestricted, so in practice on GNU/Linux this problem does not exist. Kind regards, Roger --=20 .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail. --to+bXLvrczl8f0V1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAk0feEwACgkQVcFcaSW/uEhzKgCfRUHtNiwnSjHt//aTpbXqQNSY AUEAoM+ODWdhnvMlyk6RMRMAXSKwfpIq =bMeU -----END PGP SIGNATURE----- --to+bXLvrczl8f0V1-- From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 22:30:32 2011 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 1233) id DFA8C1065670; Sat, 1 Jan 2011 22:30:32 +0000 (UTC) Date: Sat, 1 Jan 2011 22:30:32 +0000 From: Alexander Best To: Bruce Cran Message-ID: <20110101223032.GA57635@freebsd.org> References: <201012121110.oBCBABjm057751@freefall.freebsd.org> <20101212111844.7510053e@core.draftnet> <20101212121923.GA61077@freebsd.org> <20101223103220.0000483f@unknown> <20101223183720.GA84742@freebsd.org> <20101223192130.00007b30@unknown> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101223192130.00007b30@unknown> Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/104624: Sound, mouse and keyboard badly interrupted while I/O (disk, net) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 22:30:33 -0000 On Thu Dec 23 10, Bruce Cran wrote: > On Thu, 23 Dec 2010 18:37:20 +0000 > Alexander Best wrote: > > > is this output right at the beginning normal? > > > > fio: this platform does not support process shared mutexes, forcing > > use of threads. Use the 'thread' option to get rid of this warning. > > f1: (g=0): rw=write, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1 ... > > f1: (g=0): rw=write, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1 > > fio: this platform does not support process shared mutexes, forcing > > use of threads. Use the 'thread' option to get rid of this warning. > > f2: (g=1): rw=randwrite, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1 ... > > f2: (g=1): rw=randwrite, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1 > > fio: this platform does not support process shared mutexes, forcing > > use of threads. Use the 'thread' option to get rid of this warning. > > f3: (g=2): rw=read, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1 ... > > f3: (g=2): rw=read, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1 > > fio: this platform does not support process shared mutexes, forcing > > use of threads. Use the 'thread' option to get rid of this warning. > > f4: (g=3): rw=randread, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1 ... > > f4: (g=3): rw=randread, bs=4K-4K/4K-4K, ioengine=sync, iodepth=1 > > Starting 12 threads and 4 processes > > Yes - it just means that FreeBSD doesn't support pshared mutexes. You > can add "thread" to the job file to stop the warning. just wanted to report that this doesn't seem to be a SMP issue. kern.smp.disabled: 1 makes no difference. cheers. alex > > -- > Bruce Cran -- a13x From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 1 23:10:11 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4A62106567A for ; Sat, 1 Jan 2011 23:10:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6BA628FC15 for ; Sat, 1 Jan 2011 23:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p01NAAS7059059 for ; Sat, 1 Jan 2011 23:10:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p01NAA3J059058; Sat, 1 Jan 2011 23:10:10 GMT (envelope-from gnats) Resent-Date: Sat, 1 Jan 2011 23:10:10 GMT Resent-Message-Id: <201101012310.p01NAA3J059058@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "Ronald F.Guilmette" Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E09E8106564A for ; Sat, 1 Jan 2011 23:02:51 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id C07258FC0C for ; Sat, 1 Jan 2011 23:02:51 +0000 (UTC) Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id 21C75BDC46; Sat, 1 Jan 2011 15:02:51 -0800 (PST) Message-Id: <20110101230251.21C75BDC46@segfault.tristatelogic.com> Date: Sat, 1 Jan 2011 15:02:51 -0800 (PST) From: "Ronald F.Guilmette" To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: kern/153610: nfe0 malfunction at boot time X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ronald F.Guilmette" List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jan 2011 23:10:11 -0000 >Number: 153610 >Category: kern >Synopsis: nfe0 malfunction at boot time >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jan 01 23:10:10 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Ronald F. Guilmette >Release: FreeBSD 8.1-RELEASE amd64 >Organization: Infinite Monkeys & Co. >Environment: FreeBSD 8.1-RELEASE amd64 Gigabyte GA-m55plus-S3G nmotherboard w/ Nvidia 430 Southbridge Onboard Ethernet port hardwired up to a stock Linksys WRT54G wireless router configured for static (i.e. NO DHCP) >Description: Upon boot-up of the GA-m55plus-S3G based system, I get an (unending?) stream of console/syslog messages exactly like this: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) After googling around awhile, I learned that this is an old, and apparently still unsolved problem: http://kerneltrap.org/mailarchive/freebsd-current/2008/1/18/578972 The thread above suggested that I try manually down-ing and then up-ing the nfe0 interface. I did that, and yes, that causes the problem to go away and after that up/down the interface seems to be functioning normally. However this server SHOULD be able to recover gracefully from, e.g., power failures, even when I am out of town, so what am I supposed to do? Should I add "manual" down & up commands for this interface to my /etc/rc.local file?? Ideally, I shouldn't have to do that (and I'm not even 100% sure that even doing that will produce reliable results). >How-To-Repeat: See above. Get yourself a motherboard with an Nvidia 430 Southbridge on it, and then wire up the ethernet port from that to a stock Linksys WRT54G, set the Linksys box to NO DHCP (although that probably doesn't matter), give the nfe0 device a static IP in your /etc/rc.conf file (although that probably doesn't matter either), and then do a cold restart. >Fix: Beats me. I am forced to workaround this for now by installing a cheapie Realtek ethernet card (which most certainly works). That's a pity, because I wanted to try using the gigabit capability of the onboard Nvidia ethernet port. Oh well. I'll live. >Release-Note: >Audit-Trail: >Unformatted: