On Fri, 7 Feb 2003, Hiten Pandya wrote:
> On Thu, Feb 06, 2003 at 10:53:08AM -0800, Julian Elischer wrote the words in effect
>of:
> >
> >
> > On Thu, 6 Feb 2003, John Baldwin wrote:
> >
> > >
> > > On 05-Feb-2003 Julian Elischer wrote:
> > > >
> > > > Is there ever a case when a vnode is
On Fri, 7 Feb 2003, Hiten Pandya wrote:
> On Thu, Feb 06, 2003 at 10:53:08AM -0800, Julian Elischer wrote the words in effect
>of:
> >
> > On Thu, 6 Feb 2003, John Baldwin wrote:
> >
> > > On 05-Feb-2003 Julian Elischer wrote:
> > > >
> > > > Is there ever a case when a vnode is locked for lo
On Thu, Feb 06, 2003 at 10:53:08AM -0800, Julian Elischer wrote the words in effect of:
>
>
> On Thu, 6 Feb 2003, John Baldwin wrote:
>
> >
> > On 05-Feb-2003 Julian Elischer wrote:
> > >
> > > Is there ever a case when a vnode is locked for longer than the duration
> > > of the syscall that l
On Thu, 6 Feb 2003, John Baldwin wrote:
>
> On 05-Feb-2003 Julian Elischer wrote:
> >
> > Is there ever a case when a vnode is locked for longer than the duration
> > of the syscall that locked it?
>
> Shouldn't be. That would be a bug I believe. Userland threads should
> never hold any ker
On 05-Feb-2003 Julian Elischer wrote:
>
> Is there ever a case when a vnode is locked for longer than the duration
> of the syscall that locked it?
Shouldn't be. That would be a bug I believe. Userland threads should
never hold any kernel locks.
--
John Baldwin <[EMAIL PROTECTED]> <>< htt
Is there ever a case when a vnode is locked for longer than the duration
of the syscall that locked it?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
