public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Meena Shanmugam <meenashanmugam@google.com>
Cc: stable@vger.kernel.org, trond.myklebust@hammerspace.com
Subject: Re: Request to cherry-pick f00432063db1 to 5.10
Date: Fri, 13 May 2022 10:25:04 +0200	[thread overview]
Message-ID: <Yn4V4HdJFyHARf1b@kroah.com> (raw)
In-Reply-To: <CAMdnWFBCyiU-p1ww5NQnvMxVUnVyCkzoS6D+6Hg=7aJR4Bwn5Q@mail.gmail.com>

On Thu, May 12, 2022 at 10:38:04AM -0700, Meena Shanmugam wrote:
> On Thu, May 12, 2022 at 9:23 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, May 10, 2022 at 07:33:23PM -0700, Meena Shanmugam wrote:
> > > Hi all,
> > >
> > > The commit f00432063db1a0db484e85193eccc6845435b80e upstream (SUNRPC:
> > > Ensure we flush any closed sockets before xs_xprt_free()) fixes
> > > CVE-2022-28893, hence good candidate for stable trees.
> > > The above commit depends on 3be232f(SUNRPC: Prevent immediate
> > > close+reconnect)  and  89f4249(SUNRPC: Don't call connect() more than
> > > once on a TCP socket). Commit 3be232f depends on commit
> > > e26d9972720e(SUNRPC: Clean up scheduling of autoclose).
> > >
> > > Commits e26d9972720e, 3be232f, f00432063db1 apply cleanly on 5.10
> > > kernel. commit 89f4249 didn't apply cleanly. I have patch for 89f4249
> > > below.
> >
> > We also need this for 5.15.y first, before we can apply it to 5.10.y.
> > Can you provide a working backport for that tree as well?
> >
> > And as others pointed out, your patch is totally corrupted and can not
> > be used, please fix your email client.
> >
> > thanks,
> >
> > greg k-h
> 
> For 5.15.y commit f00432063db1a0db484e85193eccc6845435b80e((SUNRPC:
> Ensure we flush any closed sockets before xs_xprt_free())) applies
> cleanly. The depend patch
> 3be232f(SUNRPC: Prevent immediate close+reconnect) also applies
> cleanly. Patch  89f4249
> (SUNRPC: Don't call connect() more than once on a TCP socket) is
> already present in 5.15.34 onwards.
> 
> Sorry about the patch corruption, I will fix it.

Sorry, but this did not work out at all, I get build errors when
attempting it for 5.10.y:

  CC [M]  net/sunrpc/xprtsock.o
net/sunrpc/xprtsock.c: In function ‘xs_tcp_setup_socket’:
net/sunrpc/xprtsock.c:2276:13: error: too few arguments to function ‘test_and_clear_bit’
 2276 |         if (test_and_clear_bit(XPRT_SOCK_CONNECT_SENT),
      |             ^~~~~~~~~~~~~~~~~~
In file included from ./arch/x86/include/asm/bitops.h:391,
                 from ./include/linux/bitops.h:29,
                 from ./include/linux/kernel.h:12,
                 from ./include/asm-generic/bug.h:20,
                 from ./arch/x86/include/asm/bug.h:93,
                 from ./include/linux/bug.h:5,
                 from ./include/linux/mmdebug.h:5,
                 from ./include/linux/gfp.h:5,
                 from ./include/linux/slab.h:15,
                 from net/sunrpc/xprtsock.c:24:
./include/asm-generic/bitops/instrumented-atomic.h:81:20: note: declared here
   81 | static inline bool test_and_clear_bit(long nr, volatile unsigned long *addr)
      |                    ^~~~~~~~~~~~~~~~~~
net/sunrpc/xprtsock.c:2276:55: warning: left-hand operand of comma expression has no effect [-Wunused-value]
 2276 |         if (test_and_clear_bit(XPRT_SOCK_CONNECT_SENT),
      |                                                       ^
net/sunrpc/xprtsock.c:2312:17: warning: this statement may fall through [-Wimplicit-fallthrough=]
 2312 |                 set_bit(XPRT_SOCK_CONNECT_SENT, &transport->sock_state);
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
net/sunrpc/xprtsock.c:2313:9: note: here
 2313 |         case -EALREADY:
      |         ^~~~
make[2]: *** [scripts/Makefile.build:280: net/sunrpc/xprtsock.o] Error 1
make[1]: *** [scripts/Makefile.build:497: net/sunrpc] Error 2


And I am not quite sure what order you want me to apply things for 5.15.y.

So please, send me a properly backported series of patches for this for 5.15.y
and 5.10.y and I will be glad to pick them up.  Right now I'm just confused as
this was obviously not tested at all :(

thanks,

greg k-h

  reply	other threads:[~2022-05-13  8:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  2:33 Request to cherry-pick f00432063db1 to 5.10 Meena Shanmugam
2022-05-12  6:48 ` Bagas Sanjaya
2022-05-12 16:23 ` Greg KH
2022-05-12 17:38   ` Meena Shanmugam
2022-05-13  8:25     ` Greg KH [this message]
2022-05-13 17:59       ` [PATCH] SUNRPC: Don't call connect() more than once on a TCP socket Meena Shanmugam
2022-05-14  4:56         ` Greg KH
2022-05-14  5:34           ` [PATCH 0/4] Request to cherry-pick f00432063db1 to 5.10 Meena Shanmugam
2022-05-14  5:34             ` [PATCH 1/4] SUNRPC: Clean up scheduling of autoclose Meena Shanmugam
2022-05-14  5:34             ` [PATCH 2/4] SUNRPC: Prevent immediate close+reconnect Meena Shanmugam
2022-05-14  5:34             ` [PATCH 3/4] SUNRPC: Don't call connect() more than once on a TCP socket Meena Shanmugam
2022-05-16 21:34               ` Greg KH
2022-05-17  3:56                 ` Meena Shanmugam
2022-05-14  5:34             ` [PATCH 4/4] SUNRPC: Ensure we flush any closed sockets before xs_xprt_free() Meena Shanmugam
2022-05-14  8:47             ` [PATCH 0/4] Request to cherry-pick f00432063db1 to 5.10 Bagas Sanjaya
2022-05-16 12:43               ` Greg KH
2022-05-13 18:10       ` Meena Shanmugam
2022-05-13 18:14       ` Meena Shanmugam
2022-05-16 12:42         ` Greg KH

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=Yn4V4HdJFyHARf1b@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=meenashanmugam@google.com \
    --cc=stable@vger.kernel.org \
    --cc=trond.myklebust@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