From: akpm@linux-foundation.org
To: dev@openvz.org, kuznet@ms2.inr.ac.ru, tony.luck@intel.com,
mm-commits@vger.kernel.org
Subject: - ia64-virt_to_page-can-be-called-with-null-arg.patch removed from -mm tree
Date: Wed, 07 Feb 2007 11:51:46 -0800 [thread overview]
Message-ID: <200702071951.l17Jpk5P025187@shell0.pdx.osdl.net> (raw)
The patch titled
IA64: virt_to_page() can be called with NULL arg
has been removed from the -mm tree. Its filename was
ia64-virt_to_page-can-be-called-with-null-arg.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: IA64: virt_to_page() can be called with NULL arg
From: Kirill Korotaev <dev@openvz.org>
It does not return NULL when arg is NULL.
Signed-off-by: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Signed-off-by: Kirill Korotaev <dev@openvz.org>
Cc: "Luck, Tony" <tony.luck@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/asm-ia64/pgalloc.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN include/asm-ia64/pgalloc.h~ia64-virt_to_page-can-be-called-with-null-arg include/asm-ia64/pgalloc.h
--- a/include/asm-ia64/pgalloc.h~ia64-virt_to_page-can-be-called-with-null-arg
+++ a/include/asm-ia64/pgalloc.h
@@ -137,7 +137,8 @@ pmd_populate_kernel(struct mm_struct *mm
static inline struct page *pte_alloc_one(struct mm_struct *mm,
unsigned long addr)
{
- return virt_to_page(pgtable_quicklist_alloc());
+ void *pg = pgtable_quicklist_alloc();
+ return pg ? virt_to_page(pg) : NULL;
}
static inline pte_t *pte_alloc_one_kernel(struct mm_struct *mm,
_
Patches currently in -mm which might be from dev@openvz.org are
origin.patch
allow-access-to-proc-pid-fd-after-setuid.patch
allow-access-to-proc-pid-fd-after-setuid-fix.patch
allow-access-to-proc-pid-fd-after-setuid-update.patch
reply other threads:[~2007-02-07 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200702071951.l17Jpk5P025187@shell0.pdx.osdl.net \
--to=akpm@linux-foundation.org \
--cc=dev@openvz.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tony.luck@intel.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.