When booting sys-kernel/hardened-sources-4.4.2 the jfs partitions fail to mount because PAX detects a size overflow. PAX' message reads as follows: PAX: size overflow detected in function diMount fs/jfs/jfs_imap.c:143 cicus.289_68 max, count: 23, decl: inofree; num: 0; context: iagctl;
(In reply to Sam from comment #0) > When booting sys-kernel/hardened-sources-4.4.2 the jfs partitions fail to > mount because PAX detects a size overflow. PAX' message reads as follows: > > PAX: size overflow detected in function diMount fs/jfs/jfs_imap.c:143 > cicus.289_68 max, count: 23, decl: inofree; num: 0; context: iagctl; Looks like a classic overflow.
This is a known problem: https://forums.grsecurity.net/viewtopic.php?f=3&t=4398
(In reply to Emese Revfy from comment #2) > This is a known problem: > https://forums.grsecurity.net/viewtopic.php?f=3&t=4398 thanks Emese, is it fixed yet?
(In reply to Anthony Basile from comment #3) > (In reply to Emese Revfy from comment #2) > > This is a known problem: > > https://forums.grsecurity.net/viewtopic.php?f=3&t=4398 > > thanks Emese, is it fixed yet? We are still waiting for the original reporter to report it upstream.
Thanks for your swift replies! I sent a message to the maintainer of JFS, with Emese on CC.
(In reply to Sam from comment #5) > Thanks for your swift replies! I sent a message to the maintainer of JFS, > with Emese on CC. Did upstream JFS work on this? Did the fix trickle down yet?
Not that I know of. The maintainer did post a brief message on GRSecurity forums back in March, though. Personally, I decided to move away from JFS.
We'll come back to this if someone else hits it.