From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: ja@ssi.bg, netdev@vger.kernel.org, horms@verge.net.au,
bugme-daemon@bugzilla.kernel.org, l0op8ack@hotmail.com
Subject: Re: [Bugme-new] [Bug 10556] New: IPVS sync_backup oops
Date: Tue, 06 May 2008 13:31:53 -0700 (PDT) [thread overview]
Message-ID: <20080506.133153.68569175.davem@davemloft.net> (raw)
In-Reply-To: <20080506131054.fb6196cf.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Tue, 6 May 2008 13:10:54 -0700
> On Sun, 27 Apr 2008 16:40:16 -0700 (PDT)
> David Miller <davem@davemloft.net> wrote:
>
> > From: Julian Anastasov <ja@ssi.bg>
> > Date: Sat, 26 Apr 2008 20:48:46 +0300 (EEST)
> >
> > > Result from ip_vs_proto_get() should be checked because
> > > protocol value can be invalid or unsupported in backup. Also, add
> > > checks to validate message limits and connection state.
> > >
> > > Signed-off-by: Julian Anastasov <ja@ssi.bg>
> >
> > This patch looks great, and fixes real bugs regardless of the
> > effect upon the bug report in question.
> >
> > I would really like to see this fix tested, because if it fixes
> > the specific bug, all the better, and we should indicate this in
> > the changelog message.
>
> The reporter (L0op8ack <l0op8ack@hotmail.com>) has used the bugzilla web
> interface to confirm that this patch fixes 2.6.24.4.
Great, thanks for the update.
next prev parent reply other threads:[~2008-05-06 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10556-10286@http.bugzilla.kernel.org/>
2008-04-26 11:04 ` [Bugme-new] [Bug 10556] New: IPVS sync_backup oops Andrew Morton
2008-04-26 16:31 ` Evgeniy Polyakov
2008-04-26 17:48 ` Julian Anastasov
2008-04-27 15:33 ` Julian Anastasov
2008-04-27 23:40 ` David Miller
2008-05-06 20:10 ` Andrew Morton
2008-05-06 20:31 ` David Miller [this message]
2008-04-27 8:22 ` Julian Anastasov
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=20080506.133153.68569175.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=l0op8ack@hotmail.com \
--cc=netdev@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).