From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sandeep Patil <sspatil@android.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
stable <stable@vger.kernel.org>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: [PATCH 1/1] fs: pipe: wakeup readers everytime new data written is to pipe
Date: Sat, 31 Jul 2021 07:32:41 +0200 [thread overview]
Message-ID: <YQTgeSUwqC5/8i88@kroah.com> (raw)
In-Reply-To: <CAHk-=wgw7hh5+E6P2YYpHH51YNnkpro5tzSdXEmL9Xpk5Bh9Dg@mail.gmail.com>
On Fri, Jul 30, 2021 at 03:55:17PM -0700, Linus Torvalds wrote:
> On Fri, Jul 30, 2021 at 3:53 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > I've pushed it out as commit 3a34b13a88ca ("pipe: make pipe writes
> > always wake up readers"). Holler if you notice anything odd remaining.
>
> .. and as I wrote that, I realized that I had forgotten to mark it for
> stable even though that was the intent.
>
> So stable team, please consider this the "that commit should probably
> be added to your queue" notification,
Will do so, thanks!
greg k-h
next prev parent reply other threads:[~2021-07-31 5:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 22:26 [PATCH 0/1] Revert change in pipe reader wakeup behavior Sandeep Patil
2021-07-29 22:26 ` [PATCH 1/1] fs: pipe: wakeup readers everytime new data written is to pipe Sandeep Patil
2021-07-29 23:01 ` Linus Torvalds
2021-07-30 19:11 ` Sandeep Patil
2021-07-30 19:23 ` Linus Torvalds
2021-07-30 19:47 ` Sandeep Patil
2021-07-30 22:06 ` Linus Torvalds
2021-07-30 22:53 ` Linus Torvalds
2021-07-30 22:55 ` Linus Torvalds
2021-07-31 5:32 ` Greg Kroah-Hartman [this message]
2021-08-02 18:59 ` Sandeep Patil
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=YQTgeSUwqC5/8i88@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dhowells@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sspatil@android.com \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).