linux-kernel - Re: Bug in current -git tree causing dbus and gnome to chew up cpu time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 14 Feb 2007 09:39:10 +1100
From:	Neil Brown <neilb@...e.de>
To:	Greg KH <greg@...ah.com>
Cc:	Andreas Gruenbacher <agruen@...e.de>,
	torvalds@...ux-foundation.org, viro@...iv.linux.org.uk, hch@....de,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: Bug in current -git tree causing dbus and gnome to chew up cpu time

On Tuesday February 13, greg@...ah.com wrote:
> 
> This causes the following to just loop over and over, incrementing the
> pid:
> 
> gnome-vfs-daemo(8914): 

That's odd.  getcwd returning an empty string.
I can only see that happening if you do the equivalent of
   chdir("/");
   chroot("/somewhere");
   getcwd(buf,sizeof(buf));

That would return an empty string with the new code but not with the
old.
But I cannot imagine gnome-vfs-daemon doing a chroot, as it does not
run as root.

You could try removing the
		if (*buffer == '/') {
			buffer++;
			buflen++;
		}
from the new __d_path.  But that still wouldn't really explain what
was happening.

Maybe also put a WARN_ON(! *buffer) just before the return to find out
exactly what is going on when the empty string is returned.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/