linux-kernel - Re: LTP: preadv03: WARNING: CPU: 0 PID: 101250 at mm/gup.c:2121 is_valid_gup

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: <Y+JGh0+a540TLr6V@nvidia.com>
Date:   Tue, 7 Feb 2023 08:39:35 -0400
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     open list <linux-kernel@...r.kernel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        lkft-triage@...ts.linaro.org, linux-mm <linux-mm@...ck.org>,
        LTP List <ltp@...ts.linux.it>,
        John Hubbard <jhubbard@...dia.com>,
        Alistair Popple <apopple@...dia.com>,
        Christoph Hellwig <hch@...radead.org>,
        Claudio Imbrenda <imbrenda@...ux.ibm.com>,
        David Hildenbrand <david@...hat.com>,
        David Howells <dhowells@...hat.com>,
        Mike Rapoport <rppt@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: LTP: preadv03: WARNING: CPU: 0 PID: 101250 at mm/gup.c:2121
 is_valid_gup_args (mm/gup.c:2121 (discriminator 1))

On Tue, Feb 07, 2023 at 02:09:27PM +0530, Naresh Kamboju wrote:
> Following test regressions noticed on Linux next-20230207.
> LTP syscalls pwritev03 and preadv03 failed.
> The tests use external mounted SSD drives for creating tmp files.
> 
> Regressions found on arm64 juno-r2 and x86:
>   - ltp-syscalls/pwritev03
>   - ltp-syscalls/preadv03
>   - ltp-syscalls/pwritev03_64
>   - ltp-syscalls/preadv03_64
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>

Yes, this is what Stephen noticed, it is a merge resolution problem
in linux-next

https://lore.kernel.org/all/Y+JBak3Tt8Pdw3yE@nvidia.com/

Jason