Date: Sat, 07 Jul 2007 19:21:29 -0600 From: Scott Long <scottl@samsco.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: Tai-hwa Liang <avatar@mmlab.cse.yzu.edu.tw>, Jiawei Ye <leafy7382@gmail.com>, current@freebsd.org Subject: Re: HEADS UP: destroy_dev_sched() KPI in the tree Message-ID: <46903C19.2040002@samsco.org> In-Reply-To: <20070707160042.GJ2200@deviant.kiev.zoral.com.ua> References: <20070703180141.GJ2200@deviant.kiev.zoral.com.ua> <E1I6SAN-0000by-Bt@cs1.cs.huji.ac.il> <20070705144443.GV2200@deviant.kiev.zoral.com.ua> <c21e92e20707070536x6c8053c0l7ecad5a5bfa6de15@mail.gmail.com> <20070707160042.GJ2200@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Kostik Belousov wrote: > On Sat, Jul 07, 2007 at 08:36:23PM +0800, Jiawei Ye wrote: >> On 7/5/07, Kostik Belousov <kostikbel@gmail.com> wrote: >>> Today, I reverted the part of commit that tried to transform destroy_dev() >> >from d_close() into destroy_dev_sched(). See kern_conf.c, rev. 1.208. >>> You shall call destroy_dev_sched() explicitely. >>> >>> >> Does this mean that mount_smbfs has to explicitly call it now? It is >> currently stuck in the devdrn state with the latest kernel :( >> >> Jiawei Ye > Exactly. Patch by Tai-hwa Liang is pending. I also remember that sg(4) > had the same problem, but I do not know it current status. Which driver is sg(4)? If you're talking about scsi_sg, it's not affected by the problem. scsi_targ is/was, I haven't checked to see if it was fixed yet. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46903C19.2040002>