[Crash-utility] transaction_t in jbd module vs. transaction_t in jbd2 module

[Brad Hubbard]

Hello,

We recently encountered an issue where a transaction_t struct appeared 
to be corrupt but this ended up being a symbol conflict as the customer 
was using ext3 and ext4 and had both modules in use. Unloading the jbd 
module did not help and the only way to see the correct representation 
of the the transaction_t struct in question was to restart crash without 
any modules loaded and load only the jbd2 module.

Is this a known issue? Is there a strategy that needs to be followed for 
dealing with duplicate symbols?

-- 

Kindest Regards,

Brad Hubbard
Software Maintenance Engineer
Red Hat Global Support Services
Asia Pacific Region