From: Al Viro <viro@ZenIV.linux.org.uk>
To: lkp@lists.01.org
Subject: Re: [vfs] b413afd673: kernel BUG at arch/x86/mm/physaddr.c:26!
Date: Tue, 19 Apr 2016 03:42:14 +0100 [thread overview]
Message-ID: <20160419024214.GC25498@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87zisqpgsj.fsf@yhuang-dev.intel.com>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
On Tue, Apr 19, 2016 at 08:45:48AM +0800, kernel test robot wrote:
> Hi,
>
> Here is the test result for T3.
>
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git T3
> commit b413afd67397cfc175a9656fc9e0444597a753e0 ("i_dir_seq (__d_add() only, with sanity checks for dir)")
Oh, I see... Try to add this (to be folded into the commit in original
branch):
diff --git a/mm/shmem.c b/mm/shmem.c
index 00d5d02..50447e6 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -3123,7 +3123,8 @@ static struct inode *shmem_alloc_inode(struct super_block *sb)
static void shmem_destroy_callback(struct rcu_head *head)
{
struct inode *inode = container_of(head, struct inode, i_rcu);
- kfree(inode->i_link);
+ if (S_ISLNK(inode->i_mode))
+ kfree(inode->i_link);
kmem_cache_free(shmem_inode_cachep, SHMEM_I(inode));
}
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp] [vfs] b413afd673: kernel BUG at arch/x86/mm/physaddr.c:26!
Date: Tue, 19 Apr 2016 03:42:14 +0100 [thread overview]
Message-ID: <20160419024214.GC25498@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87zisqpgsj.fsf@yhuang-dev.intel.com>
On Tue, Apr 19, 2016 at 08:45:48AM +0800, kernel test robot wrote:
> Hi,
>
> Here is the test result for T3.
>
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git T3
> commit b413afd67397cfc175a9656fc9e0444597a753e0 ("i_dir_seq (__d_add() only, with sanity checks for dir)")
Oh, I see... Try to add this (to be folded into the commit in original
branch):
diff --git a/mm/shmem.c b/mm/shmem.c
index 00d5d02..50447e6 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -3123,7 +3123,8 @@ static struct inode *shmem_alloc_inode(struct super_block *sb)
static void shmem_destroy_callback(struct rcu_head *head)
{
struct inode *inode = container_of(head, struct inode, i_rcu);
- kfree(inode->i_link);
+ if (S_ISLNK(inode->i_mode))
+ kfree(inode->i_link);
kmem_cache_free(shmem_inode_cachep, SHMEM_I(inode));
}
next prev parent reply other threads:[~2016-04-19 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 0:45 [vfs] b413afd673: kernel BUG at arch/x86/mm/physaddr.c:26! kernel test robot
2016-04-19 0:45 ` [lkp] " kernel test robot
2016-04-19 2:42 ` Al Viro [this message]
2016-04-19 2:42 ` Al Viro
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=20160419024214.GC25498@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=lkp@lists.01.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: 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.