> YAMAMOTO Takashi wrote:
>
>> it isn't a sane behaviour.
>> i want to see the log.
>
> I found the bug in kernel part of PUFFS, and I am the one that
> introduced it: if I get a vnode from name cache and succesfully lookup
> it, I reuse the cached vnode without checking if the userland cookie
>
YAMAMOTO Takashi wrote:
> it isn't a sane behaviour.
> i want to see the log.
I found the bug in kernel part of PUFFS, and I am the one that
introduced it: if I get a vnode from name cache and succesfully lookup
it, I reuse the cached vnode without checking if the userland cookie
matches. Fix co
hi,
> Hi
>
> In perfuse, I attempt to reuse the same userland puffs node when the
> same file is looked up. I do that by searching an inode number match
> accross siblings.
>
> I experience unleasant things such as INACTIVE after RECLAIM on the same
> puffs node, which cause crashes since RECLAI
On Sun, Jul 01, 2012 at 09:05:20PM +, Christos Zoulas wrote:
> In article <4ff09c68.6000...@gmail.com>,
> Adam Hoka wrote:
> >
> >I plan to commit this if there are no good reasons or suggestions for an
> >alternative solution.
> >
> >I think it doesn't hide the problem, as it still prints a
In article <4ff09c68.6000...@gmail.com>,
Adam Hoka wrote:
>
>I plan to commit this if there are no good reasons or suggestions for an
>alternative solution.
>
>I think it doesn't hide the problem, as it still prints a warning as it
>used to. The only thing it removes is the bogus message about ki
On 6/26/2012 8:12 PM, Adam Hoka wrote:
> On 6/24/2012 10:23 AM, Adam Hoka wrote:
>> Hi!
>>
>> Can you guys please check if the following makes sense:
>>
>> http://www.netbsd.org/~ahoka/patches/timebackwards.diff
>>
>> The use case is the following:
>>
>> After starting NetBSD in vmware I see
On Sun, Jul 01, 2012 at 04:05:58AM +0200, Emmanuel Dreyfus wrote:
> In perfuse, I attempt to reuse the same userland puffs node when the
> same file is looked up. I do that by searching an inode number match
> accross siblings.
>
> I experience unleasant things such as INACTIVE after RECLAIM