From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12790] New: kernel build warning causes EXT4 boot warning
Date: Sat, 28 Feb 2009 02:25:46 -0800 (PST) [thread overview]
Message-ID: <bug-12790-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=12790
Summary: kernel build warning causes EXT4 boot warning
Product: File System
Version: 2.5
KernelVersion: 2.6.28.7
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: thoralf.dassler@gmail.com
Latest working kernel version: unknown
Earliest failing kernel version: unknown
Distribution: Slamd64
Hardware Environment: Toshiba Satellite P200
Software Environment: n/a
Problem Description: Boot message:
EXT4-fs warning (device sda1): ext4_fill_super: extents feature not enabled on
this filesystem, use tune2fs.
Steps to reproduce: boot into Linux
I get these lines when I build the kernel:
CC fs/ext4/super.o
fs/ext4/super.c: In function 'ext4_fill_super':
fs/ext4/super.c:2177: warning: format '%u' expects type 'unsigned int', but
argument 2 has type 'ext4_group_t'
See .config attached. I also noticed several patches on Google, but am
reluctant to apply them.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-02-28 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 10:25 bugme-daemon [this message]
2009-02-28 10:26 ` [Bug 12790] kernel build warning causes EXT4 boot warning bugme-daemon
2009-02-28 14:12 ` bugme-daemon
2009-02-28 16:07 ` bugme-daemon
2009-05-19 19:14 ` 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-12790-13602@http.bugzilla.kernel.org/ \
--to=bugme-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 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 NNTP newsgroup(s).