linux-kernel - Re: ext3 build failure: "log_start_commit" [fs/ext3/ext3.ko] undefined

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20091112094042.GC14528@duck.suse.cz>
Date:	Thu, 12 Nov 2009 10:40:42 +0100
From:	Jan Kara <jack@...e.cz>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: ext3 build failure: "log_start_commit" [fs/ext3/ext3.ko]
	undefined

On Thu 12-11-09 01:22:01, Stefan Richter wrote:
> Hi Jan,
> 
> I just pulled linux-2.6.git and got this:
> ERROR: "log_start_commit" [fs/ext3/ext3.ko] undefined!
> 
> I guess it is due to "ext3: Wait for proper transaction commit on fsync".
> 
> Is this log_start_commit() of fs/jbd/journal.c?
> 
> $ grep -e JBD -e EXT3 .config
> CONFIG_EXT3_FS=m
> # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
> # CONFIG_EXT3_FS_XATTR is not set
> CONFIG_JBD=m
> CONFIG_JBD2=m
  Yes, thanks. I've already merged the fix.

								Honza

-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/