LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 03-08-2004, 06:04 PM   #1
KingofBLASH
Member
 
Registered: Sep 2003
Distribution: Just upgraded to Slackware 10.0
Posts: 91

Rep: Reputation: 15
When will the mremap() kernel bug get patched?


There was an announcement on Slashdot about a new Linux kernel vulnerability. I checked the slackware security page and still no fix. Anybody know an ETA for a fix, and if it's worth worrying about?

Thanks,

Dan
 
Old 03-08-2004, 06:06 PM   #2
trickykid
Guru
 
Registered: Jan 2001
Posts: 24,133

Rep: Reputation: 199Reputation: 199
You can get the patches from www.kernel.org

Don't necessarily always have to wait for Patrick to make his own for Slackware, etc.
 
Old 03-08-2004, 06:17 PM   #3
KingofBLASH
Member
 
Registered: Sep 2003
Distribution: Just upgraded to Slackware 10.0
Posts: 91

Original Poster
Rep: Reputation: 15
I know that this is the second mremap() fix. Is this the correct version:

<akpm@osdl.org>
[PATCH] mremap NULL pointer dereference fix

This is a cleaned-up version of a mremap() fix for "move_one_page()"
by Rajesh Venkatasubramanian <vrajesh@umich.edu>. We could use a NULL
"src" pointer.

Because while we do hold the MM semaphore over the whole sequence, the
destination page table allocation will possibly drop the page table
spinlock. That in turn can cause a clean source page to be stolen by
page reclaim, causing the source-side "get_one_pte_map_nested()" to
return NULL the second time around even if it didn't on the first case.

So we just check "src" again, and get rid of the bogus TLB invalidate
while we're at it.
 
Old 03-08-2004, 06:26 PM   #4
trickykid
Guru
 
Registered: Jan 2001
Posts: 24,133

Rep: Reputation: 199Reputation: 199
Are you using the 2.4.x series or 2.6.x series? 2.4.25 will fix it in that series and I do believe the 2.6.3 is the fix for that series.

Regards.
 
Old 03-08-2004, 06:53 PM   #5
Dravis
LQ Newbie
 
Registered: Aug 2003
Distribution: Slackware 9.1
Posts: 15

Rep: Reputation: 0
That Slashdot story was a dupe. All they reported was a document that showed more info about the second mremap bug than was initally disclosed. There is no third mremap bug.

It has been known and fixed for a while (kernel 2.4.25 has the fix).
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Debian patched kernel vs official Linux Kernel gerald45 Debian 7 10-12-2005 05:45 AM
About Kernel after getting patched small_boy22 Linux - General 3 05-19-2005 11:54 AM
Fedora Patched kernel for Win4Lin ekp Fedora 2 03-28-2005 08:17 AM
Second mremap critical bug zuessh Linux - Security 19 02-24-2004 07:24 PM
should I be worried about the Second mremap critical bug? Mandrake 9.2 user Fear58 Linux - Security 3 02-21-2004 01:42 PM


All times are GMT -5. The time now is 06:51 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration