From: "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro>
To: Thomas Graf <tgraf@suug.ch>
Cc: netdev@oss.sgi.com, davem@davemloft.net
Subject: Re: [PATCH] [SCHED] Fix unlock spinlock in error path
Date: Mon, 16 May 2005 22:25:23 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.62.0505162224420.20204@webhosting.rdsbv.ro> (raw)
In-Reply-To: <20050516134900.GC13748@postel.suug.ch>
On Mon, 16 May 2005, Thomas Graf wrote:
> * Catalin(ux aka Dino) BOIE <Pine.LNX.4.62.0505161555080.13294@webhosting.rdsbv.ro> 2005-05-16 16:01
>> In act_api.c::tcf_action_copy_stats, in error path (get_stats
>> returns < 0), the spinlock taken in gnet_stats_start_copy_compat
>> or gnet_stats_start_copy is not unlocked.
>
> This is on purpose, get_stats() is nothing more than a placeholder
> at the moment for something that should really be called dump_stats()
> and have struct gnet_dump as one of its arguments. The unlocking
> must be done in the internal error handling and if we ever have an
> operation that could fail between _start() and _stop() for
> another reason we'll need a gnet_stats_abort() (skb_trim()'ing
> properly) to avoid double unlocking. But since there is no
> user of this API yet it doesn't make sense to bloat the code.
Thanks Thomas for the explication!
Sorry for the noise.
---
Catalin(ux aka Dino) BOIE
catab at deuroconsult.ro
http://kernel.umbrella.ro/
next prev parent reply other threads:[~2005-05-16 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 13:01 [PATCH] [SCHED] Fix unlock spinlock in error path Catalin(ux aka Dino) BOIE
2005-05-16 13:49 ` Thomas Graf
2005-05-16 19:25 ` Catalin(ux aka Dino) BOIE [this message]
2005-05-16 20:12 ` Thomas Graf
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=Pine.LNX.4.62.0505162224420.20204@webhosting.rdsbv.ro \
--to=util@deuroconsult.ro \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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).