From: Miklos Szeredi <miklos@szeredi.hu>
To: David Howells <dhowells@redhat.com>
Cc: lsf-pc@lists.linux-foundation.org,
Matthew Wilcox <willy@infradead.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
dwmw2@infradead.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [LSF/MM/BPF TOPIC] Replacing TASK_(UN)INTERRUPTIBLE with regions of uninterruptibility
Date: Fri, 2 Feb 2024 13:06:30 +0100 [thread overview]
Message-ID: <CAJfpegu-s=K0W6M7BqzrkaNsnXiJ25LcGLLMS-E-roKCD0dVZw@mail.gmail.com> (raw)
In-Reply-To: <2751706.1706872935@warthog.procyon.org.uk>
On Fri, 2 Feb 2024 at 12:22, David Howells <dhowells@redhat.com> wrote:
>
> Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> > Just making inode_lock() interruptible would break everything.
>
> Why? Obviously, you'd need to check the result of the inode_lock(), which I
> didn't put in my very rough example code, but why would taking the lock at the
> front of a vfs op like mkdir be a problem?
No problem in theory. It just looks like a tedious job doing all that.
But please go for it, it's a worthy goal in my opinion.
Thanks,
Miklos
next prev parent reply other threads:[~2024-02-02 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 8:51 David Howells
2024-02-02 9:08 ` Miklos Szeredi
2024-02-02 9:43 ` Kent Overstreet
2024-02-02 10:30 ` David Howells
2024-02-02 10:46 ` Miklos Szeredi
2024-02-02 11:22 ` David Howells
2024-02-02 12:06 ` Miklos Szeredi [this message]
2024-02-02 12:44 ` Kent Overstreet
2024-02-02 16:23 ` Al Viro
2024-02-03 17:27 ` Kent Overstreet
2024-02-02 13:28 ` Matthew Wilcox
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='CAJfpegu-s=K0W6M7BqzrkaNsnXiJ25LcGLLMS-E-roKCD0dVZw@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=willy@infradead.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