From: Matthew Wilcox <matthew@wil.cx>
To: ?????? shin hong <hongshin@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: a suspected race at __posix_lock_file()
Date: Sun, 26 Jul 2009 16:20:02 -0600 [thread overview]
Message-ID: <20090726222002.GB3711@parisc-linux.org> (raw)
In-Reply-To: <2014bcab0907232256y18f98816r15464c024a934ae7@mail.gmail.com>
On Fri, Jul 24, 2009 at 02:56:24PM +0900, ?????? shin hong wrote:
> Hi. I found a suspected race condition bug at fs/locks/__posix_lock_file()
> in recent Linux kernel.
>
> This bug is similar to the one reported in ChangeLog 2.6.24 ( commit
> 85c59580b30c82aa771aa33b37217a6b6851bc14 ).
>
> Big Kernel Lock(BKL) might be released and re-taken
> at the call site of locks_delete_lock()
> since Releasing-On-Block semantics of BKL.
> Locks_delete_lock() may be blocked by kmem_cache_alloc() invocation.
Could you explain to me how locks_delete_lock() calls kmem_cache_alloc()?
> Please examine the possbility of race condition of this code
> and let me know your opinion.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
prev parent reply other threads:[~2009-07-26 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 5:56 a suspected race at __posix_lock_file() 홍신 shin hong
2009-07-26 22:20 ` Matthew Wilcox [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=20090726222002.GB3711@parisc-linux.org \
--to=matthew@wil.cx \
--cc=hongshin@gmail.com \
--cc=linux-fsdevel@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).