From: Eric Sandeen <sandeen@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: viro@zeniv.linux.org.uk
Subject: Re: [PATCH 0/2 V2] avoid softlockups in various s_inodes iterators
Date: Wed, 13 Nov 2019 16:07:43 -0600 [thread overview]
Message-ID: <a7f6218c-ba80-14bd-b5f8-94bc7d4070b7@redhat.com> (raw)
In-Reply-To: <1573159954-27846-1-git-send-email-sandeen@redhat.com>
On 11/7/19 2:52 PM, Eric Sandeen wrote:
> 2 patches to make sure we either schedule in an s_inodes walking
> loop, or do our best to limit the size of the walk, to avoid soft
> lockups.
>
> V2 to fix inexplicable patch mangling
>
> Thanks,
> -Eric
>
Al, ping on this?
Thanks,
-Eric
prev parent reply other threads:[~2019-11-13 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 20:52 [PATCH 0/2 V2] avoid softlockups in various s_inodes iterators Eric Sandeen
2019-11-07 20:52 ` [PATCH 1/2] fs: avoid softlockups in " Eric Sandeen
2019-11-07 20:52 ` [PATCH 2/2] fs: call fsnotify_sb_delete after evict_inodes Eric Sandeen
2019-11-13 23:26 ` Al Viro
2019-11-15 13:47 ` [PATCH 2/2 V2] " Eric Sandeen
2019-11-13 22:07 ` Eric Sandeen [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=a7f6218c-ba80-14bd-b5f8-94bc7d4070b7@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).