[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e8d31e48-df6a-fde4-4c6b-c4ccf1664ded@linaro.org>
Date: Thu, 15 Jun 2023 10:52:03 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Anna Schumaker <schumaker.anna@...il.com>
Cc: Trond Myklebust <trondmy@...merspace.com>,
Anna Schumaker <Anna.Schumaker@...app.com>,
linux-nfs <linux-nfs@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Subject: Re: Regression: NULL pointer dereference after NFS_V4_2_READ_PLUS
(commit 7fd461c47)
On 14/06/2023 22:55, Anna Schumaker wrote:
>>>> Still null ptr (built on 420b2d4 with your patch):
>>>
>>> We're through the merge window and at rc1 now, so I can spend more
>>> time scratching my head over your bug again. We've come up with a
>>> patch (attached) that adds a bunch of printks to show us what the
>>> kernel thinks is going on. Do you mind trying it out and letting us
>>> know what gets printed out? You'll need to make sure
>>> CONFIG_NFS_V4_2_READ_PLUS is enabled when compiling the kernel.
>>
>> The patch does not apply. I tried: v6.4-rc1, v6.4-rc5, next-20230609.
>
> Can you try the attached patch on top of my 3-patch series from the
> other day, and let me know what gets printed out? It adds a bunch of
> printk()s at strategic points to print out what is going on with the
> xdr scratch buffer since it's suddenly a bad memory address after
> working for a bit on your machine.
>
Here you have entire log - attached (113 kB, I hope goes past mailing
lists/spam filters).
Best regards,
Krzysztof
View attachment "oops-nfs-read-plus-20230615.txt" of type "text/plain" (116050 bytes)
Powered by blists - more mailing lists