linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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 10:08:59 +0100	[thread overview]
Message-ID: <CAJfpegtOiiBqhFeFBbuaY=TaS2xMafLOES=LHdNx8BhwUz7aCg@mail.gmail.com> (raw)
In-Reply-To: <2701318.1706863882@warthog.procyon.org.uk>

On Fri, 2 Feb 2024 at 09:51, David Howells <dhowells@redhat.com> wrote:
>
> Hi,
>
> We have various locks, mutexes, etc., that are taken on entry to filesystem
> code, for example, and a bunch of them are taken interruptibly or killably (or
> ought to be) - but filesystem code might be called into from uninterruptible
> code, such as the memory allocator, fscache, etc..

Are you suggesting to make lots more filesystem/vfs/mm sleeps
killable?  That would present problems with being called from certain
contexts.

Or are there bugs already?

Thanks,
Miklos


  reply	other threads:[~2024-02-02  9:09 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 [this message]
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
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='CAJfpegtOiiBqhFeFBbuaY=TaS2xMafLOES=LHdNx8BhwUz7aCg@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