All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: David Disseldorp <ddiss@suse.de>
Cc: linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	ronnie sahlberg <ronniesahlberg@gmail.com>,
	Paulo Alcantara <pc@cjr.nz>
Subject: Re: [PATCH] cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL
Date: Thu, 30 Mar 2023 17:42:49 -0500	[thread overview]
Message-ID: <CAH2r5msdSfBMBo=yKSLJqjn4Hyn3boSwQ1RywuWiOYfjSgD2Zw@mail.gmail.com> (raw)
In-Reply-To: <20230330231910.1bed68a1@echidna.fritz.box>

Fixed description (and updated to include Ronnie's RB)

On Thu, Mar 30, 2023 at 4:17 PM David Disseldorp <ddiss@suse.de> wrote:
>
> Hi Steve,
>
> On Wed, 29 Mar 2023 18:20:33 -0500, Steve French wrote:
>
> > merged into cifs-2.6.git for-next and added Paulo's Reviewed-by
>
> Thanks, although I'm only aware of Ronnie's review (in this thread).
>
> > On Wed, Mar 29, 2023 at 3:23 PM David Disseldorp <ddiss@suse.de> wrote:
> >
> > > When compiled with CONFIG_CIFS_DFS_UPCALL disabled, cifs_dfs_d_automount
> > > NULL. cifs.ko logic for mapping CIFS_FATTR_DFS_REFERRAL attributes to
>     ^^
> If you're fixing the reviewed-by, then please also add the missing
> "is" between "cifs_dfs_d_automount NULL".
>
> Cheers, David



-- 
Thanks,

Steve

      reply	other threads:[~2023-03-30 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 20:24 [PATCH] cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL David Disseldorp
2023-03-29 20:29 ` ronnie sahlberg
     [not found] ` <CAH2r5mtEXtRWbtf9OAzwWa2Wm6fUR+fZrU=OmtiP3E0VQpn+2w@mail.gmail.com>
2023-03-29 23:21   ` Fwd: " Steve French
2023-03-30 21:19   ` David Disseldorp
2023-03-30 22:42     ` Steve French [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='CAH2r5msdSfBMBo=yKSLJqjn4Hyn3boSwQ1RywuWiOYfjSgD2Zw@mail.gmail.com' \
    --to=smfrench@gmail.com \
    --cc=ddiss@suse.de \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=pc@cjr.nz \
    --cc=ronniesahlberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.