From: Albert Strasheim <fullung@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 32312] New: Race condition in umount
Date: Tue, 26 Apr 2011 14:37:56 +0200 [thread overview]
Message-ID: <BANLkTi==e7r+K6THP1X8=ReL_TCcVh+_Sg@mail.gmail.com> (raw)
In-Reply-To: <20110331113655.faea3975.akpm@linux-foundation.org>
Hello all
I was wondering if anyone has had a chance to review this issue?
Regards
Albert
On Thu, Mar 31, 2011 at 8:36 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
>
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Thu, 31 Mar 2011 04:54:52 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=32312
>>
>> Summary: Race condition in umount
>> Product: File System
>> Version: 2.5
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: VFS
>> AssignedTo: fs_vfs@kernel-bugs.osdl.org
>> ReportedBy: fullung@gmail.com
>> Regression: No
>>
>>
>> The Red Hat folks suggested reporting this bug here:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=683836
>>
>> In summary, doing many umounts in parallel causes some umounts to fail and if
>> the mount/parallel umount cycle is repeated a few times, bad stuff happens
>> inside the kernel.
>>
>> Reproduced with 2.6.38.*.
>>
>
>
--
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
next prev parent reply other threads:[~2011-04-26 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-32312-10286@https.bugzilla.kernel.org/>
2011-03-31 18:36 ` [Bugme-new] [Bug 32312] New: Race condition in umount Andrew Morton
2011-04-26 12:37 ` Albert Strasheim [this message]
2011-04-27 11:52 ` Jan Kara
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='BANLkTi==e7r+K6THP1X8=ReL_TCcVh+_Sg@mail.gmail.com' \
--to=fullung@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--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).