[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wg8e77mmVWZrSjhDe3+3MfF_h1op7VjTJv570zrE2s9Jw@mail.gmail.com>
Date: Thu, 6 Mar 2025 07:59:03 -1000
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Rasmus Villemoes <ravi@...vas.dk>
Cc: Oleg Nesterov <oleg@...hat.com>, Mateusz Guzik <mjguzik@...il.com>,
K Prateek Nayak <kprateek.nayak@....com>, "Sapkal, Swapnil" <swapnil.sapkal@....com>,
Manfred Spraul <manfred@...orfullife.com>, Christian Brauner <brauner@...nel.org>,
David Howells <dhowells@...hat.com>, WangYuli <wangyuli@...ontech.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
"Shenoy, Gautham Ranjal" <gautham.shenoy@....com>, Neeraj.Upadhyay@....com, Ananth.narayan@....com
Subject: Re: [PATCH] pipe_read: don't wake up the writer if the pipe is still full
On Wed, 5 Mar 2025 at 22:35, Rasmus Villemoes <ravi@...vas.dk> wrote:
>
> On Wed, Mar 05 2025, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> >
> > and there might be other cases where the pipe_index_t size might matter.
>
> Yeah, for example
>
> unsigned int count, head, tail, mask;
>
> case FIONREAD:
Thanks. I've hopefully fixed this (and the FUSE issue you also
reported), and those should work correctly no on 32-bit. Knock wood.
Mind taking a look and double-checking the fixes?
Linus
Powered by blists - more mailing lists