All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: davem@davemloft.net, rds-devel@oss.oracle.com,
	santosh.shilimkar@oracle.com, netdev@vger.kernel.org
Cc: syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH net-next] rds: clean up loopback rds_connections on netns deletion
Date: Mon, 25 Jun 2018 10:49:07 -0400	[thread overview]
Message-ID: <20180625144907.GE14823@oracle.com> (raw)
In-Reply-To: <1529934085-181126-1-git-send-email-sowmini.varadhan@oracle.com>

On (06/25/18 06:41), Sowmini Varadhan wrote:
  :
> Add the changes aligned with the changes from
> commit ebeeb1ad9b8a ("rds: tcp: use rds_destroy_pending() to synchronize
> netns/module teardown and rds connection/workq management") for
> rds_loop_transport

FWIW, I am optimistic that this will take care of a number
of the use-after-free panics reported by syzbot (I have not
marked the patch with the recommended syzkaller Reported-by 
tags because I was not able to reproduce each original issue, 
but inspection of the traces suggests this missing patch may 
be behind the races that cause the reports).

--Sowmini

  reply	other threads:[~2018-06-25 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 13:41 [PATCH net-next] rds: clean up loopback rds_connections on netns deletion Sowmini Varadhan
2018-06-25 14:49 ` Sowmini Varadhan [this message]
2018-06-26 13:23 ` David Miller
2018-06-26 13:40   ` Sowmini Varadhan
2018-06-26 14:29     ` David Miller
2018-06-26 14:44       ` Sowmini Varadhan
2018-06-26 14:48         ` Dmitry Vyukov
2018-06-26 15:04           ` Sowmini Varadhan
2018-06-26 15:21             ` Dmitry Vyukov
2018-06-26 14:53       ` Sowmini Varadhan
2018-06-26 16:28         ` [rds-devel] " Sowmini Varadhan
2018-06-27  1:12           ` David Miller

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=20180625144907.GE14823@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=rds-devel@oss.oracle.com \
    --cc=santosh.shilimkar@oracle.com \
    --cc=syzkaller-bugs@googlegroups.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.