From: David Miller <davem@davemloft.net>
To: herton@redhat.com
Cc: chien.yen@oracle.com, rds-devel@oss.oracle.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
rmanes@redhat.com, dledford@redhat.com
Subject: Re: Small fixes/changes for RDS
Date: Fri, 03 Oct 2014 12:52:59 -0700 (PDT) [thread overview]
Message-ID: <20141003.125259.1940750405354043575.davem@davemloft.net> (raw)
In-Reply-To: <1412200194-28902-1-git-send-email-herton@redhat.com>
From: "Herton R. Krzesinski" <herton@redhat.com>
Date: Wed, 1 Oct 2014 18:49:51 -0300
> I got a report of one issue within RDS (after investigation it was a double
> free), and I'm sending the fix (patch 3/3) which reporter said it works (no more
> WARNING triggered on a specially instrumented kernel). The report/test was done
> on a very old kernel (RHEL 5, 2.6.18 based with backports), but the problem the
> patch handles still exists and should not change. Besides that, while
> reviewing some of the code but being unable to reproduce with rds_tcp, I
> noticed two small improvements/fixes which are in patches 1 and 2.
Series applied, thanks.
prev parent reply other threads:[~2014-10-03 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 21:49 Small fixes/changes for RDS Herton R. Krzesinski
2014-10-01 21:49 ` [PATCH 1/3] net/rds: call rds_conn_drop instead of open code it at rds_connect_complete Herton R. Krzesinski
2014-10-01 21:49 ` [PATCH 2/3] net/rds: do proper house keeping if connection fails in rds_tcp_conn_connect Herton R. Krzesinski
2014-10-01 21:49 ` [PATCH 3/3] net/rds: fix possible double free on sock tear down Herton R. Krzesinski
2014-10-03 19:52 ` David Miller [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=20141003.125259.1940750405354043575.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chien.yen@oracle.com \
--cc=dledford@redhat.com \
--cc=herton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=rmanes@redhat.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;
as well as URLs for NNTP newsgroup(s).