From: "David S. Miller" <davem@davemloft.net>
To: kaber@trash.net
Cc: dev@openvz.org, torvalds@osdl.org, akpm@osdl.org,
linux-kernel@vger.kernel.org, dim@sw.ru, st@sw.ru,
netdev@vger.kernel.org
Subject: Re: [PATCH] netlink oops fix due to incorrect error code
Date: Mon, 09 Jan 2006 15:54:53 -0800 (PST) [thread overview]
Message-ID: <20060109.155453.02785248.davem@davemloft.net> (raw)
In-Reply-To: <43C2F6DC.7040602@trash.net>
From: Patrick McHardy <kaber@trash.net>
Date: Tue, 10 Jan 2006 00:50:52 +0100
> Kirill Korotaev wrote:
> > Fixed oops after failed netlink socket creation.
> > Wrong parathenses in if() statement caused err to be 1,
> > instead of negative value.
> > Trivial fix, not trivial to find though.
> >
> > Signed-Off-By: Dmitry Mishin <dim@sw.ru>
> > Signed-Off-By: Kirill Korotaev <dev@openvz.org>
>
> Good catch. Dave, please apply.
Already in Linus's tree, he applied it directly :-)
prev parent reply other threads:[~2006-01-09 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43C27662.2030400@openvz.org>
2006-01-09 23:50 ` [PATCH] netlink oops fix due to incorrect error code Patrick McHardy
2006-01-09 23:54 ` David S. 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=20060109.155453.02785248.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=dev@openvz.org \
--cc=dim@sw.ru \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=st@sw.ru \
--cc=torvalds@osdl.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).