On Thu, 7 Jul 2005, Brian King wrote: > Kai Makisara wrote: > >>The primary change is adding a kref to the Scsi_Tape structure, to avoid > >>an oops when the tape drive is removed while open. This includes > >>scsi_tape_get/put routines and scsi_tape_release, and changes to st_open > >>and st_release. This is all based on the SCSI disk & CD reference > >>counting code. > >> > > > > You have added a new kref for this. Have you considered using the > > existing cdev refcounting instead of a separate kref? > > > > (When the new character device code was introduced, I got the impression > > that the proper way for the st would be to embed the struct into struct > > scsi_tape and make the destructor. The scsi_tapes[] array would not be > > necessary any more because the struct scsi_tape would be accessible through > > containerof(inode->i_cdev, struct scsi_tape, cdev). > > (An array would be still necessary for tape number allocation.) > > I did not implement this at that time because there was no real need for > > the change and it seemed too complex to test just for fun.) > > I'm not sure how you would do this since there is currently no way to > embed data in a cdev.
True. This is why it has to be done the other way: embed cdev(s) into struct scsi_tape. The file linux/drivers/char/snsc.c is an example how this works except for the release (deallocation) part. I just searched linux/fs/char_dev.c for a solution for this part but did not find one. The URL http://lkml.org/lkml/2003/9/22/220 quite well describes what the code looks like. Seems best to forget using cdevs for deallocation. The tape devices now appear in the sysfs class scsi_tape. One possibility might be to use refcounting in these objects as suggested by the URL. This does not remove the search loop through scsi_tapes[] in st_open() and the added code and data would be only for deallocation. > Also, since there are multiple cdevs per scsi_tape, > it seems cleaner to use a new kref. > The new kref may well be the best way overall. I just want to explore the existing possibilities that don't need updating when the world around st changes. -- Kai - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
