(I am not subscribed to this list, so please cc me in replies.)
Rename is still broken in a number of file systems because of races
and deadlocks and an insane locking protocol. To make it easier to
fix them, and to make it easier to replace the VOP_RENAME protocol by
something less insane in the
On Sun, Dec 18, 2011 at 11:59:35PM -0500, Christos Zoulas wrote:
> On Dec 18, 11:54pm, t...@panix.com (Thor Lancelot Simon) wrote:
> -- Subject: Re: cloning device close race?
>
> | > >I am guessing the problem also exists with other cloning
> | > >pseudodevices, not just the new /dev/random imple
On Dec 18, 11:54pm, t...@panix.com (Thor Lancelot Simon) wrote:
-- Subject: Re: cloning device close race?
| > >I am guessing the problem also exists with other cloning
| > >pseudodevices, not just the new /dev/random implementation.
| >
| > Does adding:
| >
| > vn_close(nd.ni_vp, flags, l->
On Mon, Dec 19, 2011 at 04:06:51AM +, Christos Zoulas wrote:
> In article <20111219033403.ga25...@panix.com>,
> Thor Lancelot Simon wrote:
> >-=-=-=-=-=-
> >
> >I wrote the attached test program as a benchmark for the new
> >/dev/random implementation.
> >
> >If you run 10 or so copies at onc
On Sun, 18 Dec 2011 22:34:03 -0500
Thor Lancelot Simon wrote:
> If you run 10 or so copies at once on a multiprocessor system
> with DIAGNOSTIC, you'll see a lot of this message emitted:
>
> vrelel: missing VOP_CLOSE(): vnode @ 0xfe801e73cb28, flags
> (0x800030)
> tag VT_UFS(1), type
In article <20111219033403.ga25...@panix.com>,
Thor Lancelot Simon wrote:
>-=-=-=-=-=-
>
>I wrote the attached test program as a benchmark for the new
>/dev/random implementation.
>
>If you run 10 or so copies at once on a multiprocessor system
>with DIAGNOSTIC, you'll see a lot of this message e
I wrote the attached test program as a benchmark for the new
/dev/random implementation.
If you run 10 or so copies at once on a multiprocessor system
with DIAGNOSTIC, you'll see a lot of this message emitted:
vrelel: missing VOP_CLOSE(): vnode @ 0xfe801e73cb28, flags
(0x800030)
tag
In article ,
Bharat Joshi wrote:
>Hi,
>
> It has been some time and I did not get any response for the
>below question.
>
> I am not subscribed to the NetBSD tech-kern mailing list but I
>have been checking the mailing list archive to make sure that I have
>not missed any responses.
>
Hi folks,
during this years Summer of Code Charles Zhang and I implemented the
posix_spawn syscall. We are now at a point that, with some further minor
cleanup and debugging, this is ready to commit. The main changes are pretty
local, but to avoid code duplication a few of the existing file operat
Hi,
It has been some time and I did not get any response for the
below question.
I am not subscribed to the NetBSD tech-kern mailing list but I
have been checking the mailing list archive to make sure that I have
not missed any responses.
I disabled the code I had identified
Hi,
On Sun, Dec 18, 2011 at 7:24 AM, Izumi Tsutsui wrote:
> Hi,
>
>> Izumi, thank you for reviewing! New patches are attached.
> :
>> >> Here is a fix for the issue. Independent on what fs partition
>> >> contains, ufs_ls() was called. Because of ext2 and ufs similarity it
>> >> worked successfu
11 matches
Mail list logo