From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, rds-devel@oss.oracle.com,
santosh.shilimkar@oracle.com
Subject: Re: [PATCH net-next] rds: clean up loopback rds_connections on netns deletion
Date: Tue, 26 Jun 2018 10:53:23 -0400 [thread overview]
Message-ID: <20180626145323.GH20575@oracle.com> (raw)
In-Reply-To: <20180626.232956.1181108479532700313.davem@davemloft.net>
On (06/26/18 23:29), David Miller wrote:
> >>
> >> Since this probably fixes syzbot reports, this can be targetted
> >> at 'net' instead?
> >
> > that thought occurred to me but I wanted to be conservative and have
> > it in net-next first, have the syzkaller-bugs team confirm the
> > the fixes and then backport to earlier kernels (if needed)..
>
> I think there is a way to ask syzbot to test a patch in an
> email.
and just to add, the fix itself is logically correct, so belongs in
net-next. What I dont have (and therefore did not target net) is
official confirmation that the syzbot failures are root-caused to the
absence of this patch (since there is no reproducer for many of these,
and no crash dumps available from syzbot).
--Sowmini
next prev parent reply other threads:[~2018-06-26 14:53 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
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 [this message]
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=20180626145323.GH20575@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 \
/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.