[Crash-utility] [RFC PATCH v2 0/2] Show memory overcommit data in dump_kmeminfo()

Aaron Tomlin atomlin at redhat.com
Wed Dec 3 15:25:17 UTC 2014


On Wed 2014-12-03 10:18 -0500, Dave Anderson wrote:
> 
> 
> ----- Original Message -----
> > On Tue 2014-12-02 12:11 -0500, Dave Anderson wrote:
> > > Hi Aaron,
> > >
> > > I've got a RHEL4 kernel which shows a COMMIT LIMIT of zero, and then
> > > dies with a SIGFPE:
> > [ ... ]
> > > Program received signal SIGFPE, Arithmetic exception.
> > > dump_kmeminfo () at memory.c:7970
> > > 7970						/ allowed) : 0;
> > 
> > OK.
> > 
> > > So there also needs to be an allowance for this:
> > [ ... ]
> > >   crash> p sysctl_overcommit_ratio
> > >   sysctl_overcommit_ratio = $2 = 0
> > >   crash>
> > 
> > Quick question, would you prefer to silently bail out of displaying memory
> > over commitment details in the event of a 0 value for "allowed" or print as
> > follows:
> > 
> >    COMMIT LIMIT        0            0         ----
> >       COMMITTED  1150595       4.4 GB         ----
> 
> I guess I would prefer the above, unless you feel that it's misleading?

OK I prefer the above too.

-- 
Aaron Tomlin




More information about the Crash-utility mailing list