From: David Miller <davem@davemloft.net>
To: jarkao2@gmail.com
Cc: xemul@openvz.org, netdev@vger.kernel.org
Subject: Re: [PATCH (regression)] Fragments: fix race between inet_frag_find and inet_frag_secret_rebuild
Date: Fri, 27 Jun 2008 20:06:29 -0700 (PDT) [thread overview]
Message-ID: <20080627.200629.124429489.davem@davemloft.net> (raw)
In-Reply-To: <20080624180714.GA3125@ami.dom.local>
From: Jarek Poplawski <jarkao2@gmail.com>
Date: Tue, 24 Jun 2008 20:07:14 +0200
> Pavel Emelyanov wrote, On 06/24/2008 12:43 PM:
>
> > The problem is that while we work w/o the inet_frags.lock even
> > read-locked the secret rebuild timer may occur (on another CPU,
> - since BHs are still disables in the inet_frag_find) and change
>
> + since BHs are still disabled in the inet_frag_find) and change
I've applied Pavel's fix with this comment typo cure.
Thanks.
prev parent reply other threads:[~2008-06-28 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 10:43 [PATCH (regression)] Fragments: fix race between inet_frag_find and inet_frag_secret_rebuild Pavel Emelyanov
2008-06-24 18:07 ` Jarek Poplawski
2008-06-25 6:42 ` Pavel Emelyanov
2008-06-25 7:09 ` David Miller
2008-06-25 9:37 ` Jarek Poplawski
2008-06-28 3:06 ` 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=20080627.200629.124429489.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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 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.