From: Vasily Gorbik <gor@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Matthew Garrett <matthewgarrett@google.com>,
James Morris <jmorris@namei.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: linux-next: Tree for Aug 13
Date: Tue, 13 Aug 2019 17:10:48 +0200 [thread overview]
Message-ID: <your-ad-here.call-01565709048-ext-0789@work.hours> (raw)
In-Reply-To: <20190813105645.4ffba70c@gandalf.local.home>
On Tue, Aug 13, 2019 at 10:56:45AM -0400, Steven Rostedt wrote:
>
> This looks related to what Marek posted.
>
> https://lore.kernel.org/linux-security-module/3028ed35-3b6d-459f-f3c8-103c5636fe95@samsung.com/
>
> Care to apply the change he suggested to see if it fixes the issue for
> you. If it does, Marek, can you make an official patch?
>
> -- Steve
Right, same issue - same fix. Oh well, at least I got a bit more
familiar with the code.
--
⣿⣿⣿⣿⢋⡀⣀⠹⣿⣿⣿⣿
⣿⣿⣿⣿⠠⣶⡦⠀⣿⣿⣿⣿
⣿⣿⣿⠏⣴⣮⣴⣧⠈⢿⣿⣿
⣿⣿⡏⢰⣿⠖⣠⣿⡆⠈⣿⣿
⣿⢛⣵⣄⠙⣶⣶⡟⣅⣠⠹⣿
⣿⣜⣛⠻⢎⣉⣉⣀⠿⣫⣵⣿
next prev parent reply other threads:[~2019-08-13 15:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 9:19 linux-next: Tree for Aug 13 Stephen Rothwell
2019-08-13 12:41 ` Vasily Gorbik
2019-08-13 14:56 ` Steven Rostedt
2019-08-13 15:10 ` Vasily Gorbik [this message]
2019-08-14 6:14 ` Marek Szyprowski
2019-08-14 7:35 ` Stephen Rothwell
2019-08-13 14:57 ` Vasily Gorbik
2019-08-13 14:58 ` [PATCH] tracefs: avoid crash when open callback is not set Vasily Gorbik
-- strict thread matches above, loose matches on Subject: below --
2021-08-13 8:59 linux-next: Tree for Aug 13 Stephen Rothwell
2020-08-13 6:58 Stephen Rothwell
2018-08-13 9:32 Stephen Rothwell
2018-08-13 13:23 ` Guenter Roeck
2015-08-13 7:13 Stephen Rothwell
2014-08-13 3:56 Stephen Rothwell
2013-08-13 8:28 Stephen Rothwell
2013-08-13 8:28 ` Stephen Rothwell
2012-08-13 2:54 Stephen Rothwell
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=your-ad-here.call-01565709048-ext-0789@work.hours \
--to=gor@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=matthewgarrett@google.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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.