From: Oleg Nesterov <oleg@redhat.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
David Howells <dhowells@redhat.com>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/pipe.c: merge if statements with identical conditions
Date: Fri, 7 Mar 2025 23:54:08 +0100 [thread overview]
Message-ID: <20250307225408.GC28762@redhat.com> (raw)
In-Reply-To: <20250307222500.1117662-1-linux@rasmusvillemoes.dk>
On 03/07, Rasmus Villemoes wrote:
>
> As 'head' is not updated after head+1 is assigned to pipe->head, the
> condition being tested here is exactly the same as in the big if
> statement just above. Merge the two bodies.
Yes.
But Mateusz has already sent the same patch, please see
[PATCH 1/3] pipe: drop an always true check in anon_pipe_write()
https://lore.kernel.org/all/20250303230409.452687-2-mjguzik@gmail.com/
Oleg.
> Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> ---
> fs/pipe.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/fs/pipe.c b/fs/pipe.c
> index 097400cce241..27385e3e5417 100644
> --- a/fs/pipe.c
> +++ b/fs/pipe.c
> @@ -547,10 +547,8 @@ pipe_write(struct kiocb *iocb, struct iov_iter *from)
>
> if (!iov_iter_count(from))
> break;
> - }
> -
> - if (!pipe_full(head, pipe->tail, pipe->max_usage))
> continue;
> + }
>
> /* Wait for buffer space to become available. */
> if ((filp->f_flags & O_NONBLOCK) ||
> --
> 2.48.1
>
prev parent reply other threads:[~2025-03-07 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 22:25 [PATCH] fs/pipe.c: merge if statements with identical conditions Rasmus Villemoes
2025-03-07 22:40 ` Mateusz Guzik
2025-03-07 22:51 ` Rasmus Villemoes
2025-03-07 22:54 ` Oleg Nesterov [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=20250307225408.GC28762@redhat.com \
--to=oleg@redhat.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=torvalds@linux-foundation.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