Re: 2.4.22pre6aa1

Sergey S. Kostyliov
2003-07-25T10:55:53Z

Hello Andrea,

On Friday 25 July 2003 09:28, you wrote:
> On Wed, Jul 23, 2003 at 03:21:15PM +0400, Sergey S. Kostyliov wrote:
> > Hello Andrea,

<cut>

> hmm, 2.4.22pre6aa1 was the first 2.4 largepages port to the >=22pre
> shmfs backport from 2.5. It could be a bug in 2.5, or a bug present only
> in the backport of the 2.5 code to 22pre, or even a bug only present in
> -aa due the largepage patch ported on top of the backport included in
> 22pre. I'll have a closer look at it tomorrow. The place where it
> crashed is:
>
> BUG_ON(inode->i_blocks);
>
> it might be only a minor accounting issue. It needs some auditing.

Thanks for you recponce!
Yes, it seems possible. At least it continue to run just fine after
oops for 2.4.22pre6aa1.
Btw I've managed to get a hard lockup with 2.4.22pre7aa1 in the same
scenario. It just stops responding to even Alt+SysRq+* from keyboard.

>
> I'm afraid you're the first one testing the shmfs backport in 22pre +
> the largepage support patch in my tree with a big app doing swapoff at
> the same time.
>
> Are you using bigpages btw?

No, I'm not using bigpages.

>
> thank you very much for the feedback,
>
> Andrea
>
> PS. shall this give us relevant problems in the debugging/auditing, I'll
> just give you a patch to backout the backport and go back to the shmfs
> code in 2.4.21rc8aa1 that is running rock solid in production with
> largepages (I doubt you need the loop device on top of shmfs anyways). I
> prefer not to spend much time on new 2.4 features.

I doubt it depends on bigpages because they
are not used in my setup. But I can live with that. Rule: do not run
`swapoff -a` under load doesn't sound as impossible in my case (if this
is the only way to trigger this problem).

--
Best regards,
Sergey S. Kostyliov <rathamahata@php4.ru>
Public PGP key: http://sysadminday.org.ru/rathamahata.asc