From: Andrew Morton <akpm@digeo.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] umount versus iprune
Date: Thu, 20 Feb 2003 10:40:17 -0800 [thread overview]
Message-ID: <20030220104017.7f1981be.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302201337110.1623-100000@localhost.localdomain>
Hugh Dickins <hugh@veritas.com> wrote:
>
> When prune_icache coincides with unmounting, invalidate_inodes notices
> the inode it's working on as busy but doesn't wait: Self-destruct in 5
> seconds message, and later iput oopses on freed super_block.
>
> Neither end is a fast path, so patch below just adds iprune_sem for
> exclusion: if you've got a neater solution, great - I shied away from
> games with i_state, and extending use of shrinker_sem felt like abuse.
>
Sounds reasonable. The semaphore will block kswapd, but the reason kswapd
is being blocked is so that someone else can free tons of memory, so shrug.
Is 2.4 affected?
next prev parent reply other threads:[~2003-02-20 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 13:39 [PATCH] umount versus iprune Hugh Dickins
2003-02-20 18:40 ` Andrew Morton [this message]
2003-02-20 19:54 ` Hugh Dickins
2003-02-20 20:16 ` Hugh Dickins
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=20030220104017.7f1981be.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@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