[1.] One line summary of the problem:
buz.c, 6pack.c use nonexistant KMALLOC_MAXSIZE in 2.4.3
[2.] Full description of the problem/report:
buz.c:2837: `KMALLOC_MAXSIZE' undeclared (first use in this function)
in kernel-source-2.4.3:
$ find . -name '*.h' | xargs grep KMALLOC_MAXSIZE
$ find . -name '*.c' | xargs grep KMALLOC_MAXSIZE
./drivers/media/video/buz.c: * If v4l_bufsize <= KMALLOC_MAXSIZE we use kmalloc
./drivers/media/video/buz.c: if (v4l_bufsize <= KMALLOC_MAXSIZE) {
./drivers/media/video/buz.c: * If the requested buffer size is smaller than
KMALLOC_MAXSIZE,
./drivers/media/video/buz.c: * size to KMALLOC_MAXSIZE in that case (which forces
contiguous allocation).
./drivers/media/video/buz.c: alloc_contig = (zr->jpg_bufsize < KMALLOC_MAXSIZE);
./drivers/media/video/buz.c: alloc_contig = (zr->jpg_bufsize < KMALLOC_MAXSIZE);
./drivers/media/video/buz.c: if (zr->need_contiguous && br.size >
KMALLOC_MAXSIZE)
./drivers/media/video/buz.c: br.size = KMALLOC_MAXSIZE;
./drivers/net/hamradio/6pack.c: if (sixpack_maxdev * sizeof(void*) >= KMALLOC_MAXSIZE)
{
$ find ../kernel-source-2.2.19 -name '*.h' | xargs grep KMALLOC_MAXSIZE
[3.] Keywords (i.e., modules, networking, kernel):
kernel, release engineering, drivers
[4.] Kernel version (from /proc/version):
2.4.3
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
N/A
[6.] A small shell script or example program which triggers the
problem (if possible)
make-kpkg
[7.] Environment
debian, kernel-source-2.4.2 patched up to 2.4.3
[7.1.] Software (add the output of the ver_linux script here)
N/A
[7.2.] Processor information (from /proc/cpuinfo):
N/A
[7.3.] Module information (from /proc/modules):
N/A
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
N/A
[7.5.] PCI information ('lspci -vvv' as root)
N/A
[7.6.] SCSI information (from /proc/scsi/scsi)
N/A
[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
N/A
[X.] Other notes, patches, fixes, workarounds:
Doing at least a "christmas tree" build ("all lights on", though in
this case "build *everything* that can be built as a module, and use
the config defaults for the rest" would be quite enough to catch
these) before it goes out the door would be useful...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
