From: Greg KH <gregkh@linuxfoundation.org>
To: Paulo Alcantara <pc@manguebit.com>
Cc: Eduard Bachmakov <e.bachmakov@gmail.com>,
stable@vger.kernel.org, linux-cifs@vger.kernel.org,
Steve French <smfrench@gmail.com>
Subject: Re: Unexpected additional umh-based DNS lookup in 6.6.0
Date: Fri, 24 Nov 2023 11:53:30 +0000 [thread overview]
Message-ID: <2023112402-handoff-spore-f997@gregkh> (raw)
In-Reply-To: <cbe899ddc4bfc2835fc015eb0badfc10@manguebit.com>
On Thu, Nov 23, 2023 at 10:56:53PM -0300, Paulo Alcantara wrote:
> Stable team,
>
> Eduard Bachmakov <e.bachmakov@gmail.com> writes:
>
> > I noticed this got pulled into 6.7. Given this is a user-facing
> > regression, can this be proposed for the next 6.6 point release?
> > Sorry, if this is already the case and I missed it.
>
> Could you please backport
>
> 5e2fd17f434d ("smb: client: fix mount when dns_resolver key is not available")
>
> to v6.6.y?
Will do so now, thanks, I'm way behind in catching up with stable
patches due to the merge window and then Plumbers and now some
additional travel, sorry about that.
greg k-h
prev parent reply other threads:[~2023-11-24 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADCRUiNvZuiUZ0VGZZO9HRyPyw6x92kiA7o7Q4tsX5FkZqUkKg@mail.gmail.com>
[not found] ` <d2c0c53db617b6d2f9b71e734b165b4b.pc@manguebit.com>
[not found] ` <CADCRUiNSk7b7jVQrYoD153UmaBdFzpcA1q3DvfwJcNC6Q=gy0w@mail.gmail.com>
[not found] ` <482ee449a063acf441b943346b85e2d0.pc@manguebit.com>
[not found] ` <CADCRUiN=tz85t5T00H1RbmwSj_35j9vbe92TaKUrESUyNSK9QA@mail.gmail.com>
2023-11-24 1:56 ` Unexpected additional umh-based DNS lookup in 6.6.0 Paulo Alcantara
2023-11-24 11:53 ` Greg KH [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=2023112402-handoff-spore-f997@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=e.bachmakov@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=smfrench@gmail.com \
--cc=stable@vger.kernel.org \
/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