filp_open() in 2.2.19 causes memory corruption
A message that is not in the archive (sent off-list or not yet received): [email protected]
On Mon, Apr 23, 2001 at 11:47:27PM +0100, David Woodhouse wrote:
David/LKML,
I've gotten to the bottom of this problem, and you are correct that klog is trashing the messages file for the oops. As for the oops, it was related to the use of ll_rw_blk() instead of submit_bh() in 2.4.3 which was causing
memory corruption in Linus' buffer cache code. In NetWare, we used to
create a signature field for I/O and other structures that were submitted by modules other than the media manager.
This would be useful for the buffer cache to put in a signature field so if he ever gets back a buffer head that is not his, the buffer cache could drop it with a noisy message rather than have memory corruption and other side effects that take days to track down.
Jeff
Quoted 1 line
Quoted 2 lines · [email protected] said:
I've gotten to the bottom of this problem, and you are correct that klog is trashing the messages file for the oops.
Oh dear. That's quite a serious bug in klogd. It should never destroy the original information, _especially_ if the System.map it's looking at blatantly doesn't match /proc/ksyms.
Have you reported it to your distribution vendor yet?
--
dwmw2