linux-ext4 - Re: next: ext4 build failure

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <50BDFDB4.30002@tao.ma>
Date:	Tue, 04 Dec 2012 21:42:12 +0800
From:	Tao Ma <tm@....ma>
To:	Theodore Ts'o <tytso@....edu>, Jiri Slaby <jslaby@...e.cz>,
	boyu.mt@...bao.com, linux-ext4@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: next: ext4 build failure

On 12/04/2012 09:40 PM, Tao Ma wrote:
> Hi Ted,
> On 12/04/2012 09:27 PM, Theodore Ts'o wrote:
>> On Tue, Dec 04, 2012 at 10:29:00AM +0100, Jiri Slaby wrote:
>>> Hi,
>>>
>>> commit a7b0168d4a9bb78535827ddaf9c055963f5bd7aa
>>> Author: Tao Ma <boyu.mt@...bao.com>
>>> Date:   Sun Dec 2 20:30:52 2012 -0500
>>>
>>>     ext4: let fallocate handle inline data correctly
>>>
>>> added
>>>
>>> static int int ext4_convert_inline_data(struct inode *inode)
>>>
>>>        ^^^^^^^
>>>
>>> when EXT4_FS_XATTR is unset.
>>>
>>> Care to fix that?
>>
>> Oops.  Thanks for catching this!!!
> Please push the patch with the subject "[PATCH] ext4: Fix inline data
> build warning found by kernel build testing." and these error should go
> away. And also Dan's smatch has found another issue and I have sent out
> the patch with subject "[PATCH] ext4: Fix inline data build warning
> found by kernel build testing.".
sorry, I hit the send button too fast. The subject for the 2nd patch is
"[PATCH] ext4: Fix a build warning in __ext4_journalled_writepage."
Sorry for all the trouble.

Thanks
Tao

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html