All of lore.kernel.org
 help / color / mirror / Atom feed
From: Todd Kjos <tkjos@google.com>
To: kbuild-all@lists.01.org
Subject: Re: Fwd: [PATCH] objtool, perf: fix stream_open.cocci warnings
Date: Mon, 13 Jan 2020 10:32:53 -0800	[thread overview]
Message-ID: <CAHRSSExvnq6M68b=0JiV-aYAPwiwDaYUg=+pqarqep5RxXnhSQ@mail.gmail.com> (raw)
In-Reply-To: <20200113182145.GA411698@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]

> tree:   https://android.googlesource.com/kernel/common android-4.9-o-mr1

Looks like the comment was related to an issue found on the
android-4.9-o-mr1 branch which doesn't get LTS merges and is really
just a patch repository for patches cited in the Android Security
Bulletin. We don't do general bug-fixes or take LTS merges on that
branch.

On Mon, Jan 13, 2020 at 10:21 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> On Mon, Jan 13, 2020 at 06:04:44PM +0000, Kirill Smelkov wrote:
> > Android people,
> >
> > Please see inside if Android 4.9-o wants to pick up stream_open
> > related deadlock fixes. FUSE part of it is already applied to upstream
> > stable/linux-4.9.y as 9c829b6e3fe2 and cfd8d2e79524, but the Android
> > tree does not have any of the fixes at all.
>
> I do not understand, the commit 10dce8af3422 ("fs: stream_open - opener
> for stream-like files so that read and write can run simultaneously
> without deadlock") is commit 9c829b6e3fe2 in the linux stable 4.9 branch
> and commit bbd84f33652f ("fuse: Add FOPEN_STREAM to use stream_open()")
> is commit cfd8d2e79524 in the linux stable 4.9 branch, right?
>
> If so, that commit is in the 4.9.181 release, which _is_ included in all
> of the android common branches already, as all of the LTS/stable kernel
> releases are merged into the android common trees.
>
> Right now the tip-of-tree of the android-4.9-o branch is 2641bba251cd
> ("Merge 4.9.209 into android-4.9-o") so of course 4.9.181 is also in
> there :)
>
> So I really do not understand what you are asking about here.  Is there
> a specific patch that did not get into the stable releases that you feel
> should go only into the android tree?  If so, what is that upstream
> commit and why wouldn't it go into the stable releases?
>
> confused,
>
> greg k-h
>
> --
> You received this message because you are subscribed to the Google Groups "cros-kernel-buildreports" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cros-kernel-buildreports+unsubscribe(a)googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/cros-kernel-buildreports/20200113182145.GA411698%40kroah.com.

  reply	other threads:[~2020-01-13 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.21.2001131717230.4078@hadrien>
2020-01-13 18:04 ` Fwd: [PATCH] objtool, perf: fix stream_open.cocci warnings Kirill Smelkov
2020-01-13 18:21   ` Greg Kroah-Hartman
2020-01-13 18:32     ` Todd Kjos [this message]
2020-01-13 18:52       ` Kirill Smelkov
2020-01-13 18:56         ` Todd Kjos
2020-01-13 23:08           ` Li, Philip
2020-01-13 23:15             ` Guenter Roeck
2020-01-13 23:18               ` Li, Philip
2020-01-13 23:27                 ` Guenter Roeck
2020-01-13 21:48         ` Julia Lawall

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='CAHRSSExvnq6M68b=0JiV-aYAPwiwDaYUg=+pqarqep5RxXnhSQ@mail.gmail.com' \
    --to=tkjos@google.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.