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 ./WHATS_NEW lib/mm/memlock.c Date: Wed, 30 Mar 2011 13:06:00 -0000 [thread overview] Message-ID: <20110330130614.3241.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-03-30 13:06:13 Modified files: . : WHATS_NEW lib/mm : memlock.c Log message: Few more files filtered from memory locking Code located in these files should not be used in critical section. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1965&r2=1.1966 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/mm/memlock.c.diff?cvsroot=lvm2&r1=1.38&r2=1.39 --- LVM2/WHATS_NEW 2011/03/30 12:43:32 1.1965 +++ LVM2/WHATS_NEW 2011/03/30 13:06:13 1.1966 @@ -1,5 +1,6 @@ Version 2.02.85 - =================================== + Extend the set of memory regions, that are not locked to memory. Enhance usability with the valgrind memcheck tool. Support regular quit of the lvm_thread_fn function in clvmd. Fix reading of unallocated memory in lvm1 format import function. --- LVM2/lib/mm/memlock.c 2011/03/30 12:43:32 1.38 +++ LVM2/lib/mm/memlock.c 2011/03/30 13:06:13 1.39 @@ -89,9 +89,11 @@ /* default blacklist for maps */ static const char * const _blacklist_maps[] = { "locale/locale-archive", + "/LC_MESSAGES/", "gconv/gconv-modules.cache", "/libreadline.so.", /* not using readline during mlock */ "/libncurses.so.", /* not using readline during mlock */ + "/libtinfo.so.", /* not using readline during mlock */ "/libdl-", /* not using dlopen,dlsym during mlock */ /* "/libdevmapper-event.so" */ };
next reply other threads:[~2011-03-30 13:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-30 13:06 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-01-12 18:29 agk 2011-06-12 0:23 agk 2011-03-06 16:47 mbroz 2010-09-30 11:32 zkabelac 2010-06-24 8:29 zkabelac
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=20110330130614.3241.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).