STREAMS and Character Device Coexistence [PSARC/2009/380 FastTrack timeout 07/13/2009]
Edward Pilatowicz wrote: fyi, i'm not a psarc member. i'm just a heckler[1]. ARC review: hecklers wanted. ;-}
Support off-line files on SAM-QFS for Samba in Solaris [PSARC/2009/381 FastTrack timeout 07/13/2009]
My concern is that this doesn't provide a complete solution to sharing offline files on Nevada or OpenSolaris, or support future HSM or file migration applications. Users have the option to share files over SMB using smb/server (the native CIFS Service) or Samba, and it seems inappropriate to select a mechanism that doesn't support that choice. Adding an offline system attribute (PSARC/2007/315 and PSARC 2007/394) would provide support to smb/server, Samba and other file sharing protocols, such as NFS, and it would be available in both kernel and user space. The interfaces described in PSARC/2007/315 are available via libc - no special dlopen() or library dependency required to support SAM-QFS file sharing. I'd much prefer to see an ARC case that adds an offline system attribute, which would support both our current file sharing needs and future needs (HSM and file migration applications) than one that simply satisfies the short term need of one application. I could work with you on such an ARC case and implementation. Alan - Original Message - Jiri Sasek - RPE Prague Jiri.Sasek at Sun.COM wrote: Hi Alan Please let me elaborate more detailed. Samba and SMB-server has different design concepts: Samba: pure user-space application doing all the CIFS processing on the user-space level. Use only the very basic data-transfer acceleration methods like sendfile(2) or splice() [bi-directional sendfile supported by Linux kernel] calls supported directly in the kernel. On the other side it can link any user space library. i.e. libsam.so as in this case SMB-server: doing more accelerations directly in the kernel. There is a lot of interfaces on which such change should be applied. There the reasons why not to harmonize the unified interface for the Samba and SMB-server: - samba has also internal interfaces (samba 3.+ is modular) but these interfaces are controlled by the samba.org community. - there are different design concepts between the Samba an SMB-server. - samba.org follows different priorities than appliance team integrating the SMB-server. I have never heard about QFS support on appliances. Also the integration of SAM (*) to run above the ZFS was planed after the SAM-QFS integration into the Nevada. SAM-QFS integration into the Nevada was planed to the end of the cal. year 08 but it was postponed where no date is currently estimated. In such case I am unconvinced about the effectivity of waiting for the harmonized solition for samba and SMB-server. Jiri (*) - SAM (Storage Archive Management) ~= HSM (Hierarchical Storage Management) according to IBM terminology Alan M Wright wrote: While this will solve the problem for Samba, it won't provide support for offline files via the native Solaris CIFS Service, i.e. anyone using the native Solaris CIFS Service to share samfs will continue to see timeout failures as described below. It would be good to have a solution that supports both services. Alan On 07/06/09 11:19, Daniel Hain wrote: I'm submitting this fasttrack for Jiri Sasek. This proposal seeks patch binding and will timeout on 07/13/2009. The listed imported interfaces from libsam.so are currently classified as Stable by the last approved PSARC case (PSARC/2001/599/ SAM_FS and QFS 4.0). The case for SAM-QFS 5.0 (PSARC/2007/588) lists them as Unstable, but that case has not been approved. Discussion with the SAM-QFS team indicates that they feel the classification of these interfaces is still Stable. -Dan Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Support off-line files on SAM-QFS for Samba in Solaris 1.2. Name of Document Author/Supplier: Author: Jiri Sasek 1.3 Date of This Document: 06 July, 2009 4. Technical Description Proposal: Support off-line files on SAM-QFS for Samba in Solaris. Detail: Samba is CIFS volume and printing server. The current version of Samba (3.0.34) integrated in Solaris does not support off-line file attribute for files stored on a SAM-FS volume when located on an off-line storage (a tape). Such situation has the following consequences on MS Windows clients: - Client's attempt to acces an off-line file will fail on timeout which is set too short to access a file stored on a tape or any other external (off-line) storage. - If MS Windows Eplorer's curent directory is set to a directory full of off-lined files it causes a storm of the tape changer arms when thumbnails are being generated. The solution is to let Samba use libsam.so library, [4], which provides the off-line information for files stored on a off-line storage (a tape). Since this library is optional on Solaris
Support off-line files on SAM-QFS for Samba in Solaris [PSARC/2009/381 FastTrack timeout 07/13/2009]
Providing this as a temporary solution to relieve a customer problem is excellent. My disagreement is that it should be committed as a long term solution for offline support when we already have a defined system attribute mechanism that could be used to solve the problem via libc. Alan - Original Message - Jiri Sasek - RPE Prague Jiri.Sasek at Sun.COM wrote: Please let me refine. This contract is special case of the interface contract where the interface is not controlled by Solaris and is optional in Solaris so the main accent is on the keeping of the functionality of samba in case the optional component (libsam.so) is not installed on the system. Solution itself is already running on the customers box as temporary relief so its functionality is proved. Only the issue is to prove also the original functionality of the samba daemon is not interfered in some undocumented case. Jiri Alan M Wright wrote: While this will solve the problem for Samba, it won't provide support for offline files via the native Solaris CIFS Service, i.e. anyone using the native Solaris CIFS Service to share samfs will continue to see timeout failures as described below. It would be good to have a solution that supports both services. Alan On 07/06/09 11:19, Daniel Hain wrote: I'm submitting this fasttrack for Jiri Sasek. This proposal seeks patch binding and will timeout on 07/13/2009. The listed imported interfaces from libsam.so are currently classified as Stable by the last approved PSARC case (PSARC/2001/599/ SAM_FS and QFS 4.0). The case for SAM-QFS 5.0 (PSARC/2007/588) lists them as Unstable, but that case has not been approved. Discussion with the SAM-QFS team indicates that they feel the classification of these interfaces is still Stable. -Dan Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Support off-line files on SAM-QFS for Samba in Solaris 1.2. Name of Document Author/Supplier: Author: Jiri Sasek 1.3 Date of This Document: 06 July, 2009 4. Technical Description Proposal: Support off-line files on SAM-QFS for Samba in Solaris. Detail: Samba is CIFS volume and printing server. The current version of Samba (3.0.34) integrated in Solaris does not support off-line file attribute for files stored on a SAM-FS volume when located on an off-line storage (a tape). Such situation has the following consequences on MS Windows clients: - Client's attempt to acces an off-line file will fail on timeout which is set too short to access a file stored on a tape or any other external (off-line) storage. - If MS Windows Eplorer's curent directory is set to a directory full of off-lined files it causes a storm of the tape changer arms when thumbnails are being generated. The solution is to let Samba use libsam.so library, [4], which provides the off-line information for files stored on a off-line storage (a tape). Since this library is optional on Solaris then it is necessary to use lazy binding option for linking this library with Samba. The lazy binding option makes sure that smbd (Samba daemon) will run even if libsamfs.so is not present on the system. When samfs share = yes configuration option is set in smb.conf (Samba configuration file) and libsamfs.so is not present on the system then calling the lazy linked library-call will not complete the dlopen(2) call successfuly and the standard message from the run-time linker notifying about is redirected from the stderr output to the smbd log file appropriate to the CIFS session serviced by this smbd daemon. Samba log files can be configured as described in smb.conf(4). In the standard distribution such log file is located on the /var/samba/log/log.hostname|IP path. SAM-FS library libsamfs.so is delivered by optional packages SUNWsamfsr SUNWsamfsu and should be installed from the external source. Exported Interfaces: (uncommited) - FILE_ATTRIBUTE_OFFLINE flag (0x1000) in Attributes of SMB_QUERY_FILE_BASIC_INFO response CIFS message will indicate the off/on-line file status of files located on SAM-QFS share - smb.conf option samfs share = yes|no (default: no) Imported Interfaces: The following functions from libsamfs.so are used: - sam_stat()| File status calls available from libsam library sam_segment_stat()| returning the struct sam_stat References: [1]
PSARC/2009/374 libxmlsec
Will Young wrote:
On Wed, 2009-07-08 at 15:19 -0500, Nicolas Williams wrote:
On Wed, Jul 08, 2009 at 04:06:53PM -0400, Will Young wrote:
On Wed, 2009-07-08 at 12:11 -0700, Kais Belgaied wrote:
so, any dependency on a particular version of OpenSSL's lib{crypto,ssl} ?
doesn't this case require an ARC contract against PSARC/2003/500 for the
import of OpenSSL ?
I no longer saw a need for a contract as of the integration of:
6806387 Move OpenSSL from ON to SFW
The move alone could not imply a change of interface stability.
PSARC/2006/555 (Move OpenSSL to /usr) did not change the interface
stability of any part of OpenSSL (see section 4.5 of the one-pager).
It's my understanding that within one gate no contract is needed
(updating any element of the gate one is responsible for
examining/updating related elements.) Is that not accurate?
Only true of the word Consolidation is part of the interface taxonomy
assigned and that is not the case for OpenSSL.
We plan to remove the ARC contract requirement from OpenSSL once it
reaches version 1.0.0 (which should be soon since it is currently in
Beta 2).
--
Darren J Moffat
Support off-line files on SAM-QFS for Samba in Solaris [PSARC/2009/381 FastTrack timeout 07/13/2009]
Alan.M.Wright wrote: Providing this as a temporary solution to relieve a customer problem is excellent. My disagreement is that it should be committed as a long term solution for offline support when we already have a defined system attribute mechanism that could be used to solve the problem via libc. Given the above I'm derailing this case for the purpose of writing an opinion with Advice to fund the above mentioned project and to point out the issue of adding Solaris/Sun functionality to Samba with no planned match for the in kernel CIFS server. PSARC members please are you willing to vote based on the above our would you like to see draft opinion text first. I've marked the case as waiting need vote for now. Note that this is *derail* not *deny* (though depending on the vote it could be but I doubt it). -- Darren J Moffat
PSARC/2009/374 libxmlsec
Will Young wrote: On Wed, 2009-07-08 at 15:36 -0500, Nicolas Williams wrote: On Wed, Jul 08, 2009 at 04:21:47PM -0400, Will Young wrote: On Wed, 2009-07-08 at 14:25 -0500, Nicolas Williams wrote: ... A kmf/PKCS#11 hybrid module seems to be the only possibility aside from OpenSSL or NSS that adequately covers the needed crypto operations and certificate management operations. The nice thing about KMF is that it gives you a single interface to OpenSSL and NSS keystores. But this combination also doesn't solve anything for all store types so its is not a worthwhile immediate investment. I don't understand this last statement. KMF gives nice capabilities for certificate operations, i.e. to determine the trust of a cert given a store of any type. But it really has crypto operations that are also geared towards certificate management purposes. I.e. atomic since certificates are small, not so many algorithms since no one wants an odd one for their certs. So once one has done one's cert operations and is then ready to use the key, one needs to drop to a specific underlying provider to do operations xmlsec requires with the key. This means either an implementation of crypto for each keystore type or key extraction and the assumption that key extraction will always be allowed by the non-default keystores. -Will KMF was not designed to offer a full set of crypto operations, just those that would be relevant when dealing with PKI objects - X.509 certs, RSA/DSA keys, CRLs. You can use KMF though to fetch a key handle from NSS, PKCS11, or OpenSSL and then use that key handle to do further crypto using the crypto API appropriate for the keystore. -Wyllys
STREAMS and Character Device Coexistence [PSARC/2009/380 FastTrack timeout 07/13/2009]
Sebastien Roy wrote: On Mon, 2009-07-06 at 08:55 -0700, Garrett D'Amore - sun microsystems wrote: I'm submitting the following case on my own behalf. Times out on 7/13/2009. This case seeks patch binding. +1 -Seb Thanks. - Garrett
Support off-line files on SAM-QFS for Samba in Solaris [PSARC/2009/381 FastTrack timeout 07/13/2009]
On 07/ 9/09 04:33 AM, Darren J Moffat wrote: Alan.M.Wright wrote: Providing this as a temporary solution to relieve a customer problem is excellent. My disagreement is that it should be committed as a long term solution for offline support when we already have a defined system attribute mechanism that could be used to solve the problem via libc. Given the above I'm derailing this case for the purpose of writing an opinion with Advice to fund the above mentioned project and to point out the issue of adding Solaris/Sun functionality to Samba with no planned match for the in kernel CIFS server. PSARC members please are you willing to vote based on the above our would you like to see draft opinion text first. I've marked the case as waiting need vote for now. Note that this is *derail* not *deny* (though depending on the vote it could be but I doubt it). I'd, for one, like to see the draft opinion. I have some opinions about these approaches which I will document tomorrow. -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
remove sample.au [PSARC/2009/383 Self Review]
I'm submitting the following self-review case on my own behalf. Minor binding is requested. Its possible that this could be handled as a simple bug fix, but I'm not sure if there was ever a case that supplied the the file. (It looks like this was intended to be removed as part of LSARC 2000/257, but it isn't clear.) This case just makes it explicit: I'm removing the stale file. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: remove sample.au 1.2. Name of Document Author/Supplier: Author: Garrett D'Amore 1.3 Date of This Document: 09 July, 2009 4. Technical Description Requested Binding: Patch Problem --- The legacy sample.au file on Solaris systems is about 300K. The audio itself refers to the long since EOF'd audiotool application (see LSARC 2000/257), and also makes reference to the old Sun microphone (which apparently had a battery that lasted about 210 hours.) The full path to the file is /usr/demo/SOUND/sounds/sample.au Solution This file should just be removed, it serves no purpose, and if people are actually listening to it, it may lead to confusion. Perhaps worse, it wastes about 300K of disk space, and the Live CD distributions are struggling with space requirements (so this helps them!) 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: Automatic 6.6. ARC Exposure: open
remove sample.au [PSARC/2009/383 Self Review]
On Thu, 2009-07-09 at 11:20 -0700, Garrett D'Amore - sun microsystems wrote: remove sample.au +1 -Seb
audiosbp16x audio driver [PSARC/2009/384 Self Review]
I'm submitting the following self-review case on my own behalf. Its another audio driver. The only potentially contentious portion of it is that we are only supporting stereo in the first integration though the device can do 5.1. If anyone feels this warrants promotion to a fast track, then please speak up. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: audiosbp16x audio driver 1.2. Name of Document Author/Supplier: Author: Garrett D'Amore 1.3 Date of This Document: 09 July, 2009 4. Technical Description Title: audiosbp16x audio driver Requested Binding: Minor This project proposes to deliver a device driver for the Creative SBP16X family of AC'97 audio devices. These parts are found on the Dell OEM SoundBlaster Live! 5.1 cards (these devices will have a label of SB0200 on them.) The driver would be called audiosbp16x, and would be delivered in a package SUNWaudiosbp16x. It would use the Consolidation Private Boomer (PSARC 2008/318) interfaces. The package name would be Committed, and the audiosbp16x driver would be Uncommitted, as would any specific features delivered by the driver. We are not planning on providing FMA support for this driver (we don't believe it is strategic, and no other audio drivers have FMA support currently). The driver will support suspend/resume and quiesce(9e). The hardware supports 5.1 playback and stereo record, at rates of up to 48kHz and 16 bit precision. However we are only planning on supporting stereo features in our first delivery. We will add support for full 5.1 surround sound as a future RFE, as time permits. This driver is being supplied and supported by 4Front as part of their business arrangement with Sun. 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: Automatic 6.6. ARC Exposure: open
audiols driver [PSARC/2009/385 Self Review]
I'm submitting the following self-review case on my own behalf. Its another audio driver. If anyone feels this warrants promotion to a fast track, then please speak up. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: audiols driver 1.2. Name of Document Author/Supplier: Author: Garrett D'Amore 1.3 Date of This Document: 09 July, 2009 4. Technical Description Title: audiols audio driver Requested Binding: Minor This project proposes to deliver a device driver for the Creative Audigy LS family of audio devices. These parts are found in discrete audio boards, such as the Audigy2-LS and SoundBlaster Live 24-bit 7.1 sound cards. The driver would be called audiols, and would be delivered in a package SUNWaudiols. It would use the Consolidation Private Boomer (PSARC 2008/318) interfaces. The package name would Committed, and the driver would be Uncommitted, as would any specific features delivered by the driver. We are not planning on providing FMA support for this driver (we don't believe it is strategic, and no other audio drivers have FMA support currently). In initial delivery, we are planning on supporting basic stereo playback and record using the analog ports on the device. However, architecturally, we'd like to allow for the chance to broaden this support for surround sound or SPDIF if time permits. (The device can support 7.1 and digital SPDIF output.) 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: Automatic 6.6. ARC Exposure: open
PSARC 2009/377 In-kernel pfexec implementation
This case was approved at PSARC yesterday. - Garrett
PSARC 2009/378 Basic File Privileges
This case was approved at PSARC yesterday. - Garrett
