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]
Date: Wed, 5 Jun 2024 16:53:58 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: open list <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org,
	Linux Regressions <regressions@...ts.linux.dev>,
	linux-nfs@...r.kernel.org, NeilBrown <neilb@...e.de>,
	Arnd Bergmann <arnd@...db.de>,
	Trond Myklebust <trond.myklebust@...merspace.com>,
	Anna Schumaker <anna@...nel.org>, kasong@...cent.com,
	LTP List <ltp@...ts.linux.it>
Subject: Re: WARNING: at fs/nfs/nfs3xdr.c:188 encode_filename3 on rk3399

On Thu, May 30, 2024 at 06:54:05PM +0530, Naresh Kamboju wrote:
> The following kernel warning has been noticed while running LTP statvfs01
> testcase on arm64 device rk3399-rock-pi-4b with NFS mounted test setup and
> started from Linux next-20240522 tag and till next-20240529.
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> 
> Test log:
> -----
> mke2fs 1.47.0 (5-Feb-2023)
> tst_test.c:1131: TINFO: Mounting /dev/loop0 to /scratch/ltp-9gvw[
> 5211.161721] EXT4-fs (loop0): mounting ext2 file system using the ext4
> subsystem
> F2L8n6/LTP_stadLH0F7/mntpoint fstyp=ext2 flags=0
> [ 5211.169391] EXT4-fs (loop0): mounted filesystem
> af9dfac2-88f6-453d-9d02-c14cc888a51d r/w without journal. Quota mode:
> none.
> statvfs01.c:32: TPASS: statvfs(TEST_PATH, &buf) passed
> [ 5211.175518] ------------[ cut here ]------------
> statvfs01.c:44: TPASS: creat(valid_fname, 0444) returned fd 3
> [ 5211.175938] WARNING: CPU: 5 PID: 786885 at fs/nfs/nfs3xdr.c:188
> encode_filename3+0x4c/0x60

I believe this was be fixed by Neil's patch which was merged:

https://lore.kernel.org/all/171693789645.27191.13475059024941012614@noble.neil.brown.name/

regards,
dan carpenter


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ