public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/lib/mm memlock.c Date: Mon, 08 Mar 2010 15:55:00 -0000 [thread overview] Message-ID: <20100308155553.13375.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2010-03-08 15:55:53 Modified files: lib/mm : memlock.c Log message: Unconditionaly ignore also Virtual Dynamically-linked Shared Object (VDSO on 32bit is VSyscall on 64bit) It seems it could be locked on 64bit kernels running 32bit binaries, but it makes troubles on real 32bit machines where mlock() returns error when trying to lock such map area. (0xffffe000) Behavior of mlockall() seems to be similar. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/mm/memlock.c.diff?cvsroot=lvm2&r1=1.17&r2=1.18 --- LVM2/lib/mm/memlock.c 2010/03/05 15:14:03 1.17 +++ LVM2/lib/mm/memlock.c 2010/03/08 15:55:52 1.18 @@ -59,7 +59,8 @@ /* list of maps, that are unconditionaly ignored */ static const char * const _ignore_maps[] = { - "[vsyscall]" + "[vdso]", + "[vsyscall]", }; /* default blacklist for maps */
next reply other threads:[~2010-03-08 15:55 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-03-08 15:55 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-03-01 21:19 zkabelac 2012-02-01 10:48 zkabelac 2011-06-01 19:26 agk 2011-03-06 17:52 zkabelac 2011-02-18 14:51 zkabelac 2010-10-25 13:00 zkabelac 2010-10-15 9:48 zkabelac 2010-07-08 14:47 zkabelac 2010-07-08 13:05 zkabelac 2010-04-01 14:53 zkabelac 2010-04-01 13:43 zkabelac 2010-03-30 14:41 zkabelac 2010-03-30 14:41 zkabelac 2010-03-09 12:31 agk 2010-03-09 10:25 zkabelac 2010-03-08 17:14 zkabelac 2010-03-05 15:14 zkabelac 2009-11-18 18:22 mornfall 2008-05-28 23:12 agk
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100308155553.13375.qmail@sourceware.org \ --to=zkabelac@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).