From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 124651] ext4 bugon panic when I mmap a file
Date: Tue, 19 Jul 2016 01:39:03 +0000 [thread overview]
Message-ID: <bug-124651-13602-8p0nfiWBQP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-124651-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=124651
--- Comment #2 from wangguang <35445233@qq.com> ---
fs/ext4/inode.c:2263:mpage_prepare_extent_to_map:
2261: lblk = ((ext4_lblk_t)page->index) <<
(PAGE_CACHE_SHIFT - blkbits);
2263: head = page_buffers(page);
EXT4 BUG_ON page_buffers() because a page goes to writeback without
buffer-heads attached.
I think unmap_page_range set the page dirty again Cause the problem。
I can recurrent the bug by:
(1) mmap a file
addr = (char *)mmap(NULL, MAPLEN, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0);
memset(addr, 'i', MAPLEN);
(2) return err at
ext4_writepages->mpage_map_and_submit_extent->mpage_map_one_extent Cause the
log:
ext4_msg(sb, KERN_CRIT,
"Delayed block allocation failed for "
"inode %lu at logical offset %llu with"
" max blocks %u with error %d",
inode->i_ino,
(unsigned long long)map->m_lblk,
(unsigned)map->m_len, -err);
(3) Unmap case warning:
WARNING: at fs/buffer.c:661 __set_page_dirty+0xaa/0xc0()
(4) wait for sync,then bugon
see the attachment please.
--
You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-07-19 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 2:09 [Bug 124651] New: ext4 bugon panic when I mmap a file bugzilla-daemon
2016-07-18 13:25 ` [Bug 124651] " bugzilla-daemon
2016-07-19 1:39 ` bugzilla-daemon [this message]
2016-07-19 1:40 ` bugzilla-daemon
2016-07-19 1:40 ` bugzilla-daemon
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=bug-124651-13602-8p0nfiWBQP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.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.