From: David Howells <dhowells@redhat.com>
To: Damian Tometzki <damian@riscv-rocks.de>
Cc: dhowells@redhat.com, Eric Biggers <ebiggers@kernel.org>,
Steve French <smfrench@gmail.com>, John Sanpe <sanpeqf@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Paulo Alcantara <pc@manguebit.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: smb cifs: Linux 6.7 pre rc-1 kernel dump in smb2_get_aead_req
Date: Mon, 06 Nov 2023 10:01:17 +0000 [thread overview]
Message-ID: <2545100.1699264877@warthog.procyon.org.uk> (raw)
In-Reply-To: <ZUiXkPPP1TuOgmmf@fedora.fritz.box>
Damian Tometzki <damian@riscv-rocks.de> wrote:
> the revert of f1b4cb650b9a0eeba206d8f069fcdc532bfbcd74 solved the issue of
> the kernel dump.
That almost certainly did not fix the problem - merely hid the wanring.
Prior to f1b4cb650b9a0eeba206d8f069fcdc532bfbcd74, ->user_backed is explicitly
set if the iov_iter is initialised to a user-backed type, now it's just
inferred from the type being 0 or 1 - so I think that the iov_iter has not
been initialised somewhere.
Somewhere being from SMB2_tcon() and cifs_send_recv() on down.
David
next prev parent reply other threads:[~2023-11-06 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 18:39 [PATCH] fs/smb: using crypto lib instead cifs_arc4 John Sanpe
2023-10-22 19:38 ` Steve French
2023-10-22 19:40 ` Steve French
2023-10-22 19:42 ` ronnie sahlberg
2023-11-05 19:33 ` Eric Biggers
2023-11-05 17:28 ` smb cifs: Linux 6.7 pre rc-1 kernel dump in smb2_get_aead_req Damian Tometzki
[not found] ` <CAH2r5msde65PMtn-96VZDAQkT_rq+e-2G4O+zbPUR8zSWGxMsg@mail.gmail.com>
2023-11-05 19:36 ` Eric Biggers
2023-11-05 19:40 ` Damian Tometzki
2023-11-05 20:15 ` Eric Biggers
2023-11-06 7:36 ` Damian Tometzki
2023-11-06 10:01 ` David Howells [this message]
2023-11-06 14:40 ` [PATCH] cifs: Fix encryption of cleared, but unset rq_iter data buffers David Howells
2023-11-06 15:41 ` Paulo Alcantara
2023-11-07 5:18 ` Damian Tometzki
2023-11-07 18:51 ` Steve French
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=2545100.1699264877@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=damian@riscv-rocks.de \
--cc=ebiggers@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=sanpeqf@gmail.com \
--cc=smfrench@gmail.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