[ENBD] 2.4.21 dual athlon 1GB ram enbd problem

Peter T. Breuer enbd@lists.community.tummy.com
Wed, 6 Aug 2003 11:42:01 +0200 (MET DST)


"Peter T. Breuer wrote:"
> "Rene Villalon wrote:"
> > For 2.4.30 Under 2.4.21 it went away after I put the module on
> > /lib/modules/2.4.21/kernel/drivers/block and ran a depmod.
> 
> So there is some support module needed? Which contains kunmap_high()?
> 
> > > > # insmod /tmp/enbd.o
> > > > /tmp/enbd.o: unresolved symbol kunmap_high
> > > > /tmp/enbd.o: unresolved symbol highmem_start_page
> > > > /tmp/enbd.o: unresolved symbol kmap_high
> > >
> > > Well, those ought to be in the kernel, or something like them.
> > > kunmap_high is introduced in asm/highmem.h (in my 2.4.20-xfs).
> 
> BTW, if you delete all references to nbd_rw_iovec in the code, the
> kunmap problem should go away. It seems to be used in the raw device

I put up a 2.4.31 update that won't compile the raw interface stuff if
you magic -DNO_RAW_TRANSFERS into the compile flags somehow. That
should cure the problem wholesale as far as I can see.

The "raw interface" is a character device on the same major as the enbd
block device. It's not needed since one can bidn the generic raw device
to any block device, but I was curious to see if a direct
implementation offered any advantages.

Anyway, in a fit of optimism I took a carving knife out and removed the
built-in raid1 support, since taht shoudl be supported by fr1 now. The
result still seems to work, so with that I'll actually finally issue
2.4.31 and move on.


Peter