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: <20250211183531.4359-1-sj@kernel.org>
Date: Tue, 11 Feb 2025 10:35:31 -0800
From: SeongJae Park <sj@...nel.org>
To: "Arnd Bergmann" <arnd@...db.de>
Cc: SeongJae Park <sj@...nel.org>,
	"Naresh Kamboju" <naresh.kamboju@...aro.org>,
	"open list" <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>,
	"Linux PM" <linux-pm@...r.kernel.org>,
	rcu <rcu@...r.kernel.org>,
	"LTP List" <ltp@...ts.linux.it>,
	"Linux Regressions" <regressions@...ts.linux.dev>,
	lkft-triage@...ts.linaro.org,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Paul E. McKenney" <paulmck@...nel.org>,
	"Vincent Guittot" <vincent.guittot@...aro.org>,
	"Daniel Lezcano" <daniel.lezcano@...aro.org>,
	"Dan Carpenter" <dan.carpenter@...aro.org>,
	"Anders Roxell" <anders.roxell@...aro.org>
Subject: Re: next-20250210: WARNING: at include/linux/rwsem.h:85 madvise_unlock

On Tue, 11 Feb 2025 10:32:55 +0100 "Arnd Bergmann" <arnd@...db.de> wrote:

> On Tue, Feb 11, 2025, at 10:23, Naresh Kamboju wrote:
> > Regressions on arm64 Juno-r2 device while running LTP syscalls tests
> > madvise01 warnings on the Linux next-20250210 tag.
> >
> > First seen on next-20250210
> > Good: next-20250207
> > Bad: next-20250210
> 
> Cc SeongJae Park <sj@...nel.org>
[...]
> This is mmap_write_unlock() triggering
> rwsem_assert_held_write(&mm->mmap_lock);
> 
> That code was changed in these commits:
> 
> 415553982a1e mm-madvise-remove-redundant-mmap_lock-operations-from-process_madvise-fix
> ec68fbd9e99f mm/madvise: remove redundant mmap_lock operations from process_madvise()
> f19c9d7b57cf mm/madvise: split out madvise() behavior execution
> a4d5a73cdc14 mm/madvise: split out madvise input validity check
> 948a0a9ea070 mm/madvise: split out mmap locking operations for madvise()
> 
> You could try reverting them to see if that fixes it again.

Thank you for kindly Cc-ing me and further providing this nice information,
Arnd!  I posted a fix and continuing discussion there:
https://lore.kernel.org/20250211063201.5106-1-sj@kernel.org


Thanks,
SJ

[...]

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ