This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue Apr 16 19:56:18 2024 Received: from entropy.muc.muohio.edu (IDENT:root@entropy.muc.muohio.edu [134.53.213.10]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id RAA13161 for ; Wed, 10 Nov 1999 17:35:31 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by entropy.muc.muohio.edu (8.9.3/8.9.3) with ESMTP id FAA08323; Wed, 10 Nov 1999 05:32:57 -0500 Received: by vger.rutgers.edu via listexpand id ; Wed, 10 Nov 1999 17:32:29 -0500 Received: by vger.rutgers.edu id ; Wed, 10 Nov 1999 17:32:08 -0500 Received: from ix.netcorps.com ([207.1.125.106]:50349 "EHLO ix.netcorps.com") by vger.rutgers.edu with ESMTP id ; Wed, 10 Nov 1999 17:32:01 -0500 Received: from timpanogas.com ([207.109.151.230]) by ix.netcorps.com (8.9.0/8.9.0) with ESMTP id OAA02403 for ; Wed, 10 Nov 1999 14:38:38 -0800 (PST) Message-Id: <3829F0C7.59C568A7@timpanogas.com> Date: Wed, 10 Nov 1999 15:25:11 -0700 From: "Jeff V. Merkey" Organization: TRG, Inc. X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en Mime-Version: 1.0 To: linux-kernel@vger.rutgers.edu Subject: [Fwd: Getting IOCTL's into VFS File System Drivers] Content-Type: multipart/mixed; boundary="------------097E68D99BB5D8EED9D8BB78" Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig This is a multi-part message in MIME format. --------------097E68D99BB5D8EED9D8BB78 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------097E68D99BB5D8EED9D8BB78 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <3829DA11.D0B119E2@timpanogas.com> Date: Wed, 10 Nov 1999 13:48:17 -0700 From: "Jeff V. Merkey" Organization: TRG, Inc. X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: linux-kernel@vger.rutgers.edu Subject: Getting IOCTL's into VFS File System Drivers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Alan/Ingo/Pavel, Do you one you guys know a good way to get IOCTL calls into the FS drivers? I noticed there is an IOCTL path for FILE objects, but there does not appear to be a general purpose IOCTL call to the File System Drivers themselves (but there is to symbolic devices files created by these FS's). I basically need this for the utilities that create and config volumes and mirroring so I can query as to whether a file system is mounted from the tools, and prohibit users from blowing away volume segments, namespaces, etc. while a volume is mounted. There are also some question/answer stuff during boot from a Netware file system if NWFSCK (Netware volume repair utility) gets invoked due to mounting problems. I need to be able to pass back and forth, such as asking whether an imcomplete mirror group should be activated and failing mirrors dropped during system boot if FS errors are detected. I am calling open() from the utilities with symbolic handles for device objects (i.e. /dev/hda, /dev/hdb, etc.) and this is how I am creating partitions, volumes, etc. Is there a symbolic handle that will map to the FS driver so I can pass IOCTL commands between the utilities and the file system driver, like /proc/filesystems/nwfs or something to that effect? I religously poured over the code in Linux until 4 a.m. this morning, and it doesn't look like this is supported. Thanks in advance for the fabulous help. Jeff --------------097E68D99BB5D8EED9D8BB78-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/