From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 10 02:37:12 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF6B81065673 for ; Tue, 10 Apr 2012 02:37:12 +0000 (UTC) (envelope-from sushanth_rai@yahoo.com) Received: from nm20.bullet.mail.sp2.yahoo.com (nm20.bullet.mail.sp2.yahoo.com [98.139.91.90]) by mx1.freebsd.org (Postfix) with SMTP id AEF628FC18 for ; Tue, 10 Apr 2012 02:37:12 +0000 (UTC) Received: from [98.139.91.64] by nm20.bullet.mail.sp2.yahoo.com with NNFMP; 10 Apr 2012 02:37:12 -0000 Received: from [98.139.44.67] by tm4.bullet.mail.sp2.yahoo.com with NNFMP; 10 Apr 2012 02:37:12 -0000 Received: from [127.0.0.1] by omp1004.access.mail.sp2.yahoo.com with NNFMP; 10 Apr 2012 02:37:12 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 193849.89033.bm@omp1004.access.mail.sp2.yahoo.com Received: (qmail 5222 invoked by uid 60001); 10 Apr 2012 02:37:11 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1334025431; bh=FTdBq8vK0mYYL7OzYYfVAlC+sBnQW0vFehjb4cXxYDU=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=Jfwr+KJUC8+5wMZE+2a7Yc+Yh4NMOkj7OAJ5Q0l17lmmtHgbqbjRVApQEGzPh0v7aLWlSvgdZKTuGOe+NYUzLLbI9JSiRkbZVdFDctkmAW71D20dJvujGcg4nf/yHuHfWCCOU2utXGH6U80KIn7Fssd407EMEBspGLfpaJrMxGs= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=ZzQ8Wk+7Tnr8ceIp+zmdwrMynM8/XKs2zgxOP0GEMNLufIkJQYfUwcYeIoB9ph2yRdW1D/hfwFa9UnKrF4Vc1JX9nV97sBdANj+QUU34TQNJtJnm6AcDNF+eod2m8MfV12jWNy4HXQKCJ/5znJKoPP51Z/DkySVF2IAT6OWmr40=; X-YMail-OSG: GldXdi4VM1kwL3tWjWWOOp4uT3OJu.ZTPUfo7OLOvVTLdGA xUp7GO0hEU5sRAyypB2nW4JOVC4QWC2n_.RpoOHUGXk8AZkMC2jkSMEpVnJg LzPv71X0Dyg_Gaa2xwDh45Yd1eD.z40HsBLdCmY8p1YoSeCZtt3hF0eqNwo8 aCZK5yBQ_R0xbwJnaKaNFvTRNZM6ss2r6uAo7UamhW2Snje4JdxfmWjNFst2 zcHJplaD_pv6Zpm9e.YUTucVSnHTIs0Ej41_RQyATNw0TWlnlPsXqFHINya. v.WbOOUr1TFeOyB6l68_OV9sVuLFcX8WTiKdVg69Ih4uCWzrbCUN9DPshBkW IIn_PSS3RVllZOU9rfR.SzGiR.YGH1PcMPa9wsdKWGnYfKMEwpjnZPKX23FQ dQh0N8tzokPgebB346QKY1eEe9oMbmY4_tXoPcpYaRzjDklHDK70Em7eqA7r MdaPNHR8- Received: from [209.119.38.67] by web180011.mail.gq1.yahoo.com via HTTP; Mon, 09 Apr 2012 19:37:11 PDT X-Mailer: YahooMailClassic/15.0.5 YahooMailWebService/0.8.117.340979 Message-ID: <1334025431.77315.YahooMailClassic@web180011.mail.gq1.yahoo.com> Date: Mon, 9 Apr 2012 19:37:11 -0700 (PDT) From: Sushanth Rai To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: mlockall() on freebsd 7.2 + amd64 returns EAGAIN X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 02:37:13 -0000 Hello, I have a simple program that links with the math library. The only thing that program does is to call mlockall(MCL_CURRENT | MCL_FUTURE). This call to mlockall fails with EAGAIN. I figured out that kernel vm_fault() is returning KERN_PROTECTION_FAILURE when it tries to fault-in the mmap'ed math library address. But I can't figure why. The /proc//map returns the following for the process: 0x800634000 0x80064c000 24 0 0xffffff0025571510 r-x 104 52 0x1000 COW NC vnode /lib/libm.so.5 0x80064c000 0x80064d000 1 0 0xffffff016f11c5e8 r-x 1 0 0x3100 COW NNC vnode /lib/libm.so.5 0x80064d000 0x80074c000 4 0 0xffffff0025571510 r-x 104 52 0x1000 COW NC vnode /lib/libm.so.5 Since ntpd calls mlockall with same option and links with math library too, I look at map o/p of ntpd, which looks slightly different "resident" column (3rd column) on 3rd line: 0x800682000 0x80069a000 8 0 0xffffff0025571510 r-x 100 50 0x1000 COW NC vnode /lib/libm.so.5 0x80069a000 0x80069b000 1 0 0xffffff0103b85870 r-x 1 0 0x3100 COW NNC vnode /lib/libm.so.5 0x80069b000 0x80079a000 0 0 0xffffff0025571510 r-x 100 50 0x1000 COW NC vnode /lib/libm.so.5 I don't know if that has anything to do with failure. The snippet of code that returns failure in vm_fault() is the following: if (fs.pindex >= fs.object->size) { unlock_and_deallocate(&fs); return (KERN_PROTECTION_FAILURE); } Any help would be appreciated. Thanks, Sushanth