[EMAIL PROTECTED] (Russ Allbery)  wrote on 09.10.05 in <[EMAIL PROTECTED]>:

> Kai Henningsen <[EMAIL PROTECTED]> writes:
>
> > Package: inn2
> > Version: 2.4.2-3.colo.1
> > Severity: normal
> > File: tdx-util
>
> > tdx-util: tradindexed: entry 54313 is reachable from multiple paths
> > tdx-util: tradindexed: entry 54304 is reachable from multiple paths
> > tdx-util: tradindexed: entry 54313 is reachable from multiple paths
> > tdx-util: tradindexed: entry 54304 is reachable from multiple paths
> > tdx-util: tradindexed: entry 54313 is reachable from multiple paths
> > tdx-util: tradindexed: entry 54304 is reachable from multiple paths
> > tdx-util: tradindexed: entry 54313 is reachable from multiple paths
> > tdx-util: tradindexed: entry 54304 is reachable from multiple paths
> > tdx-util: tradindexed: entry 54313 is reachable from multiple paths
> > tdx-util: tradindexed: entry 54304 is reachable from multiple paths
> > [and so on]
> > (2.4.2-3.colo.1 is exactly like 2,4,2-3 except for
> > DEB_BUILD_OPTIONS=nostrip)
>
> This is a type of corruption that tdx-util isn't smart enough to fix.  I'm
> not sure how the corruption happened in the first place, though.  tdx-util

I'm pretty certain it was memory corruption.

> can detect hash chain loops of length one, but doesn't have any code to
> detect longer ones.
>
> I'm probably not going to get a chance to add code for that any time soon,
> but patches are welcome.  In the meantime, I've added it to TODO.

I ended up rebuilding the complete overview with tdx-util. Probably not  
the most optimal solution.


MfG Kai


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to