[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: df triggering deallocation of an invalid port?
From: |
Justus Winter |
Subject: |
Re: df triggering deallocation of an invalid port? |
Date: |
Tue, 23 Sep 2014 12:51:38 +0200 |
User-agent: |
alot/0.3.5 |
Hey Thomas :)
Quoting Thomas Schwinge (2014-09-23 12:26:01)
> Hi!
>
> The root filesystem and the one backing ~/ are two separate instances of
> ext2fs. I just ran »dh -h ~/« , and noticed on the GNU Mach console:
> »task e19b6e10 deallocating an invalid port 1047, most probably a bug.«
> As it is one of the few Mach tasks that don't get a proper name set (as
> far as I know),
Only if your gnumach is oldish, 4e55e562 sets the name of tasks
created by the boot script. I do not know whether Samuel pulled this
into the Debian package though.
> I suspect it is the root filesystem that has been printing this.
I see quite a lot of tasks without proper names, I suspect fork w/o exec...
> Running df again, it does not reproduce. (But I've seen this
> before, so probably "once per system boot".) Per rpctrace, df is
> doing all kinds of RPCs. Issue to be confirmed, and to be analyzed.
Try rpctracing `/hurd/mtab /' instead of doing df.
Cheers,
Justus