From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Anna Schumaker <schumaker.anna@gmail.com>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
Anna Schumaker <Anna.Schumaker@netapp.com>,
linux-nfs <linux-nfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Regression: NULL pointer dereference after NFS_V4_2_READ_PLUS (commit 7fd461c47)
Date: Wed, 21 Jun 2023 15:27:33 +0200 [thread overview]
Message-ID: <dfcc114f-56f1-e4ab-7b36-f9a4ce3e8c8c@linaro.org> (raw)
In-Reply-To: <CAFX2JfnH_rOFxn+uT4e1Eutea5En4_z26a-u_qCwOsnr5EowRw@mail.gmail.com>
On 21/06/2023 14:49, Anna Schumaker wrote:
> On Sat, Jun 17, 2023 at 6:09 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> On 15/06/2023 21:38, Anna Schumaker wrote:
>>> On Thu, Jun 15, 2023 at 1:16 PM Anna Schumaker <schumaker.anna@gmail.com> wrote:
>>>>
>>>> On Thu, Jun 15, 2023 at 1:04 PM Anna Schumaker <schumaker.anna@gmail.com> wrote:
>>>>>
>>>>> On Thu, Jun 15, 2023 at 9:01 AM Anna Schumaker <schumaker.anna@gmail.com> wrote:
>>>>>>
>>>>>> On Thu, Jun 15, 2023 at 4:55 AM Krzysztof Kozlowski
>>>>>> <krzysztof.kozlowski@linaro.org> wrote:
>>>>>>>
>>>>>>> On 15/06/2023 10:52, Krzysztof Kozlowski wrote:
>>>>>>>> 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).
>>>>>>>
>>>>>>> As expected this bounced from the mailing lists, but I hope you got it.
>>>>>>> If not, let me know.
>>>>>>
>>>>>> I did still receive it. Thanks!
>>>>>
>>>>> Can you swap out yesterday's patch with this patch? I've adjusted what
>>>>> gets printed out, and added printk()s to xdr_copy_to_scratch(). I'm
>>>>> starting to think that the xdr scratch buffer is fine, and that it's
>>>>> the other pointer passed to memcpy() in that function that's the
>>>>> problem, and the output from this patch will confirm for me.
>>>>
>>>> Oh, and can you add this one on top of the v2 patch as well?
>>>
>>> Sorry about the noise today. Can you use this patch instead of the two
>>> I attached earlier? I cleaned up the output and cut down on extra
>>> output..
>>>
>>
>> Here you have - attached.
>
> This is good, thanks! I was finally able to figure out how to hit the
> bug using a 32bit x86 VM, so hopefully the next thing you hear from me
> is a patch fixing the bug!
QEMU also has 32-bit ARM and x86...
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-21 13:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 15:44 Regression: NULL pointer dereference after NFS_V4_2_READ_PLUS (commit 7fd461c47) Krzysztof Kozlowski
2023-01-08 8:52 ` Linux kernel regression tracking (#adding)
2023-02-18 4:42 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-02-18 15:09 ` Krzysztof Kozlowski
2023-02-21 14:24 ` Linux regression tracking (Thorsten Leemhuis)
2023-01-08 13:25 ` Krzysztof Kozlowski
2023-01-08 17:09 ` Trond Myklebust
2023-01-09 8:14 ` Krzysztof Kozlowski
2023-01-09 8:42 ` Krzysztof Kozlowski
2023-01-09 14:44 ` Trond Myklebust
2023-01-09 15:07 ` Chuck Lever III
2023-01-09 15:26 ` Anna Schumaker
2023-01-09 18:25 ` Chuck Lever III
2023-01-09 15:38 ` Trond Myklebust
2023-01-09 17:11 ` Chuck Lever III
2023-01-09 17:20 ` Chuck Lever III
2023-01-22 22:25 ` Anna Schumaker
2023-01-23 7:58 ` Krzysztof Kozlowski
2023-02-09 18:22 ` Anna Schumaker
2023-02-10 8:41 ` Krzysztof Kozlowski
2023-02-10 8:53 ` Krzysztof Kozlowski
2023-02-10 20:55 ` Anna Schumaker
2023-02-11 11:23 ` Krzysztof Kozlowski
2023-02-12 14:05 ` Anna Schumaker
2023-02-14 11:02 ` Krzysztof Kozlowski
2023-02-16 17:40 ` Olga Kornievskaia
2023-03-06 17:09 ` Anna Schumaker
2023-04-04 1:01 ` Olga Kornievskaia
2023-04-04 5:29 ` Krzysztof Kozlowski
2023-06-10 10:15 ` Krzysztof Kozlowski
2023-06-14 20:55 ` Anna Schumaker
2023-06-15 8:52 ` Krzysztof Kozlowski
2023-06-15 8:55 ` Krzysztof Kozlowski
2023-06-15 13:01 ` Anna Schumaker
2023-06-15 17:04 ` Anna Schumaker
2023-06-15 17:16 ` Anna Schumaker
2023-06-15 19:38 ` Anna Schumaker
2023-06-17 10:09 ` Krzysztof Kozlowski
2023-06-21 12:49 ` Anna Schumaker
2023-06-21 13:27 ` Krzysztof Kozlowski [this message]
2023-06-23 17:59 ` Anna Schumaker
2023-06-26 10:28 ` Krzysztof Kozlowski
2023-06-27 19:08 ` Anna Schumaker
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=dfcc114f-56f1-e4ab-7b36-f9a4ce3e8c8c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Anna.Schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=schumaker.anna@gmail.com \
--cc=trondmy@hammerspace.com \
/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;
as well as URLs for NNTP newsgroup(s).