Currently dump driver has some data
structures which are maintained in memory.
These data structures are initialized
when LKCD is configured. Some of the information
that these data structures contain includes
the dump flags, dump device etc.
These data structures are "unprotected" in the sense
that any rogue kernel code can wipe them out
and initiate dump. In that case, dump will fail
since the configuration information is lost.
This can be avoided if we put all dump driver related
information in the same page and mark
the page as "read-only" after LKCD is configured.
Thus configuration information will be
protected against any such "rogue" code.
This increases the reliability of the dump driver.
Pls let me know whether this requirement
of a "read-only" config page sounds reasonable
enough to be implemented in LKCD.
Thanks and Regards,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560033
Get latest updates about Open Source Projects, Conferences and News.