All of lore.kernel.org
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: qiyong@fc-cn.com, clameter@sgi.com, mm-commits@vger.kernel.org
Subject: - set_page_refcounted-vm_bug_on-fix.patch removed from -mm tree
Date: Tue, 05 Feb 2008 14:32:16 -0800	[thread overview]
Message-ID: <200802052231.m15MVvAV012201@imap1.linux-foundation.org> (raw)


The patch titled
     set_page_refcounted() VM_BUG_ON fix
has been removed from the -mm tree.  Its filename was
     set_page_refcounted-vm_bug_on-fix.patch

This patch was dropped because it was merged into mainline or a subsystem tree

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: set_page_refcounted() VM_BUG_ON fix
From: Qi Yong <qiyong@fc-cn.com>

The current PageTail semantic is that a PageTail page is first a
PageCompound page.  So remove the redundant PageCompound test in
set_page_refcounted().

Signed-off-by: Qi Yong <qiyong@fc-cn.com>
Cc: Christoph Lameter <clameter@sgi.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/internal.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff -puN mm/internal.h~set_page_refcounted-vm_bug_on-fix mm/internal.h
--- a/mm/internal.h~set_page_refcounted-vm_bug_on-fix
+++ a/mm/internal.h
@@ -24,7 +24,7 @@ static inline void set_page_count(struct
  */
 static inline void set_page_refcounted(struct page *page)
 {
-	VM_BUG_ON(PageCompound(page) && PageTail(page));
+	VM_BUG_ON(PageTail(page));
 	VM_BUG_ON(atomic_read(&page->_count));
 	set_page_count(page, 1);
 }
_

Patches currently in -mm which might be from qiyong@fc-cn.com are

origin.patch
kill-an-unused-ptr_err-in-bdev_cache_init.patch

                 reply	other threads:[~2008-02-05 22:41 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=200802052231.m15MVvAV012201@imap1.linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=qiyong@fc-cn.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.