linux-kernel - fs cache patch breaks sparc build in 2.6.18-rc4-mm2

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

Message-Id: <20060824131544.aa9223f0.pj@sgi.com>
Date:	Thu, 24 Aug 2006 13:15:44 -0700
From:	Paul Jackson <pj@....com>
To:	linux-kernel@...r.kernel.org
Cc:	David Howells <dhowells@...hat.com>,
	Trond Myklebust <trond.myklebust@....uio.no>,
	Andrew Morton <akpm@...l.org>
Subject: fs cache patch breaks sparc build in 2.6.18-rc4-mm2

The 2.6.18-rc4-mm2 patch:
    fs-cache-make-kafs-use-fs-cache.patch

seems to break the arch=sparc defconfig build, failing with:

  CC [M]  fs/afs/file.o
fs/afs/file.c: In function `afs_file_releasepage':
fs/afs/file.c:332: error: structure has no member named `cache'
make[2]: *** [fs/afs/file.o] Error 1

Looking at line numbers 326-337 in the file fs/afs/file.c, I see:

326             /* deny */
327             if (PageFsMisc(page)) {
328                     _leave(" = F");
329                     return 0;
330             }
331
332             fscache_uncache_page(AFS_FS_I(page->mapping->host)->cache, page);
333
334             /* indicate that the page can be released */
335             _leave(" = T");
336             return 1;
337     }

So this does seem to be the line 332 the compile is complaining about.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.925.600.0401
-
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/