linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Koch <mail@alexanderkoch.net>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: linux-cifs@vger.kernel.org
Subject: Re: cifs.upcall broken with cifs-utils 6.13
Date: Fri, 06 Aug 2021 09:09:33 +0200	[thread overview]
Message-ID: <2f863f5d2c22907a88a4bfc04ab5f1b4@alexanderkoch.net> (raw)
In-Reply-To: <956dd84c4e27fd02541ca4fabb7b1776@alexanderkoch.net>

Hi Aurélien,

>> It's unfortunately a regression in the CVE fix. We are trying to come 
>> up
>> with a proper fix.

Any news about the proper fix for this regression?

I've seen there is no new release but maybe the is a patch that I could
propose for the maintainer of the 'cifs-utils' package in Arch in order 
to
work around this issue.

As of right now, the only working option is to keep the package 
downgraded
to 6.12.


Best regards,

Alex

  reply	other threads:[~2021-08-06  7:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 16:05 cifs.upcall broken with cifs-utils 6.13 Alexander Koch
2021-04-20 16:41 ` Aurélien Aptel
2021-04-20 17:02   ` Alexander Koch
2021-08-06  7:09     ` Alexander Koch [this message]
2021-08-06  9:02       ` Pavel Shilovsky

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=2f863f5d2c22907a88a4bfc04ab5f1b4@alexanderkoch.net \
    --to=mail@alexanderkoch.net \
    --cc=aaptel@suse.com \
    --cc=linux-cifs@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;
as well as URLs for NNTP newsgroup(s).