From: Jason Gunthorpe <jgg@nvidia.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
lkft-triage@lists.linaro.org, linux-mm <linux-mm@kvack.org>,
LTP List <ltp@lists.linux.it>, John Hubbard <jhubbard@nvidia.com>,
Alistair Popple <apopple@nvidia.com>,
Christoph Hellwig <hch@infradead.org>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
David Howells <dhowells@redhat.com>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.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))
Date: Tue, 7 Feb 2023 08:39:35 -0400 [thread overview]
Message-ID: <Y+JGh0+a540TLr6V@nvidia.com> (raw)
In-Reply-To: <CA+G9fYvAURcTwqyGwoTpxAOR0EDTbU6a71d5z74R4Wv-qT02OQ@mail.gmail.com>
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@linaro.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
prev parent reply other threads:[~2023-02-07 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 8:39 Naresh Kamboju
2023-02-07 12:39 ` Jason Gunthorpe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+JGh0+a540TLr6V@nvidia.com \
--to=jgg@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=arnd@arndb.de \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=imbrenda@linux.ibm.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=naresh.kamboju@linaro.org \
--cc=rppt@kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox