I'm announcing the release of the 4.14.70 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.18.8 kernel.
All users of the 4.18 kernel series must upgrade.
The updated 4.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.18.y
and can be browsed at the normal kernel.org git web browser:
On Sat, Sep 15, 2018 at 04:34:56AM +0800, Yang Shi wrote:
> Regression and performance data:
> Did the below regression test with setting thresh to 4K manually in the code:
> * Full LTP
> * Trinity (munmap/all vm syscalls)
> * Stress-ng: mmap/mmapfork/mmapfixed/mmapaddr/mmapmany/vm
> * mm-t
On Fri, 14 Sep 2018, Fenghua Yu wrote:
> int parse_cbm(void *_data, struct rdt_resource *r, struct rdt_domain *d);
> -int parse_bw(void *_buf, struct rdt_resource *r, struct rdt_domain *d);
> +int parse_bw(void *_data, struct rdt_resource *r, struct rdt_domain *d);
Sorry no. This keeps the code
Attention Please!,
This is to official inform you that we have been having meetings for
the past Three (3) Weeks which ended two days ago with the World Bank
president and other seven continent presidents on the Congress we
treated on solution to Scam victim and the
world economic crises that e
On Fri, 14 Sep 2018, Fenghua Yu wrote:
> If information for a cache instance with more CLOSIDs than another is
> being generated we thus encounter a warning like:
>
> [ 130.010591] [ cut here ]
> [ 130.016680] invalid mode for closid 8
> [ 130.021791] WARNING: CPU: 88 PI
On Tue, 11 Sep 2018, Feng Tang wrote:
> Thanks for the suggestion, and I have 2 patches: one adds a build warning,
> the other prepares fixmap page table on demand and doesn't need warning.
The latter please.
> But I met a problem, that the "__end_of_permanent_fixed_addresses" is
> defined in
Drop call to of_match_device, which is subsumed by the subsequent
call to of_device_get_match_data. The code becomes simpler, and a
temporary variable can be dropped.
Found by coccinelle.
Signed-off-by: YueHaibing
---
drivers/iio/potentiometer/max5481.c | 7 ++-
1 file changed, 2 insertion
Drop call to of_match_device, which is subsumed by the subsequent
call to of_device_get_match_data. The code becomes simpler, and a
temporary variable can be dropped.
Found by coccinelle.
Signed-off-by: YueHaibing
---
drivers/iio/potentiometer/mcp4018.c | 7 ++-
1 file changed, 2 insertion
Drop call to of_match_device, which is subsumed by the subsequent
call to of_device_get_match_data. The code becomes simpler, and a
temporary variable can be dropped.
Found by coccinelle.
Signed-off-by: YueHaibing
---
drivers/iio/potentiometer/mcp4531.c | 7 ++-
1 file changed, 2 insertion
Add device-tree description of the Mitac MIO A701 board.
This is aimed at replacing mioa701.c board file, and once stabilized,
the leftover, such as the suspend resume mechanics will rely on a new
IPL, and not the legacy Windows CE one.
Signed-off-by: Robert Jarzmik
---
Since v1: fix lcd_supply a
Ping.
On 2018/7/25 15:07, YueHaibing wrote:
> Sean Wang reported dma_zalloc_coherent doesn't work as expect on his
> armv7,the allocated mem is not zeroed.The reason is __alloc_from_pool
> doesn't honor __GFP_ZERO.
>
> As commit 6829e274a623 ("arm64: dma-mapping: always clear allocated buffers"
On 2018-09-15 12:52, YueHaibing wrote:
> Drop call to of_match_device, which is subsumed by the subsequent
> call to of_device_get_match_data. The code becomes simpler, and a
> temporary variable can be dropped.
>
> Found by coccinelle.
>
> Signed-off-by: YueHaibing
Acked-by: Peter Rosin
Che
On 2018-09-15 12:54, YueHaibing wrote:
> Drop call to of_match_device, which is subsumed by the subsequent
> call to of_device_get_match_data. The code becomes simpler, and a
> temporary variable can be dropped.
>
> Found by coccinelle.
>
> Signed-off-by: YueHaibing
Acked-by: Peter Rosin
Che
* Arnd Bergmann wrote:
> diff --git a/arch/x86/include/uapi/asm/elf.h b/arch/x86/include/uapi/asm/elf.h
> new file mode 100644
> index ..a640e1224939
> --- /dev/null
> +++ b/arch/x86/include/uapi/asm/elf.h
> @@ -0,0 +1,30 @@
> +/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-
Use rtc_add_group to add the common sysfs group to avoid a possible race
condition.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-isl1208.c | 11 +--
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/drivers/rtc/rtc-isl1208.c b/drivers/rtc/rtc-isl1208.c
index ea18a8f4b
* tip-bot for Vincent Guittot wrote:
> Commit-ID: 2e62c4743adc4c7bfcbc1f45118fc7bec58cf30a
> Gitweb:
> https://git.kernel.org/tip/2e62c4743adc4c7bfcbc1f45118fc7bec58cf30a
> Author: Vincent Guittot
> AuthorDate: Thu, 19 Jul 2018 14:00:06 +0200
> Committer: Ingo Molnar
> CommitDate:
Hello Alexey,
On 09/08/2018 01:13:07+0300, Alexey Khoroshilov wrote:
> After moving rtc_register_device() sysfs group is left unremoved
> on the error path.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov
> Fixes: 236b7187034e ("rtc: isl1
Hi Ingo,
On Sat, 15 Sep 2018 at 13:47, Ingo Molnar wrote:
>
>
> * tip-bot for Vincent Guittot wrote:
>
> > Commit-ID: 2e62c4743adc4c7bfcbc1f45118fc7bec58cf30a
> > Gitweb:
> > https://git.kernel.org/tip/2e62c4743adc4c7bfcbc1f45118fc7bec58cf30a
> > Author: Vincent Guittot
> > AuthorDate
* Vincent Guittot wrote:
> Hi Ingo,
>
> On Sat, 15 Sep 2018 at 13:47, Ingo Molnar wrote:
> >
> >
> > * tip-bot for Vincent Guittot wrote:
> >
> > > Commit-ID: 2e62c4743adc4c7bfcbc1f45118fc7bec58cf30a
> > > Gitweb:
> > > https://git.kernel.org/tip/2e62c4743adc4c7bfcbc1f45118fc7bec58cf30
Linus,
Please pull the latest locking-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-for-linus
# HEAD: 0b405c65ad459f5f4d3db1672246172bd19d946d locking/ww_mutex: Fix
spelling mistake "cylic" -> "cyclic"
Misc fixes: liblockdep fix
On Fri, Sep 14, 2018 at 12:53:00PM -0700, Paul Burton wrote:
> Hi Mike,
>
> On Mon, Sep 10, 2018 at 12:23:18PM +0300, Mike Rapoport wrote:
> > MIPS already has memblock support and all the memory is already registered
> > with it.
> >
> > This patch replaces bootmem memory reservations with membl
The whole static protection magic is silently fixing up anything which is
handed in. That's just wrong. The offending call sites need to be fixed.
Add a debug mechanism which emits a warning if a requested mapping needs to be
fixed up. The DETECT debug mechanism is really not meant to be enabled e
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: cb48b6a26cace226d8b299a48c73e808eb0c4f61 Merge tag
'perf-urgent-for-mingo-4.19-20180912' of
git://git.kernel.org/pub/scm/linux/kerne
on Thu, Sep 13, 2018 at 8:32 PM Amir Goldstein wrote:
>On Thu, Sep 13, 2018 at 2:25 PM Nixiaoming wrote:
>>
>> On Tue, Sep 11, 2018 at 11:12 PM Amir Goldstein wrote:
>> >On Tue, Sep 11, 2018 at 9:51 AM Nixiaoming wrote:
>> >>
>> >> Inotify api cannot display information about users and processes
This patch removes do {} while (0) loop for single statement macros.
Issue found by checkpatch.
Signed-off-by: Nishad Kamdar
---
drivers/staging/mt7621-mmc/sd.c | 28 +++-
1 file changed, 7 insertions(+), 21 deletions(-)
diff --git a/drivers/staging/mt7621-mmc/sd.c b/dri
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
# HEAD: 882a78a9f39f5535b209b4aa0a1741e35b8c67fb sched/fair: Fix kernel-doc
notation warning
Misc fixes: various scheduler metrics corner
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 002b87d2aace62b4f3841c3aa43309d2380092be x86/APM: Fix build warning
when PROC_FS is not enabled
Misc fixes:
- EFI crash fix
- Xen P
On Mon, Jan 13, 2014 at 04:11:38PM -0800, Dave Hansen wrote:
>
> From: Dave Hansen
>
> Right now, there is a "Enable paravirtualization code" option in
> the "Processor Features" menu, which means Xen. There is also a
> group of host-side paravirtualization options specific to KVM
> under the t
Is this commit queued up for inclusion into the stable tree?
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/of/base.c?h=next-20180913&id=e54192b48da75f025ae4b277925eaf6aca1d13bd
Applying the patch on top of v4.18.8 fixes the booting problem for me.
The contents
On Fri, Sep 14, 2018 at 12:13:38PM +0200, Romain Izard wrote:
> When using watchdog_init_timeout to update the default timeout value,
> an error means that there is no "timeout-sec" in the relevant device
> tree node.
>
> This should not prevent binding of the driver to the device.
>
> Fixes: 976
On Sat, 15 Sep 2018 at 14:30, Ingo Molnar wrote:
>
>
> * Vincent Guittot wrote:
>
> > Hi Ingo,
> >
> > On Sat, 15 Sep 2018 at 13:47, Ingo Molnar wrote:
> > >
> > >
> > > * tip-bot for Vincent Guittot wrote:
> > >
> > > > Commit-ID: 2e62c4743adc4c7bfcbc1f45118fc7bec58cf30a
> > > > Gitweb:
Thx for the review, that's very helpful.
On Wed, Sep 12, 2018 at 05:55:14PM +0200, Peter Zijlstra wrote:
> On Wed, Sep 12, 2018 at 09:24:45PM +0800, Guo Ren wrote:
>
> > +#define ATOMIC_OP(op, c_op)
> > \
> > +static inline void atomic_##op(int i, a
On Thu, 6 Sep 2018, Thomas Gleixner wrote:
> On Wed, 5 Sep 2018, Rick Ratzel wrote:
>
> > We're looking for suggestions on how best to proceed with a new change
> > that ideally both supports the use case described above, as well as
> > addresses the symptoms brought up in the initial commit (nega
On Thu, 30 Aug 2018, Rich Felker wrote:
> On Thu, Aug 30, 2018 at 11:19:58AM +0200, Thomas Gleixner wrote:
> > On Wed, 29 Aug 2018, Rich Felker wrote:
> >
> > > I just spent a number of hours helping someone track down a bug that
> > > looks like it's some kind of futex_cmpxchg_enabled detection e
On 09/14, Jeff Layton wrote:
>
> Currently, we have a single refcount variable inside the files_struct.
> When we go to unshare the files_struct, we check this counter and if
> it's elevated, then we allocate a new files_struct instead of just
> repurposing the old one, under the assumption that th
On Sat, Sep 15, 2018 at 05:34:24PM +0200, Thomas Gleixner wrote:
> On Thu, 30 Aug 2018, Rich Felker wrote:
> > On Thu, Aug 30, 2018 at 11:19:58AM +0200, Thomas Gleixner wrote:
> > > On Wed, 29 Aug 2018, Rich Felker wrote:
> > >
> > > > I just spent a number of hours helping someone track down a bu
Some data exfiltration and return-oriented-programming attacks rely on
the ability to infer the location of sensitive data objects. The kernel
page allocator, especially early in system boot, has predictable
first-in-first out behavior for physical pages. Pages are freed in
physical address order w
Data exfiltration attacks via speculative execution and
return-oriented-programming attacks rely on the ability to infer the
location of sensitive data objects. The kernel page allocator, has
predictable first-in-first-out behavior for physical pages. Pages are
freed in physical address order when
When freeing a page with an order >= shuffle_page_order randomly select
the front or back of the list for insertion.
While the mm tries to defragment physical pages into huge pages this can
tend to make the page allocator more predictable over time. Inject the
front-back randomness to preserve the
On 09/14, Jeff Layton wrote:
>
> POSIX mandates that open fds and their associated file locks should be
> preserved across an execve. This works, unless the process is
> multithreaded at the time that execve is called.
>
> In that case, we'll end up unsharing the files_struct but the locks will
> s
In preparation for runtime randomization of the zone lists, take all
(well, most of) the list_*() functions in the buddy allocator and put
them in helper functions. Provide a common control point for injecting
additional behavior when freeing pages.
Cc: Michal Hocko
Cc: Dave Hansen
Signed-off-by
Hi Thomas,
On Sat, Sep 15, 2018 at 12:29:50PM +0200, Thomas Gleixner wrote:
> On Tue, 11 Sep 2018, Feng Tang wrote:
> > Thanks for the suggestion, and I have 2 patches: one adds a build warning,
> >
> > the other prepares fixmap page table on demand and doesn't need warning.
>
> The latter pl
On Sat, Sep 15, 2018 at 12:15:54PM -0400, Rich Felker wrote:
> On Sat, Sep 15, 2018 at 05:34:24PM +0200, Thomas Gleixner wrote:
> > On Thu, 30 Aug 2018, Rich Felker wrote:
> > > On Thu, Aug 30, 2018 at 11:19:58AM +0200, Thomas Gleixner wrote:
> > > > On Wed, 29 Aug 2018, Rich Felker wrote:
> > > >
Hi Sasha,
Sasha Levin wrote on Sat, 15 Sep 2018
01:29:55 +:
> From: Boris Brezillon
>
> [ Upstream commit 8f3931ed975e1d775b87ce85d65ecacd54138359 ]
>
> We want to allow this driver to be selected when COMPILE_TEST=y, this
> means the driver can be compiled for any arch, including MIPS. W
On 2018/09/15 11:33, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 11da3a7f84f1 Linux 4.19-rc3
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=141ffbca40
> kernel config: https://syzkaller.appspot.com/x/.config?x=99
On Sun, 16 Sep 2018, Feng Tang wrote:
> I have tried to change some header files incluing fixmap.h/apicdef.h/
> vsyscall.h, and most of the .c files compile fine now, but I can not
> use the "__end_of_permanent_fixed_addresses" in head_64.S as it is a
> enum type, and could not be recognized by as
Document device tree bindings for ROHM BH1750 ambient light sensor driver.
Signed-off-by: ryang
---
.../devicetree/bindings/iio/light/bh1750.txt | 18 ++
1 file changed, 18 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/light/bh1750.txt
diff --git a/Do
Add device tree support for ROHM BH1750 series ambient light sensors.
Signed-off-by: ryang
---
drivers/iio/light/bh1750.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/iio/light/bh1750.c b/drivers/iio/light/bh1750.c
index a814828e69f5..50b599abb383 100644
--- a/drivers/
On Sat, Sep 15, 2018 at 06:54:30PM +0800, YueHaibing wrote:
> Drop call to of_match_device, which is subsumed by the subsequent
> call to of_device_get_match_data. The code becomes simpler, and a
> temporary variable can be dropped.
>
> Found by coccinelle.
>
> Signed-off-by: YueHaibing
Alread
Urgent Attention Needed.
We have been trying to reach out to you severally in respect to your
compensation scheme funds worth $500,000 provided by the federal
government powered by the world bank group, but due to unclassified
reasons our mails to you have been bounced and our server alerted er
On Sat, 15 Sep 2018, Rich Felker wrote:
> On Sat, Sep 15, 2018 at 05:34:24PM +0200, Thomas Gleixner wrote:
> > By doing that you paper over a non functional fixup which could cause other
> > really hard to decode runtime failures. If that fails there is a bug
> > somewhere else and that runtime che
On Fri, Aug 3, 2018 at 9:47 PM, Masahiro Yamada
wrote:
> Randy Dunlap reports UML occasionally fails to build with -j and
> O= options.
With v4.19-rc2 I'm still seeing a failure (for any parallelism) under ARCH=um
$ make -j8 ARCH=um O=/tmp/foo
...
/home/kees/src/linux-build/um/Makefile:1185: ***
Am Samstag, 15. September 2018, 11:03:57 CEST schrieb agajjar:
> Hi Heiko,
>
> On 9/14/2018 11:23 PM, Heiko Stuebner wrote:
> > Hi Akash,
> >
> > Am Freitag, 14. September 2018, 14:09:09 CEST schrieb Akash Gajjar:
> >> Rockpro64 board is a rockchip RK3399 based board from pine64.org.
> >> This com
On Fri, Sep 14, 2018 at 09:38:52PM +0200, Arnd Bergmann wrote:
> On Fri, Sep 14, 2018 at 8:17 PM gregkh wrote:
> >
> > On Fri, Sep 14, 2018 at 05:15:52PM +0200, Arnd Bergmann wrote:
> > > On Thu, Sep 13, 2018 at 4:40 AM Al Viro wrote:
>
> > > + case TCSETX:
> > > + case TCSETXF:
> >
Commit-ID: 6a1cac56f41f9ea94e440dfcc1cac44b41a1b194
Gitweb: https://git.kernel.org/tip/6a1cac56f41f9ea94e440dfcc1cac44b41a1b194
Author: Brijesh Singh
AuthorDate: Fri, 14 Sep 2018 08:45:59 -0500
Committer: Thomas Gleixner
CommitDate: Sat, 15 Sep 2018 20:48:46 +0200
x86/kvm: Use __bss_de
Commit-ID: b3f0907c71e006e12fde74ea9a745b6096b6f90f
Gitweb: https://git.kernel.org/tip/b3f0907c71e006e12fde74ea9a745b6096b6f90f
Author: Brijesh Singh
AuthorDate: Fri, 14 Sep 2018 08:45:58 -0500
Committer: Thomas Gleixner
CommitDate: Sat, 15 Sep 2018 20:48:45 +0200
x86/mm: Add .bss..dec
внимания;
Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных
администратором, который в настоящее время работает на 10.9GB, Вы не сможете
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый
ящик почты. Чтобы восстановить работоспособность Ваше
export nvme disk name, queue id, sq_head, sq_tail to trace event
usage example:
go to the event directory:
cd /sys/kernel/debug/tracing/events/nvme/nvme_sq
filter by disk name:
echo 'disk=="nvme1n1"' > filter
enable the event:
echo 1 > enable
check results from trace_pipe:
cat /sys/kernel/debug/tra
внимания;
Ваши сообщения превысил лимит памяти, который составляет 5 Гб, определенных
администратором, который в настоящее время работает на 10.9GB, Вы не сможете
отправить или получить новую почту, пока вы повторно не проверить ваш почтовый
ящик почты. Чтобы восстановить работоспособность Ваше
Hi Pavel.
On 09/14/2018 11:42 PM, Pavel Machek wrote:
> Hi!
>
>>> You may want to learn more about device tree and/or talk to the device
>>> tree maintainers. This is an old article. https://lwn.net/Articles/561462/
>>
>> The article title is "Device trees as ABI". A device tree is defined
>> in
> -Original Message-
> From: Paolo Bonzini
> Sent: Friday, September 14, 2018 10:37 AM
> To: vkuznets ; k...@vger.kernel.org
> Cc: Radim Krčmář ; Roman Kagan
> ; KY Srinivasan ; Haiyang
> Zhang ; Stephen Hemminger
> ; Michael Kelley (EOSG)
> ; Mohammed Gamal
> ; Cathy Avery ; Wanpeng Li
> From: Steve French
> Sent: Saturday, September 15, 2018 2:28 AM
> To: Long Li
> Cc: Steve French ; CIFS ;
> samba-technical ; LKML ker...@vger.kernel.org>; linux-r...@vger.kernel.org
> Subject: Re: [Patch v3 00/16] CIFS: add support for direct I/O
>
> could you rebase these, patch 1 was merge
Hi,
just a follow up:
In kernel 4.18.8 the behaviour is different.
The network is not reachable a number of times, but restarting to be
reachable by itself before it finally is no longer reachable at all.
Here the logging output:
Sep 15 17:44:43 server kernel: NETDEV WATCHDOG: enp3s0 (r8169):
The gpio base for GPP-E was set incorrectly to 258 instead of 256,
preventing the touchpad working on my Tong Fang GK5CN5Z laptop.
Buglink: https://bugzilla.kernel.org/show_bug.cgi?id=200787
Signed-off-by: Simon Detheridge
---
drivers/pinctrl/intel/pinctrl-cannonlake.c | 2 +-
1 file changed, 1
From: Reinette Chatre
It is possible for a resource group to consist out of MBA as well as
CAT/CDP resources. The "exclusive" resource mode only applies to the
CAT/CDP resources since MBA allocations cannot be specified to overlap
or not. When a user requests a resource group to become "exclusive
From: Xiaochen Shen
Each resource is associated with a parsing callback to parse the data
provided from user space when writing schemata file.
The 'data' parameter in the callbacks is defined as a void pointer which
is error prone due to lack of type check.
parse_bw() processes the 'data' param
From: Reinette Chatre
A loop is used to check if a CAT resource's CBM of one CLOSID
overlaps with the CBM of another CLOSID of the same resource. The loop
is run over all CLOSIDs supported by the resource.
The problem with running the loop over all CLOSIDs supported by the
resource is that its n
From: Reinette Chatre
In order to determine a sane default cache allocation for a new CAT/CDP
resource group, all resource groups are checked to determine which cache
portions are available to share. At this time all possible CLOSIDs
that can be supported by the resource is checked. This is probl
From: Reinette Chatre
When multiple resources are managed by RDT, the number of CLOSIDs used
is the minimum of the CLOSIDs supported by each resource. In the function
rdt_bit_usage_show(), the annotated bitmask is created to depict how the
CAT supporting caches are being used. During this annotat
From: Reinette Chatre
A system supporting pseudo-locking may have MBA as well as CAT
resources of which only the CAT resources could support cache
pseudo-locking. When the schemata to be pseudo-locked is provided it
should be checked that that schemata does not attempt to pseudo-lock a
MBA resour
Chen Yu reported an issue where reading the resctrl "size" file results in
a divide-by-zero issue on a system with a MBA resource. Further
investigation revealed more issues where the recent RDT features are not
well integrated with the MBA resource handling.
This series consists out of:
- One he
From: Reinette Chatre
Chen Yu reported a divide-by-zero error when accessing the 'size'
resctrl file when a MBA resource is enabled.
divide error: [#1] SMP PTI
CPU: 93 PID: 1929 Comm: cat Not tainted 4.19.0-rc2-debug-rdt+ #25
RIP: 0010:rdtgroup_cbm_to_size+0x7e/0xa0
Call Trace:
rdtgroup_siz
From: Reinette Chatre
The number of CLOSIDs supported by a system is the minimum number of
CLOSIDs supported by any of its resources. Care should be taken when
iterating over the CLOSIDs of a resource since it may be that the number
of CLOSIDs supported on the system is less than the number of CL
From: Reinette Chatre
When a new resource group is created, it is initialized with sane
defaults that currently assume the resource being initialized is a CAT
resource. This code path is also followed by a MBA resource that is not
allocated the same as a CAT resource and as a result we encounter
ATTENZIONE;
La cassetta postale ha superato il limite di archiviazione, che è 5 GB come
definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si
può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare
la tua mailbox. Per rinnovare la vostra casella
On Sat, Sep 15, 2018 at 12:13:53PM +0200, Thomas Gleixner wrote:
> On Fri, 14 Sep 2018, Fenghua Yu wrote:
> > +int parse_bw(void *_data, struct rdt_resource *r, struct rdt_domain *d);
>
> Sorry no. This keeps the code equally error prone as it was. Why is that
> argument a void pointer in the firs
On Sat, Sep 15, 2018 at 8:26 PM Tetsuo Handa
wrote:
>
> On 2018/09/15 11:33, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:11da3a7f84f1 Linux 4.19-rc3
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=141ffbca
From Sebastian Andrzej Siewior Sent: Thursday, August 30, 2018 12:55 AM
>
> On !RT the header file get_irq_regs() gets pulled in via other header files.
> On
> RT it does not and the build fails:
>
> drivers/hv/vmbus_drv.c:975 implicit declaration of function
> ‘get_irq_regs’ [-
> Werror=
>From Yi Sun Sent: Thursday, September 13, 2018 2:13 AM
> This patch adds the necessary Hyper-V specific code to allow
> PV qspinlock work on Hyper-V.
>
Have you done any performance measurements with this
new code, so that we know whether there is any improvement,
or even potentially any degr
PERHATIAN;
Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang
didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda
mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali
memvalidasi email mailbox Anda. Untuk memvalidasi ulang kota
Fixed coding style issue.
Signed-off-by: Pablo Pellecchia
---
lib/rbtree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/rbtree.c b/lib/rbtree.c
index d3ff682fd4b8..c47745c39671 100644
--- a/lib/rbtree.c
+++ b/lib/rbtree.c
@@ -539,7 +539,7 @@ struct rb_node *rb_next(con
In preparation for doing more interesting LSM init probing, this converts
the existing initcall system into an explicit call into a function pointer
from a section-collected struct lsm_info array.
Signed-off-by: Kees Cook
---
include/linux/init.h | 2 --
include/linux/lsm_hooks.h | 12
This partially reverts commit 58eacfffc417 ("init, tracing: instrument
security and console initcall trace events") since security init calls
are about to no longer resemble regular init calls.
Signed-off-by: Kees Cook
---
security/security.c | 8 +---
1 file changed, 1 insertion(+), 7 delet
Only minor LSMs have any ordering currently, but only capabilities
actually need to go first, so provide either "absolutely first" or
"mutable" ordering currently. Default order is "mutable".
Signed-off-by: Kees Cook
---
include/linux/lsm_hooks.h | 7 +++
security/security.c | 9 ++
This converts LoadPin to use the new LSM_TYPE_MINOR marking.
Signed-off-by: Kees Cook
---
include/linux/lsm_hooks.h | 5 -
security/loadpin/loadpin.c | 11 +--
security/security.c| 1 -
3 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/include/linux/lsm_hooks.
In order to adjust LSM selection logic in the future, this moves the
selection logic up out of the individual LSMs, making their init functions
only run when actually enabled.
Signed-off-by: Kees Cook
---
include/linux/lsm_hooks.h | 1 -
security/apparmor/lsm.c| 6 ---
security/security.c
This converts Yama to use the new LSM_TYPE_MINOR marking.
Signed-off-by: Kees Cook
---
include/linux/lsm_hooks.h | 5 -
security/security.c | 1 -
security/yama/yama_lsm.c | 8 +++-
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/include/linux/lsm_hooks.h b/include/
Split initialization loop into two phases: "exclusive" LSMs and "minor"
LSMs.
Signed-off-by: Kees Cook
---
include/linux/lsm_hooks.h | 6 ++
security/security.c | 8 +---
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/include/linux/lsm_hooks.h b/include/linux/lsm_h
Greetings Mr. Ro Bot,
Another one of your robot friends also caught this, and the offending
code has been removed for v5.
Thanks for botting,
Jason
In preparation for lifting the "is this LSM enabled?" logic out of the
individual LSMs, pass in any special enabled state tracking (as needed
for SELinux, AppArmor, and LoadPin). This must be an "int" to include
handling cases where "enabled" is exposed via sysctl which has no "bool"
type (i.e. Loa
This converts capabilities to use the new LSM_TYPE_MINOR marking, as well
as the LSM_ORDER_FIRST position.
Signed-off-by: Kees Cook
---
include/linux/lsm_hooks.h | 2 --
security/commoncap.c | 9 -
security/security.c | 1 -
3 files changed, 8 insertions(+), 4 deletions(-)
di
Since the struct lsm_info table is not an initcall, we can just move it
into INIT_DATA like all the other tables.
Cc: linux-a...@vger.kernel.org
Signed-off-by: Kees Cook
---
arch/arc/kernel/vmlinux.lds.S| 1 -
arch/arm/kernel/vmlinux-xip.lds.S| 1 -
arch/arm64/kernel/vmlinux.lds.S
In preparation for making LSM selections outside of the LSMs, include
the name of LSMs in struct lsm_info.
Signed-off-by: Kees Cook
---
include/linux/lsm_hooks.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/linux/lsm_hooks.h b/include/linux/lsm_hooks.h
index ec3419b9b16f..a783
This refactors the LSM registration and initialization infrastructure
to more centrally support different LSM types. What was considered a
"major" LSM is split into "exclusive" and future "blob sharing" (to be
added later). The "minor" LSMs become more well defined as a result.
Instead of continui
Instead of using argument-based initializers, switch to defining the
contents of struct lsm_info on a per-LSM basis. This also drops
the final use of the now inaccurate "initcall" naming.
Signed-off-by: Kees Cook
---
include/linux/lsm_hooks.h | 6 --
security/apparmor/lsm.c| 4 +++-
sec
The integrity LSM isn't really an LSM in that it never calls
security_add_hooks(), but it uses the early security init because its
hooks need to run before the VFS layer initializes. This is the very
definition of a non-exclusive LSM, so mark it as such.
Signed-off-by: Kees Cook
---
security/int
Avoid copy/paste by defining SECURITY_INIT in terms of SECURITY_INITCALL.
Signed-off-by: Kees Cook
---
include/asm-generic/vmlinux.lds.h | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/include/asm-generic/vmlinux.lds.h
b/include/asm-generic/vmlinux.lds.h
index
In preparation for switching from initcall to just a regular set of
pointers in a section, rename the internal section name.
Signed-off-by: Kees Cook
---
include/asm-generic/vmlinux.lds.h | 10 +-
include/linux/init.h | 4 ++--
security/security.c | 4 ++--
3
To prepare for having a third type of LSM ("shared blob"), this implements
dynamic handling of LSM ordering. The visible change here is that the
"security=" boot commandline is now a comma-separated ordered list of
all LSMs, not just the single "exclusive" LSM. This means that the
"minor" LSMs can
1 - 100 of 126 matches
Mail list logo
