From: Jacek Tomaka
Knights Landing supports half baked LBR_FORMAT_TIME format. The addresses are
linear but it does have MISPREDICT bit but nothing else.
Unfortunately IA32_PERF_CAPABILITIES[5:0] will report LBR_FORMAT_LIP. This
change teaches LBR about this Knights Landing quirk.
---
arch/x86
--
kernel: 4.4.145-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git branch: 4.4.145-rc1-hikey-20180727-245
git commit: 1712dec90e9e99c2d1f1e30f1071bbe656ecf600
git describe: 4.4.145-rc1-hikey-20180727-245
Test details:
https://qa-reports.linaro.org/lkft/li
Linus,
I2C has some driver bugfixes for you.
Please pull.
Thanks,
Wolfram
The following changes since commit d72e90f33aa4709ebecc5005562f52335e106a60:
Linux 4.18-rc6 (2018-07-22 14:12:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa
On 27 July 2018 at 15:38, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.116 release.
> There are 33 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 27 July 2018 at 15:29, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.59 release.
> There are 48 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 27 July 2018 at 15:14, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.17.11 release.
> There are 66 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
diff --git a/Makefile b/Makefile
index 0ab689c38e82..e2664c641109 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 17
-SUBLEVEL = 10
+SUBLEVEL = 11
EXTRAVERSION =
NAME = Merciless Moray
diff --git a/arch/mips/ath79/common.c b/ar
I'm announcing the release of the 4.17.11 kernel.
All users of the 4.17 kernel series must upgrade.
The updated 4.17.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.17.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index ffc9b4e3867e..81b0e99dce80 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 14
-SUBLEVEL = 58
+SUBLEVEL = 59
EXTRAVERSION =
NAME = Petit Gorille
@@ -642,6 +642,7 @@ KBUILD_CFLAGS += $
diff --git a/Makefile b/Makefile
index 889c58e39928..a6b011778960 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 115
+SUBLEVEL = 116
EXTRAVERSION =
NAME = Roaring Lionus
@@ -635,6 +635,7 @@ KBUILD_CFLAGS += $(call
cc-disable-warning,frame-ad
I'm announcing the release of the 4.14.59 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.9.116 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
On Fri, 27 Jul 2018, Joe Perches wrote:
> On Fri, 2018-07-27 at 10:21 +, David Laight wrote:
> > From: Joe Perches Sent: 27 July 2018 11:09
> > > On Fri, 2018-07-27 at 10:04 +, David Laight wrote:
> > > > From: Andrew Morton Sent: 26 July 2018 20:28
> > > > > On Thu, 26 Jul 2018 12:25:3
I'm announcing the release of the 3.18.117 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be browsed at the normal kernel.org git web browser
diff --git a/Makefile b/Makefile
index 63f3e2438a26..be31491a2d67 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 144
+SUBLEVEL = 145
EXTRAVERSION =
NAME = Blurry Fish Butt
@@ -624,6 +624,7 @@ KBUILD_CFLAGS += $(call
cc-disable-warning,frame-
I'm announcing the release of the 4.4.145 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 973e8568e52d..9c894e7e586d 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 18
-SUBLEVEL = 116
+SUBLEVEL = 117
EXTRAVERSION =
NAME = Diseased Newt
@@ -613,6 +613,7 @@ KBUILD_CFLAGS += $(call
cc-disable-warning,frame-ad
Ben,
Am Samstag, 28. Juli 2018, 03:28:58 CEST schrieb Ben Hutchings:
> > > Isn't there a risk here, that a read error leads to erasing data that
> > > might be recoverable if the read is retried?
> >
> > Well, read error means that already something went very wrong. At other
> > places
> > in UB
Srinivas Pandruvada writes:
> Enable HWP boost on Skylake server and workstations.
>
Please revert this series, it led to significant energy usage and
graphics performance regressions [1]. The reasons are roughly the ones
we discussed by e-mail off-list last April: This causes the intel_pstate
2018-07-26 0:01 GMT+09:00 Jeremy Cline :
> On 07/25/2018 10:39 AM, Masahiro Yamada wrote:
>> 2018-07-21 4:35 GMT+09:00 Jeremy Cline :
>>> Use the print function. This maintains Python 2 support and should have
>>> no functional change.
>>>
>>> Signed-off-by: Jeremy Cline
>>> ---
>>> scripts/traci
On Fri, Jul 27, 2018 at 10:31:48AM -0700, Guenter Roeck wrote:
> On Fri, Jul 27, 2018 at 11:44:53AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.17.11 release.
> > There are 66 patches in this series, all will be posted as a response
> > to this one.
On Fri, Jul 27, 2018 at 01:49:42PM -0600, Shuah Khan wrote:
> On 07/27/2018 03:44 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.17.11 release.
> > There are 66 patches in this series, all will be posted as a response
> > to this one. If anyone has any iss
From: Todd Poynor
The device pointer passed into get_mapping() will never be NULL; the
check is unnecessary.
Reported-by: Greg Kroah-Hartman
Signed-off-by: Todd Poynor
---
drivers/staging/gasket/gasket_sysfs.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/staging/gasket/gask
From: Todd Poynor
Remove the check for refcount already zero, which shouldn't be
necessary.
Signed-off-by: Todd Poynor
---
drivers/staging/gasket/gasket_sysfs.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/staging/gasket/gasket_sysfs.c
b/drivers/staging/gasket/gasket_sysfs.c
i
From: Todd Poynor
The fun continues with gasket+apex: remove dead code and unnecessary
stuff, fixup apex PCI class for devices that advertise class 0
(undefined), and make sure the struct device doesn't go away on us.
Most of these from review comments of previous patch series.
Todd Poynor (5):
From: Todd Poynor
Apex chips with class 0 (PCI_CLASS_NOT_DEFINED) fixed up to
PCI_CLASS_SYSTEM_OTHER to enable PCI resource assignments.
Signed-off-by: Todd Poynor
---
drivers/staging/gasket/apex_driver.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/staging/gasket/apex_dr
From: Todd Poynor
Remove code with TODOs on it for working around apparent problems
previously seen in a qemu environment where dma_ops was not set
correctly. There is no user of this in the current code.
Signed-off-by: Todd Poynor
---
drivers/staging/gasket/gasket_core.c | 2 +-
drive
From: Todd Poynor
Hold a reference on the struct device kobject while a pointer to that
device is in use by gasket.
Reported-by: Greg Kroah-Hartman
Signed-off-by: Todd Poynor
---
drivers/staging/gasket/gasket_core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers
Compliment of the day to you Dear Friend.
Dear Friend.
I am Mrs. Amina Kadi. am sending this brief letter to solicit your
partnership to transfer $5.5 million US Dollars. I shall send you
more information and procedures when I receive positive response from
you.
Mrs. Amina Kadi
On 7/27/2018 8:39 PM, Pierre-Louis Bossart wrote:
> On 7/27/18 5:13 AM, Akshu Agrawal wrote:
>> There are cases where a pointer function populates
>> runtime->delay, such as:
>> ./sound/pci/hda/hda_controller.c
>> ./sound/soc/intel/atom/sst-mfld-platform-pcm.c
>>
>> Also, in some cases cpu dai u
From: "Joel Fernandes (Google)"
The 0-day bot caught an issue which all my tests missed (will add it
into my tests) where this_cpu_ptr is incorrectly returning the wrong
pointer from get_lock_stats. Fix it.
Fixes: f4ac253a8df0 ("lockdep: use this_cpu_ptr instead of get_cpu_var stats")
Signed-off
Many CPU architectures have caches that can scale independent of the CPUs.
Frequency scaling of the caches is necessary to make sure the cache is not
a performance bottleneck that leads to poor performance and power. The same
idea applies for RAM/DDR.
To achieve this, this patch adds a generic dev
> ACPI Warning: \_SB.IETM._ART: Return Package type mismatch ..
_ART is the AML method for "Active Cooling Relationship Table".
iIt tells the system how fans are related to temperature sensors.
It is likely that Windows uses DPTF on this platform, and since DPTF
is not using _ART, Linux may be
Hello Dear, I am Miss Lisa. I have very important thing to discuss
with you. please, this information is very vital. Contact me with my
private email so we can talk ( lisajoh...@hotmail.com ) I find your
email when I was searching for some that will understand me.
Lisa
On 2018/07/28 2:32, David Howells wrote:
> Implement the security hook to check the creation of a new mountpoint for
> Tomoyo.
>
> As far as I can tell, Tomoyo doesn't make use of the mount data or parse
> any mount options, so I haven't implemented any of the fs_context hooks for
> it.
>
> Signe
On Fri, 27 Jul 2018 10:31:45 -0400
Steven Rostedt wrote:
> On Fri, 27 Jul 2018 08:26:40 -0600
> Shuah Khan wrote:
>
> > Masami,
> >
> > The patch isn't in my Inbox. Could you please send it.
>
> You don't subscribe to LKML? ;-)
>
> I just bounced it to you.
>
> -- Steve
Sorry Shuah and Ste
Fix kprobe string argument testcase to not probe notrace
function. Instead, it probes tracefs function which must
be available with ftrace.
Signed-off-by: Masami Hiramatsu
---
Changes in v3:
- Fix probepoint testcase too.
---
.../ftrace/test.d/kprobe/kprobe_args_string.tc | 30 -
Prohibit kprobe-events probing on notrace function.
Since probing on the notrace function can cause recursive
event call. In most case those are just skipped, but
in some case it falls into infinit recursive call.
This protection can be disabled by the kconfig
CONFIG_KPROBE_EVENTS_ON_NOTRACE=y, bu
From: Francis Deslauriers
Move selftest function to its own compile unit so it can be compiled
with the ftrace cflags (CC_FLAGS_FTRACE) allowing it to be probed
during the ftrace startup tests.
Signed-off-by: Francis Deslauriers
Signed-off-by: Masami Hiramatsu
---
kernel/trace/Makefile
Hello,
This is the 3rd version of the series to prohibit kprobe
on notrace functions which Francis sent before.
This version fixes some issues on previous version. Fix
to handle the no-symbol kprobe-events correctly and Fix
probepoint.tc testcase to not use notrace function as
a probe point.
Tha
On Sat, Jul 28, 2018 at 12:07:19AM +, David Chen wrote:
> Hi Paul,
>
> I wasn't talking about the xchg() though.
>
> The smp_mb__after_atomic() is not for xchg(), it's for `*tail =
> rdp->nocb_gp_head;`
> it's stated so in the comment. And I do think we need ordering between
> `*tail = rdp->
On Fri, Jul 27, 2018 at 5:02 PM Schmauss, Erik wrote:
>
> The patch below should be able to fix this.
Yes, the error messages seem gone with this.
I see another ACPI warning, but that one has always been there:
acpi INT33D5:00: intel-hid: created platform device
ACPI Warning: \_SB.IETM._ART
On Thu, 2018-07-26 at 08:25 +0200, Richard Weinberger wrote:
> Ben,
>
> Am Donnerstag, 26. Juli 2018, 04:12:54 CEST schrieb Ben Hutchings:
> > On Tue, 2018-07-10 at 20:24 +0200, Greg Kroah-Hartman wrote:
> > > 4.4-stable review patch. If anyone has any objections, please let me
> > > know.
> > >
HELLO DEAR MY DONATION TO YOU.
May the peace of the Almighty God be with you and your Family,
With Due Respect and Humility, I was compelled to write you under humanitarian
ground. My name is Mrs Rosareio Romarinhio. TIMOR Origin but married with Late
Sir Ratnavale from MALAYSIA. I have took a
On Thu, 26 Jul 2018 14:53:27 +0900
Masami Hiramatsu wrote:
> Prohibit kprobe-events probing on notrace function.
> Since probing on the notrace function can cause recursive
> event call. In most case those are just skipped, but
> in some case it falls into infinit recursive call.
>
> This protec
2018-07-27 16:48 GMT+09:00 Christoph Hellwig :
> On Fri, Jul 27, 2018 at 10:32:19AM +0900, Masahiro Yamada wrote:
>> This will just add a new unmet dependency warning.
>> CONFIG_PREEMPT_COUNT will be still selected.
>
> True. I guess we simply need to prohibit CONFIG_DEBUG_ATOMIC_SLEEP
> explicitl
Hi David,
> On 28 Jul 2018, at 00:49, David Howells wrote:
> Jann Horn wrote:
>>> +static int fsinfo_generic_name_encoding(struct dentry *dentry, char *buf)
>>> +{
>>> + static const char encoding[] = "utf8";
>>> +
>>> + if (buf)
>>> + memcpy(buf, encoding, sizeof(encod
Each time we sync cfs_rq->runtime_expires with cfs_b->runtime_expires,
we should sync its ->expires_seq too. However it is missing
for distribute_cfs_runtime(), especially the slack timer call path.
Fixes: 512ac999d275 ("sched/fair: Fix bandwidth timer clock drift condition")
Cc: Xunlei Pang
Cc:
On Fri, Jul 27, 2018 at 01:34:31PM -0700, Sodagudi Prasad wrote:
> > The error should be pretty clear: "Inode table for bg 0 marked as
> > needing zeroing". That should never happen.
>
> Can you provide any debug patch to detect when this corruption is happening?
> Source of this corruption and h
On 2018-05-23 07:39, Rob Herring wrote:
Reviving an old thread. Sorry about the late reply. Got busy.
On Tue, May 22, 2018 at 1:30 PM, Saravana Kannan
wrote:
On 05/22/2018 11:08 AM, Rob Herring wrote:
On Fri, May 18, 2018 at 12:52:40AM -0700, Saravana Kannan wrote:
The firmware present in
Jann Horn wrote:
> > fs/fat/inode.c: sprintf(buf, "cp%d", sbi->options.codepage);
>
> sprintf(buf, "cp%d", sbi->options.codepage);
> sbi->nls_disk = load_nls(buf);
> if (!sbi->nls_disk) {
> fat_msg(sb, KERN_ERR, "codepage %s not found", buf);
>
Hi Paul,
I wasn't talking about the xchg() though.
The smp_mb__after_atomic() is not for xchg(), it's for `*tail =
rdp->nocb_gp_head;`
it's stated so in the comment. And I do think we need ordering between
`*tail = rdp->nocb_gp_head;` and wake up, because the waiter is checking on
head not tail
On Fri, Jul 27, 2018 at 03:05:43PM -0700, Sandeep Patil wrote:
> On Fri, Jul 27, 2018 at 04:21:14PM -0400, Theodore Y. Ts'o wrote:
> > On Fri, Jul 27, 2018 at 04:11:03PM -0400, Steven Rostedt wrote:
> > > That said, I would assume that
> > > other Android utilities are using other debugfs files for
On 7/26/18 7:38 AM, Christoph Hellwig wrote:
This patch adds a driver for the Platform Level Interrupt Controller (PLIC)
specified as part of the RISC-V supervisor level ISA manual, in the memory
layout implemented by SiFive and qemu.
The PLIC connects global interrupt sources to the local inter
> -Original Message-
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Schmauss, Erik
> Sent: Friday, July 27, 2018 2:51 PM
> To: Linus Torvalds ; Rafael J. Wysocki
>
> Cc: Linux ACPI ; Linux Kernel Mailing List ker...@vger.kernel.org>
>
On Fri, 27 Jul 2018 17:43:07 -0400
Steven Rostedt wrote:
> On Thu, 26 Jul 2018 14:54:23 +0900
> Masami Hiramatsu wrote:
>
> > Fix kprobe string argument testcase to not probe notrace
> > function. Instead, it probes tracefs function which must
> > be available with ftrace.
>
> Hi Masami,
>
>
On Sat, Jul 28, 2018 at 1:51 AM David Howells wrote:
> David Howells wrote:
>
> > One thing I'm confused about is that fat has both a codepage and a charset
> > and
> > I'm not sure of the difference.
>
> In fact, it's not clear that the codepage is actually used.
>
> warthog>git grep '[
David Howells wrote:
> One thing I'm confused about is that fat has both a codepage and a charset and
> I'm not sure of the difference.
In fact, it's not clear that the codepage is actually used.
warthog>git grep '[.>]codepage'
fs/fat/inode.c: opts->codepage = fat_default_codepa
Jann Horn wrote:
> > +static int fsinfo_generic_name_encoding(struct dentry *dentry, char *buf)
> > +{
> > + static const char encoding[] = "utf8";
> > +
> > + if (buf)
> > + memcpy(buf, encoding, sizeof(encoding) - 1);
> > + return sizeof(encoding) - 1;
> > +}
>
On Fri, Jul 27, 2018 at 11:16:39PM +, David Chen wrote:
> Hi Paul,
>
> Thanks for the advice.
> The bug is kind of hard to hit, so I can't say for certain yet.
Well, you can always remove the "tail == &rdp->nocb_follower_head" as an
extra belt-and-suspenders safety net. I am not putting that
On Thu, Jul 26, 2018 at 1:07 PM, Johannes Weiner wrote:
> On Thu, Jul 26, 2018 at 11:07:32AM +1000, Singh, Balbir wrote:
>> On 7/25/18 1:15 AM, Johannes Weiner wrote:
>> > On Tue, Jul 24, 2018 at 07:14:02AM +1000, Balbir Singh wrote:
>> >> Does the mechanism scale? I am a little concerned about ho
Hi Paul,
Thanks for the advice.
The bug is kind of hard to hit, so I can't say for certain yet.
Though after another look at the code, I found out the `smp_mb__after_atomic();`
seems to be only a compiler barrier on x86.
tail = xchg(&rdp->nocb_follower_tail, rdp->nocb_gp_tail);
The enumerated type dm_dig_connect_e is only used to group constant
values, as the actual type is never used as the type for the variables
which use the defined constants (cur_connect_state and pre_connect_state).
These two member variables have had there defined types changed to
properly reflect
Remove the enumerated type dm_dig_op_e. The type is only used as a
parameter to the function dm_change_dynamic_initgain_thresh(), but
that function is never referenced in the code at all.
I would consider this to be a coding style change as the function is
never referenced and as a result the enum
The enumerated type dm_dig_alg_e is only used by one variable in the
code, 'dig_algorithm', a member variable of the structure dig. That
member variable was defined to be of type 'u8' thus negating any
advantage of the use of an enumerated type, (compiler type-checking).
The type of the variable '
The enumerated type dm_dig_cs_ratio_e is never actually used as a type,
but only as a collection of related constants. This is because the
variables, which use the defined constant values, are defined as being
of type u8 rather then enum dm_dig_cs_ratio_e. This omission negates
the possibility of t
Refactor the use of the enumerated type dm_dig_sta_e, which is not
actually used for type checking by the compiler.
The enumerated type defines values for the enumeration, which are used
by both dig_state and dig_highpwr_state, (members of the struct dig).
Both of those variables were defined as b
The enumerated type dm_ratr_sta_e was defined in the file
drivers/staging/rtl8192u/r8192U_dm.h but never actually used in that
file. The only variable which uses this enumerated type is 'ratr_state',
a member variable of the _rate_adaptive structure defined in the file
drivers/staging/rtl8192u/r819
Remove the unused definition for DM_check_fsync_time_interval.
This is a coding style change which should have no impact on runtime
code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/r8192U_dm.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/rtl8192
The enumerated type dm_dig_pd_th_e is never actually used as
the type for the two variables which use the constants, which the
enumeration defines. This omission removes the possibility of taking
advantage of compiler type checking.
To correct this the two member variables, (curpd_thstate & prepd_
The enumerated type DM_CCK_Rx_Path_Method is used as a container for
constant definitions, rather then an enumerated type enabling compiler
type checking. To correct this, the variable which uses the constants,
defined by the enumeration, has had its type changed from a u8 to the
enumeration.
Addi
What was intended as a clean up of the file
drivers/staging/rtl8192u/r8192U_dm.h turned into refactoring of most of
the enumerated types defined in the file. Most of the enumerated types
were simply used to define a collection of constants, rather then
actually using the types as enumerated types.
The enumerated type dm_dig_dbg_e is never used in code so has simply
been removed from the source code.
this is a coding style change which should have no impact on runtime
code execution.
Signed-off-by: John Whitmore
---
drivers/staging/rtl8192u/r8192U_dm.h | 6 --
1 file changed, 6 deleti
Quoting Eddie.Horng (eddie.ho...@mediatek.com):
>
> The code in cap_inode_getsecurity(), introduced by commit 8db6c34f1dbc
> ("Introduce v3 namespaced file capabilities"), should use
> d_find_any_alias() instead of d_find_alias() do handle unhashed dentry
> correctly. This is needed, for example,
On Fri, Jul 27, 2018 at 7:36 PM David Howells wrote:
>
> Add a system call to allow filesystem information to be queried. A request
> value can be given to indicate the desired attribute. Support is provided
> for enumerating multi-value attributes.
[...]
> +static int fsinfo_generic_ids(struct
On Fri, Jul 27, 2018 at 02:13:57PM +0200, Tino Lehnig wrote:
> On 07/27/2018 02:05 PM, Minchan Kim wrote:
> > And bad page is always with writeback enable?
> >
> > writeback enable means "echo "some dev" > /sys/block/zram0/backing_dev,
> > not just enable CONFIG_ZRAM_WRITEBACK.
>
> Yes, the bug o
On Wed, Jul 25, 2018 at 06:27:59PM +0200, Krzysztof Kozlowski wrote:
> On 25 July 2018 at 16:43, Bartlomiej Zolnierkiewicz
> wrote:
> > On Tuesday, July 24, 2018 10:03:12 PM Krzysztof Kozlowski wrote:
> >> On Tue, Jul 24, 2018 at 06:46:35PM +0200, Bartlomiej Zolnierkiewicz wrote:
> >> >
> >> > Hi,
On Thu, Jul 19, 2018 at 03:22:21PM +0530, Anand Moon wrote:
> Hi Krzysztof,
>
Please send a new version of the series with applied fixes
and also get reviews from the samsung devs. Thanks.
>
> Best Regards
> -Anand
The last instances of PTR_RET have been replaced with PTR_ERR_OR_ZERO.
We can completely remove PTR_RET from the codebase now.
Signed-off-by: Gustavo A. R. Silva
---
include/linux/err.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/linux/err.h b/include/linux/err.h
index 87be243
On Fri, Jul 27, 2018 at 03:40:52PM -0700, Eduardo Valentin wrote:
> On Wed, Jul 25, 2018 at 06:12:28PM -0700, Matthias Kaehlcke wrote:
> > Hi Doug,
> >
> > On Wed, Jul 25, 2018 at 04:19:56PM -0700, Doug Anderson wrote:
> >
> > > On Tue, Jul 24, 2018 at 4:46 PM, Matthias Kaehlcke
> > > wrote:
>
On Wed, Jul 25, 2018 at 06:12:28PM -0700, Matthias Kaehlcke wrote:
> Hi Doug,
>
> On Wed, Jul 25, 2018 at 04:19:56PM -0700, Doug Anderson wrote:
>
> > On Tue, Jul 24, 2018 at 4:46 PM, Matthias Kaehlcke
> > wrote:
> > > +static int qpnp_tm_update_critical_trip_temp(struct qpnp_tm_chip *chip,
> >
On Fri, Jul 27, 2018 at 7:34 PM David Howells wrote:
>
> Add a syscall for configuring a filesystem creation context and triggering
> actions upon it, to be used in conjunction with fsopen, fspick and fsmount.
>
> long fsconfig(int fs_fd, unsigned int cmd, const char *key,
>
On Fri, Jul 27, 2018 at 07:07:46PM +, David Chen wrote:
> Hi Paul,
>
> I'd like to opinion again on this subject.
>
> So we are going to backport this patch:
> 6b5fc3a13318 ("rcu: Add memory barriers for NOCB leader wakeup")
Does this one solve the problem, or are you still seeing hangs?
If
Andy Lutomirski wrote:
> > [*] Not without a 6-arg syscall or some other way of passing it.
>
> Are there still architectures that have problems with 6-arg syscalls?
As I understand it, 6-arg syscalls are frowned upon.
> I suppose that, as long as there is never a case where fsconfig_set_path
Andy Lutomirski wrote:
> > Add a system call to allow filesystem information to be queried. A request
> > value can be given to indicate the desired attribute. Support is provided
> > for enumerating multi-value attributes.
>
> Has anyone seriously reviewed this?
I don't know. I've certainly
Andy Lutomirski wrote:
> int mfd = fsmount(...);
>
> where you pass in an fscontext fd and get out an fd referring to the
> root of the filesystem? In this case, maybe fs_open_root(2) would be
> a better name.
It's not necessarily the root of the filesystem in the sense of sb->s_root.
It might
On Fri, Jul 27, 2018 at 04:40:09PM -0500, Yazen Ghannam wrote:
> - /* Don't support asymmetric configurations today */
> - WARN_ON(mca_cfg.banks != 0 && b != mca_cfg.banks);
> - mca_cfg.banks = b;
> + mca_cfg.banks = max(mca_cfg.banks, b);
Should we change mca_cfg.banks to be a per
Andy Lutomirski wrote:
> I have a potentially silly objection. For the old timers, "mount" means to
> stick a reel of tape or some similar object onto a reader, which seems to
> imply that "mount" means to start up the filesystem. For younguns, this
> meaning is probably lost, and the more obviou
On Fri, Jul 27, 2018 at 04:21:14PM -0400, Theodore Y. Ts'o wrote:
> On Fri, Jul 27, 2018 at 04:11:03PM -0400, Steven Rostedt wrote:
> > That said, I would assume that
> > other Android utilities are using other debugfs files for system
> > status and such.
As of today, I think a lot of information
Hi!
> So for instance, this turns:
>
> int cpu = rseq_per_cpu_lock(lock, target_cpu);
> [...]
> rseq_per_cpu_unlock(lock, cpu);
>
> into
>
> int cpu = rseq_this_cpu_lock(lock);
> [...]
> rseq_per_cpu_unlock(lock, cpu);
>
> and:
>
> per_cpu_list_push(list, node, target_cpu);
>
Hi!
> The idea is to eventually incorporate this back into the kernel, so
> that Linux can avoid OOM livelocks (which TECHNICALLY aren't memory
> deadlocks, but for the user indistinguishable) out of the box.
>
> We also use psi memory pressure for loadshedding. Our batch job
psi->PSI?
>
On Fri, Jul 27, 2018 at 2:51 PM, David Howells wrote:
> Andy Lutomirski wrote:
>
>> Unless I'm rather confused, you have two or possibly three ways to
>> pass in an open fd. Can you clarify what the difference is and/or
>> remove all but one of them?
>
> No, they're not equivalent.
>
>> > (*) f
Dear RT folks!
I'm pleased to announce the v4.16.18-rt11 patch set.
Changes since v4.16.18-rt10:
- Finally fix the SIMD locking on arm64.
- Revert the srcu based notifier in crypto code. This is no longer
required since the rwsem on RT allows multiple reader.
- Add a per-CPU lock in
> -Original Message-
> From: linux-acpi-ow...@vger.kernel.org [mailto:linux-acpi-
> ow...@vger.kernel.org] On Behalf Of Linus Torvalds
> Sent: Friday, July 27, 2018 11:38 AM
> To: Rafael J. Wysocki
> Cc: Linux ACPI ; Linux Kernel Mailing List ker...@vger.kernel.org>
> Subject: Re: [GIT
Hello Jens,
On Fri, 27 Jul 2018, Jens Axboe wrote:
> SeongJae please take a look at this. It's been weeks now and silence
> on your end.
I'm so sorry for late response. Unfortunately, I was too busy to look
this regression deeply. Now the things bothering me are almost finished.
Maybe I will
As there is one-to-one relation between a bpf program
and cgroup local storage map, there is no sense in
creating a map of cgroup local storage maps.
Forbid it explicitly to avoid possible side effects.
Signed-off-by: Roman Gushchin
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Acked-by: Martin K
If a bpf program is using cgroup local storage, allocate
a bpf_cgroup_storage structure automatically on attaching the program
to a cgroup and save the pointer into the corresponding bpf_prog_list
entry.
Analogically, release the cgroup local storage on detaching
of the bpf program.
Signed-off-by:
Andy Lutomirski wrote:
> Unless I'm rather confused, you have two or possibly three ways to
> pass in an open fd. Can you clarify what the difference is and/or
> remove all but one of them?
No, they're not equivalent.
> > (*) fsconfig_set_path: A non-empty path is specified. The parameter mu
On Fri, Jul 27, 2018 at 02:57:44PM -0400, Steven Rostedt wrote:
> On Fri, 27 Jul 2018 11:51:13 -0700
> Joel Fernandes wrote:
>
> > When I refactored the code as Peter suggested I happen to move the warning
> > out but didn't simplify it further (I had it at the back of my head to do
> > that but
From: Yazen Ghannam
Linux reads MCG_CAP[Count] to find the number of MCA banks visible to a
CPU. Currently, this is assumed to be the same for all CPUs and a
warning is shown if there is a difference. The number of banks is
overwritten with the MCG_CAP[Count] value of each following CPU that
boot
1 - 100 of 784 matches
Mail list logo
