Tech Insider					     Technology and Trends

		        GNOME Mailing List Archives

From: (William R. Dirks)
Subject: Can't write vmalloc() mem in interrupt, 2.1.125/6
Date: 1998/10/23
Message-ID: <>#1/1
X-Deja-AN: 404206278
Organization: Netcom
Newsgroups: comp.os.linux.development.system

I seem to have found a serious bug in the current kernels, and I haven't 
seen any mention of it.

I have a module (a video capture driver), and any write to vmalloc()ed 
memory buffers that I do at interrupt time (in bottom half) does not 
appear in the buffer when the buffer is read later. I tried writing to 
the buffer in non-interrupt code, and that works.

There is no fault. I don't know where the memory accesses are going.

I developed this module on 2.1.106, where it works fine. I recently got
2.1.125, and noticed this problem. I now have the 2.1.126-2 patch, and it
is still there. 

I have a K6 and I compiled the kernel for 686/K6. At least one other 
person has seen this, so it is not just me or my system. Does anybody 
know anything about this?


			        About USENET

USENET (Users’ Network) was a bulletin board shared among many computer
systems around the world. USENET was a logical network, sitting on top
of several physical networks, among them UUCP, BLICN, BERKNET, X.25, and
the ARPANET. Sites on USENET included many universities, private companies
and research organizations. See USENET Archives.

		       SCO Files Lawsuit Against IBM

March 7, 2003 - The SCO Group filed legal action against IBM in the State 
Court of Utah for trade secrets misappropriation, tortious interference, 
unfair competition and breach of contract. The complaint alleges that IBM 
made concentrated efforts to improperly destroy the economic value of 
UNIX, particularly UNIX on Intel, to benefit IBM's Linux services 
business. See SCO vs IBM.

The materials and information included in this website may only be used
for purposes such as criticism, review, private study, scholarship, or

Electronic mail:			       WorldWideWeb: