Hello Stephen, Mark & All,
On Tue, Oct 02, 2018 at 04:25:51PM +1000, Stephen Rothwell wrote:
> On Tue, 2 Oct 2018 09:16:44 +0300 Matti Vaittinen
> wrote:
> >
> > On Tue, Oct 02, 2018 at 01:07:48PM +1000, Stephen Rothwell wrote:
> > > After merging the regulator tree, today's linux-next build (x8
Alexey,
On Mon, 1 Oct 2018, Alexey Budankov wrote:
> > perf_event_open() knows which PMU is associated with the event the caller
> > tries to open. So perf_event_open() can try to access/open the special per
> > PMU file on behalf of the caller. That should get the same security
> > treatment like
Hi Matthew,
Today's linux-next merge of the xarray tree got a conflict in:
fs/dax.c
between commit:
f52afc93cd01 ("dax: Fix deadlock in dax_lock_mapping_entry()")
from Linus' tree and commit:
a31521132da6 ("dax: Convert dax_lock_mapping_entry to XArray")
from the xarray tree.
I fixed
On (10/01/18 20:21), Tetsuo Handa wrote:
> >> Because there is no guarantee that memory information is dumped under the
> >> oom_lock mutex. The oom_lock is held when calling out_of_memory(), and it
> >> cannot be held when reporting GFP_ATOMIC memory allocation failures.
> >
> > IOW, static pr_li
On Fri, Sep 21, 2018 at 02:02:26PM +0200, Sebastian Andrzej Siewior wrote:
> This matches Daniel Wagner's observations which he described in [0] on
> v4.4-RT.
Peter Z recommended to drop to ticket spinlocks instead trying to port
back all the qspinlock changes to v4.4-rt.
With ticket spinlocks, '
Commit-ID: 715bd9d12f84d8f5cc8ad21d888f9bc304a8eb0b
Gitweb: https://git.kernel.org/tip/715bd9d12f84d8f5cc8ad21d888f9bc304a8eb0b
Author: Andy Lutomirski
AuthorDate: Mon, 1 Oct 2018 12:52:15 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 2 Oct 2018 08:28:15 +0200
x86/vdso: Fix asm con
Commit-ID: 7c03e7035ac1cf2a6165754e4f3a49c2f1977838
Gitweb: https://git.kernel.org/tip/7c03e7035ac1cf2a6165754e4f3a49c2f1977838
Author: Andy Lutomirski
AuthorDate: Mon, 1 Oct 2018 12:52:16 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 2 Oct 2018 08:28:32 +0200
selftests/x86: Add cl
Hi Daniel,
Today's linux-next merge of the cisco tree got a conflict in:
arch/x86/kernel/setup.c
between commit:
dcf8001d292b ("vfs: Suppress MS_* flag defs within the kernel unless
explicitly enabled")
from the vfs tree and commit:
2c070709ea75 ("This updates the x86 code to use the C
Hi Matti,
On Tue, 2 Oct 2018 09:16:44 +0300 Matti Vaittinen
wrote:
>
> On Tue, Oct 02, 2018 at 01:07:48PM +1000, Stephen Rothwell wrote:
> > After merging the regulator tree, today's linux-next build (x86_64
> > allmodconfig) produced this warning:
> >
> > drivers/mfd/rohm-bd718x7.c: In functio
On Mon, 1 Oct 2018, Mike Travis wrote:
I'm not sure what a 'community TSC adjust breakage' means.
On Mon, 1 Oct 2018, Mike Travis wrote:
> Fix regression introduced by
>
> commit cf7a63ef4e02 ("x86/tsc: Calibrate tsc only once")
>
> as it changed setup_arch() so that it now calls tsc_early_init() before
> acpi_boot_table_init() which is a necessary step, in the case of UV
> systems, to infor
On Mon, 1 Oct 2018, Mike Travis wrote:
> Introduce is_early_uv_system() which uses efi.uv_systab to decide early
> in the boot process whether we're on a UV system.
>
> This is needed to skip other early setup/init code that might break UV
> platform if done too early such as before necessary ACP
On Mon, 1 Oct 2018, Andrey Vagin wrote:
> On Mon, Oct 01, 2018 at 11:15:32AM +0200, Eric W. Biederman wrote:
> >
> > In the context of process migration there is a simpler subproblem that I
> > think it is worth exploring if we can do something about.
> >
> > For a cluster of machines all running
Hello All,
On Tue, Oct 02, 2018 at 01:07:48PM +1000, Stephen Rothwell wrote:
> After merging the regulator tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/mfd/rohm-bd718x7.c: In function 'bd718xx_i2c_probe':
> drivers/mfd/rohm-bd718x7.c:101:23: warning: c
On Mon, 1 Oct 2018, Andrey Vagin wrote:
> On Thu, Sep 27, 2018 at 11:41:49PM +0200, Thomas Gleixner wrote:
> > On Thu, 27 Sep 2018, Thomas Gleixner wrote:
> > > Add time skew via NTP/PTP into the picture and you might have to adjust
> > > timers as well, because you need to guarantee that they are
by jd ( 1658 ) <`imipak' `at' `yahoo.com'> on Saturday September 29,
2018 @02:38PM (#57395698) Homepage Journal
The author has no right granted by the GPL to revoke the freedoms of
others. Indeed, the GPL is explicit. Nobody, not even the author, can
remove the freedom of another.
You're com
Commit-ID: 77ac1c02d9f20a0d72fa992c88b98c15d087dbca
Gitweb: https://git.kernel.org/tip/77ac1c02d9f20a0d72fa992c88b98c15d087dbca
Author: Ard Biesheuvel
AuthorDate: Mon, 1 Oct 2018 10:13:24 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 2 Oct 2018 08:08:18 +0200
jump_label: Fix NULL d
Commit-ID: 57d15877033e44e9ac283b8c6e82cc67bf6a0aa6
Gitweb: https://git.kernel.org/tip/57d15877033e44e9ac283b8c6e82cc67bf6a0aa6
Author: Ard Biesheuvel
AuthorDate: Sun, 30 Sep 2018 18:49:50 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 2 Oct 2018 08:08:08 +0200
s390/vmlinux.lds: Mov
find_lock_lowest_rq may or not releease rq lock, but it is fuzzy.
If not releasing rq lock, it is unnecessary to re-call
pick_next_oushable_task.
Signed-off-by: Peng Hao
---
kernel/sched/rt.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
index 2
On Mon 01-10-18 19:59:39, jun qian wrote:
> Header and the corresponding information is not aligned,
> adjust the printing format helps us to understand the slabinfo better.
What prevents you from formating the output when printint the file? In
other words why do we want to do special formating in
On (09/30/18 00:45), zhe...@windriver.com wrote:
> From: He Zhe
>
> Give explicit error for users who want to use larger log buffer.
>
> Signed-off-by: He Zhe
> Cc: pmla...@suse.com
> Cc: sergey.senozhat...@gmail.com
> Cc: rost...@goodmis.org
Suggested-by: Sergey Senozhatsky
So people will kn
On (09/30/18 00:45), zhe...@windriver.com wrote:
> From: He Zhe
>
> Add KBUILD_MODNAME to make prints more clear.
>
> Signed-off-by: He Zhe
> Cc: pmla...@suse.com
> Cc: sergey.senozhat...@gmail.com
> Cc: rost...@goodmis.org
Reviewed-by: Sergey Senozhatsky
-ss
On (09/30/18 00:45), zhe...@windriver.com wrote:
> Correct wrong casting that might cut off the normal output.
A commit message probably could have been a bit more descriptive,
mentioning that log_first_seq and console_seq are 64-bit unsigned
integers, this is a Cc material potentially.
> Signed-
On 1 October 2018 at 22:25, Heiko Carstens wrote:
> On Sun, Sep 30, 2018 at 06:49:50PM +0200, Ard Biesheuvel wrote:
>> Commit e872267b8bcbb179 ("jump_table: move entries into ro_after_init
>> region") moved the __jump_table input section into the __ro_after_init
>> output section, but inadvertentl
On (09/30/18 00:45), zhe...@windriver.com wrote:
>
> This patch adds a check to prevent the panic.
>
> Signed-off-by: He Zhe
> Cc: sta...@vger.kernel.org
> Cc: pmla...@suse.com
> Cc: sergey.senozhat...@gmail.com
> Cc: rost...@goodmis.org
Reviewed-by: Sergey Senozhatsky
-ss
On Mon, Oct 01, 2018 at 11:14:14AM +0200, Daniel Lezcano wrote:
> On 01/10/2018 03:35, Guo Ren wrote:
> > This timer is used by SMP system and use mfcr/mtcr instruction
> > to access the regs.
> >
> > Changelog:
> > - Remove #define CPUHP_AP_CSKY_TIMER_STARTING
> > - Add CPUHP_AP_CSKY_TIMER_STAR
On 2 October 2018 at 05:53, Jason A. Donenfeld wrote:
> Hi Arnd,
>
> Apologies for the delay in getting back to you. I had some MTA issues
> and stupidly assumed ARM developers were taking the day off instead...
>
> On Tue, Oct 2, 2018 at 5:33 AM Arnd Bergmann wrote:
>> -arch-$(CONFIG_CPU_32v3)
Changes v1 -> v2: Fix PMU_FORMAT_ATTR as Peter suggested
This patch enables uprobes with reference counter in fd-based uprobe.
Highest 32 bits of perf_event_attr.config is used to stored offset
of the reference count (semaphore).
Format information in /sys/bus/event_source/devices/uprobe/format/
This is fixed with the following patch.
- Ted
>From c4a928ee604e31354c969b461aa9a6171825096a Mon Sep 17 00:00:00 2001
From: Theodore Ts'o
Date: Tue, 2 Oct 2018 01:34:44 -0400
Subject: [PATCH] ext4: fix argument checking in EXT4_IOC_MOVE_EXT
If the
Hi all,
After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/nvmem/lpc18xx_eeprom.c: In function 'lpc18xx_eeprom_remove':
drivers/nvmem/lpc18xx_eeprom.c:258:6: warning: unused variable 'ret'
[-Wunused-variable]
int ret;
^~~
Intr
>
> On Sat, Sep 29, 2018 at 01:30:26AM +0300, Tomas Winkler wrote:
> > Add tpm2_pcr_extend() function to tpm2-cmd.c with signature required
> > by tpm-interface.c. It wraps the original open code implementation.
> > The original original tpm2_pcr_extend() function is renamed to
> > __tpm2_pcr_e
This reverts commit d76c74387e1c978b6c5524a146ab0f3f72206f98.
While commit d76c74387e1c ("serial: 8250_dw: Fix runtime PM handling")
fixes runtime PM handling when using kgdb, it introduces a traceback for
everyone else.
BUG: sleeping function called from invalid context at
/mnt/host/sou
TIMER_INTR_MASK register (Base Address of Timer + 0x38) is not designed
for masking interrupts on ast2500 chips, and it's not even listed in
ast2400 datasheet, so it's not safe to access TIMER_INTR_MASK on aspeed
chips.
Similarly, TIMER_INTR_STATE register (Base Address of Timer + 0x34) is
not inte
Hi Russell,
> On 1 October 2018 at 19:56, Russell King - ARM Linux
> wrote:
> We could argue that the ARMv3 assembly files are now stable, so the
> chances of ldrh/strh being introduced is low, which would make this
> change tolerable, but the commit message needs to spell out that
> we lose thi
On Mon 01 Oct 02:55 PDT 2018, Niklas Cassel wrote:
> The help text is visible in menuconfig, however QCOM_QMI_HELPERS is a
> hidden kconfig, so it is not selectable in menuconfig.
>
> Remove the help text so that it is more clear that this is intentionally
> a hidden kconfig.
>
> Signed-off-by:
On Mon 01 Oct 03:11 PDT 2018, Niklas Cassel wrote:
> QCOM_QMI_HELPERS is a hidden kconfig, so the proper usage is
> to select it, not depend upon it.
>
> Signed-off-by: Niklas Cassel
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
> ---
> drivers/slimbus/Kconfig | 2 +-
> 1 file changed, 1 inse
Hi Ard,
On Tue, Oct 2, 2018 at 5:54 AM Ard Biesheuvel wrote:
> So Arnd's suggestion to switch to armv3-m would actually be feasible
> then? The code in question does not use ldrh only umull, and so it
> should build with armv3m as well. And we will even generate some
> better code for RiscPC if w
Hi Arnd,
Apologies for the delay in getting back to you. I had some MTA issues
and stupidly assumed ARM developers were taking the day off instead...
On Tue, Oct 2, 2018 at 5:33 AM Arnd Bergmann wrote:
> -arch-$(CONFIG_CPU_32v3)=-D__LINUX_ARM_ARCH__=3 -march=armv3
> +arch-$(CONFI
On Mon 01 Oct 14:49 PDT 2018, Stephen Boyd wrote:
> This code needs to select function #0, which is the first int in the
> array of functions, not the number 0 which may or may not be the
> function for "GPIO mode" per the enum mapping. We were getting lucky on
> SDM845, where this was tested, bec
On Mon, Oct 01, 2018 at 06:20:11PM -0700, Joel Fernandes wrote:
> From: "Joel Fernandes (Google)"
>
> synchronize_rcu_mult is now obsolete since all the different RCU flavors
> have been consolidated and the API is now common on the updater side.
> sched/core.c is the only user of it. All call_rc
Hello my dear.
Did you receive my email message to you? Please, get back to me ASAP as the
matter is becoming late. Expecting your urgent response.
Sean Kim.
Hi Rob,
Today's linux-next merge of the devicetree tree got a conflict in:
drivers/soc/qcom/apr.c
between commit:
4fadb26574cb ("soc: qcom: apr: Avoid string overflow")
from the qcom tree and commit:
b2efb5b04591 ("soc: Convert to using %pOFn instead of device_node.name")
from the devi
On Tue, Oct 2, 2018 at 8:45 AM Atish Patra wrote:
>
> On 9/28/18 11:26 PM, Anup Patel wrote:
> > This patch provides arch_show_interrupts() implementation to
> > show IPI stats via /proc/interrupts.
> >
> > Now the contents of /proc/interrupts" will look like below:
> > CPU0 CPU1
On 9/28/18 11:26 PM, Anup Patel wrote:
This patch provides arch_show_interrupts() implementation to
show IPI stats via /proc/interrupts.
Now the contents of /proc/interrupts" will look like below:
CPU0 CPU1 CPU2 CPU3
8: 17 7 6 14
Hi all,
After merging the regulator tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/mfd/rohm-bd718x7.c: In function 'bd718xx_i2c_probe':
drivers/mfd/rohm-bd718x7.c:101:23: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
bd718x
Header and the corresponding information is not aligned,
adjust the printing format helps us to understand the slabinfo better.
Signed-off-by: jun qian
Cc: Barry song <21cn...@gmail.com>
---
mm/slab_common.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/mm
Since 5c2992ee7fd8a29 ("printk: remove console flushing special
cases for partial buffered lines") we don't print cont fragments
to the consoles; cont lines are now proper log_buf entries and
there is no "consecutive continuation flag" anymore: we either
have 'c' entries that mark continuation line
We have a proper 'overflow' check which tells us that we need to
split up existing cont buffer in separate records:
if (cont.len + len > sizeof(cont.buf))
cont_flush();
At the same time we also have one extra flush: "if cont buffer is
80% full then split it up" in cont_add
From: Sergey Senozhatsky
Prior to 5c2992ee7fd8a29 ("printk: remove console flushing special
cases for partial buffered lines") we would do console_cont_flush()
for each pr_cont() to print cont fragments, so console_unlock() would
actually print data:
pr_cont();
console_lock();
Hello,
RFC
Forked from "printk feature for syzbot". Let's have a separate
discussion thread.
A buch of pr_cont tweaks and cleanups, please see commits and
commits' messages for more details.
Sergey Senozhatsky (3):
printk: keep kernel cont support always enabled
On Mon, Oct 01, 2018 at 04:33:10PM +0100, Phillip Potter wrote:
> Modify ufs_set_de_type function in fs/ufs/util.h to use a lookup
> table rather than a switch statement, as per the TODO comment.
Brittle, that... Something like fs/ext2/dir.c approach (that is,
#define S_SHIFT 12
static unsigned
We have raised the compiler requirement from time to time.
With commit cafa0010cd51 ("Raise the minimum required gcc version
to 4.6"), the minimum for GCC is 4.6 now.
This flag was added by GCC 4.6, and it is recognized by ICC as well.
It is true that Clang does not support this flag but this com
From: Girish Mahadevan
New driver for Qualcomm QuadSPI(QSPI) controller that is used to
communicate with slaves such as flash memory devices. The QSPI controller
can operate in 2 or 4 wire mode but only supports SPI Mode 0. The
controller can also operate in Single or Dual data rate modes.
Signe
From: Girish Mahadevan
Bindings for Qualcomm Quad SPI used on SoCs such as sdm845.
Signed-off-by: Girish Mahadevan
Signed-off-by: Ryan Case
---
Changes in v5:
- None
Changes in v4:
- Changed qspi@ to spi@ and device@ to flash@ to match Rob's review
Changes in v3:
- Added generic compatible
Fix a breakage caused by enabling early tsc initialization which bypasses
a check that disables the forcing of TSC ADJUST to 0 for chassis 0.
This is common on systems where all the chassis start up asynchronously
so which chassis should have a TSC ADJUST value of 0 is not predictable.
The solut
Fix regression introduced by
commit cf7a63ef4e02 ("x86/tsc: Calibrate tsc only once")
as it changed setup_arch() so that it now calls tsc_early_init() before
acpi_boot_table_init() which is a necessary step, in the case of UV
systems, to inform tsc_sanitize_first_cpu() that we're on a platform
wi
Introduce is_early_uv_system() which uses efi.uv_systab to decide early
in the boot process whether we're on a UV system.
This is needed to skip other early setup/init code that might break UV
platform if done too early such as before necessary ACPI tables parsing
takes place.
Signed-off-by: Mike
Em Mon, 1 Oct 2018 15:43:13 -0700
"Luck, Tony" escreveu:
> Nobody(*) uses them. Dropping this will allow us to make the total
> number of memory controllers configurable (as we won't have to
> worry about duplicated device names under this directory).
>
> (*) https://marc.info/?l=linux-edac&m=1
From: "Joel Fernandes (Google)"
sched/core.c was the only user of synchronize_rcu_mult. It has been
coverted to use synchronize_rcu. So lets remove the synchronize_rcu_mult
implementation entirely.
Signed-off-by: Joel Fernandes (Google)
---
include/linux/rcupdate_wait.h | 17 -
From: "Joel Fernandes (Google)"
synchronize_rcu_mult is now obsolete since all the different RCU flavors
have been consolidated and the API is now common on the updater side.
sched/core.c is the only user of it. All call_rcu_ calls boil
down to the same call_rcu. So there's no point in calling
sy
From: Girish Mahadevan
Bindings for Qualcomm Quad SPI used on SoCs such as sdm845.
Signed-off-by: Girish Mahadevan
Signed-off-by: Ryan Case
---
Changes in v4:
- Changed qspi@ to spi@ and device@ to flash@ to match Rob's review
Changes in v3:
- Added generic compatible string in addition to s
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-pcie-idio-24.c | 102 +++
1 file changed, 36 insertions(+), 66 deletio
From: Girish Mahadevan
New driver for Qualcomm QuadSPI(QSPI) controller that is used to
communicate with slaves such as flash memory devices. The QSPI controller
can operate in 2 or 4 wire mode but only supports SPI Mode 0. The
controller can also operate in Single or Dual data rate modes.
Signe
пн, 1 окт. 2018 г. в 17:59, Rodrigo Freire :
>
> By default, no messages are printed when mounting a CIFS filesystem.
> This information is valuable when troubleshooting and/or forensic
> analyzing a system and finding out if was a CIFS endpoint mount
> attempted.
> Other filesystems such as XFS, E
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-pci-idio-16.c | 67 +++--
1 file changed, 21 insertions(+), 46 deletio
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-ws16c48.c | 66 +
1 file changed, 16 insertions(+), 50 deletio
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-gpio-mm.c | 67 +
1 file changed, 16 insertions(+), 51 deletio
On Mon, Oct 01, 2018 at 05:47:57AM -0700, Christoph Hellwig wrote:
> On Mon, Oct 01, 2018 at 04:11:27PM +1000, Dave Chinner wrote:
> > This reminds me so much of Linux mmap() in the mid-2000s - mmap()
> > worked for ext3 without being aware of page faults,
>
> And "worked" still is a bit of a stre
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-104-idi-48.c | 32
1 file changed, 4 insertions(+), 28 deletions(
Replace verbose implementation in get_multiple/set_multiple callbacks
with for_each_set_clump macro to simplify code and improve clarity.
Signed-off-by: William Breathitt Gray
---
drivers/gpio/gpio-104-dio-48e.c | 67 -
1 file changed, 16 insertions(+), 51 deletio
This macro iterates for each group of bits (clump) with set bits, within
a bitmap memory region. For each iteration, "clump" is set to the found
clump index, "index" is set to the word index of the bitmap containing
the found clump, and "offset" is set to the bit offset of the found
clump within th
The introduction of the for_each_set_clump macro warrants test cases to
verify the implementation. This patch adds test case checks for whether
an out-of-bounds clump index is returned, a zero clump is returned, or
the returned clump value differs from the expected clump value. A 4-bit
clump size i
On Mon, Oct 01, 2018 at 11:32:16AM -0700, Bjorn Andersson wrote:
> On Mon 01 Oct 11:18 PDT 2018, Luis Chamberlain wrote:
>
> > On Mon, Oct 01, 2018 at 03:27:03PM +0200, Niklas Cassel wrote:
> > > On Thu, Sep 20, 2018 at 12:34:15AM -0700, Bjorn Andersson wrote:
> > > > On Wed 19 Sep 22:22 PDT 2018,
On Mon, Oct 01, 2018 at 09:30:35AM +, Kalyani Akula wrote:
> This email and any attachments are intended for the sole use of the named
> recipient(s) and contain(s) confidential information that may be proprietary,
> privileged or copyrighted under applicable law. If you are not the intended
On Mon, Oct 01, 2018 at 06:46:01PM +0100, Will Deacon wrote:
> Hi Greg,
>
> Please pull these late arm64 fixes for 4.19. Details in the tag, but we've
> fixed a hugetlb livelock issue that was reported by Fujitsu as well as
> removing some useless flexibility in our KVM SET_ONE_REG ioctl().
>
> C
On Sun, Sep 30, 2018 at 10:29:07AM -0700, Kees Cook wrote:
> Hi Greg,
>
> Please pull this pstore fix for v4.19-rc7.
>
> Thanks!
>
> -Kees
>
> The following changes since commit 831b624df1b420c8f9281ed1307a8db23afb72df:
>
> pstore: Fix incorrect persistent ram buffer mapping (2018-09-13 09:1
On Sun, Sep 30, 2018 at 12:23:43PM -0700, Olof Johansson wrote:
> Hi Linus, Greg,
>
> The following changes since commit a132bb90414bfad4f8ee23cb45fe6946a89b167d:
>
> Merge tag 'sunxi-fixes-for-4.19' of
> https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux into fixes
> (2018-09-08 10:
This is a resend of v4 in hopes of getting some more ACKS and a few more
eyes on this patchset.
Changes in v4:
- Fix bitmap_set arguments (last parameter is nbits not endbit)
While adding GPIO get_multiple/set_multiple callback support for various
drivers, I noticed a pattern of looping manifes
On Mon, Oct 01, 2018 at 07:14:06PM +0900, Chanwoo Choi wrote:
> Dear Greg,
>
> This is extcon-next pull request for v4.20. I add detailed description of
> this pull request on below. Please pull extcon with following updates.
Now merged, thanks.
greg k-h
On Mon, Oct 01, 2018 at 03:49:12PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the pull request for 4.20 merge window below. It adds PHY
> drivers for Socionext's PCIe PHY, USB2 PHY and USB3 PHY, Rockchip HDMI PHY
> and Cadence display port PHY. Patches to add Qualcomm UFS PHY
Fix a problem with commit 311ee9c151ad ("rtc: cmos: allow using ACPI for
RTC alarm instead of HPET") defining `use_acpi_alarm' module parameter
even for non-ACPI platforms, which ignore it. Wrap the definition into
#ifdef CONFIG_ACPI and use a static inline wrapper function, hardcoded
to retur
Fix a commit 311ee9c151ad ("rtc: cmos: allow using ACPI for RTC alarm
instead of HPET") `rtc-cmos' regression causing a link error:
drivers/rtc/rtc-cmos.o: In function `cmos_platform_probe':
rtc-cmos.c:(.init.text+0x33c): undefined reference to `hpet_rtc_interrupt'
rtc-cmos.c:(.init.text+0x3f4):
Hi,
This mini patch series fixes issues introduced recently for non-ACPI
platforms using `rtc-cmos'. Please see individual change descriptions for
details.
These have been run-time verified with the DECstation (arch/mips/dec).
Please apply.
Maciej
By default, no messages are printed when mounting a CIFS filesystem.
This information is valuable when troubleshooting and/or forensic
analyzing a system and finding out if was a CIFS endpoint mount
attempted.
Other filesystems such as XFS, EXT* does issue a printk() when mounting
their filesystems
On Sat, Sep 29, 2018 at 01:30:35AM +0300, Tomas Winkler wrote:
> The TPM specs defines PCR index as a positive number, and there is
> no reason to use a signed number. It is also a possible security
> issue as currently no functions check for a negative index,
> which may become a large number when
v4:
- add Reviewed-bys.
- cosmetic tweaks.
- New patches to fully centralize LSM "enable" decisions:
LSM: Finalize centralized LSM enabling logic
apparmor: Remove boot parameter
selinux: Remove boot parameter
v3:
- add CONFIG_LSM_ENABLE and refactor resulting logic
v2:
- add "lsm.orde
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
Reviewed-by: Casey Schaufler
Reviewed-by: James Morris
Reviewed-by: John
On Sat, Sep 29, 2018 at 01:30:27AM +0300, Tomas Winkler wrote:
> Add wrapper tpm_auto_startup() to tpm-interface.c
> instead of open coded decision between TPM 1.x and TPM 2.x
> in tpm-chip.c
>
> Signed-off-by: Tomas Winkler
> Tested-by: Jarkko Sakkinen
Reviewed-by: Jarkko Sakkinen
/Jarkko
LoadPin's "enable" setting is really about enforcement, not whether
or not the LSM is using LSM hooks. Instead, split this out so that LSM
enabling can be logically distinct from whether enforcement is happening
(for example, the pinning happens when the LSM is enabled, but the pin
is only checked
On Sat, Sep 29, 2018 at 01:30:26AM +0300, Tomas Winkler wrote:
> Add tpm2_pcr_extend() function to tpm2-cmd.c with signature required
> by tpm-interface.c. It wraps the original open code
> implementation. The original original tpm2_pcr_extend() function
> is renamed to __tpm2_pcr_extend() and made
On Sat, Sep 29, 2018 at 01:30:25AM +0300, Tomas Winkler wrote:
> TPM manual startup is used only from within TPM 1.x or TPM 2.x
> code, hence remove tpm_startup() function from tpm-interface.c
> and add two static functions implementations tpm1_startup()
> and tpm2_startup() into to tpm1-cmd.c and
On Sat, Sep 29, 2018 at 01:30:24AM +0300, Tomas Winkler wrote:
> Factor out TPM 1.x suspend flow from tpm-interface.c into a new function
> tpm1_pm_suspend() in tpm1-cmd.c
>
> Signed-off-by: Tomas Winkler
Reviewed-by: Jarkko Sakkinen
Tested-by: Jarkko Sakkinen
/Jarkko
On Sat, Sep 29, 2018 at 01:30:14AM +0300, Tomas Winkler wrote:
> This patch series provides initial separation of tpm 1.x and tpm 2.x
> commands, in foresight that the tpm 1.x chips will eventually phase out
> and can be compiled out for modern systems.
> A new file is added tpm1-cmd.c that contai
On Sat, Sep 29, 2018 at 01:30:22AM +0300, Tomas Winkler wrote:
> Factor out get random implementation from tpm-interface.c
> into tpm1_get_random function in tpm1-cmd.c.
> No functional changes.
>
> Signed-off-by: Tomas Winkler
> Reviewed-by: Jarkko Sakkine
Reviewed-by: Jarkko Sakkinen
Tested-
On Sat, Sep 29, 2018 at 01:30:20AM +0300, Tomas Winkler wrote:
> Move tpm1_pcr_extend to tpm1-cmd.c and remove
> unused pcrextend_header structure and
> EXTEND_PCR_RESULT_SIZE and EXTEND_PCR_RESULT_BODY_SIZE
> defines.
>
> Fixes warning:
> drivers/char/tpm/tpm-interface.c:609:38: warning: ‘pcrexte
On Sat, Sep 29, 2018 at 01:30:15AM +0300, Tomas Winkler wrote:
> 1. TPM2_CC_LAST has moved from 182 to 193
> 2. Convert tpm2_ordinal_duration from an array into a switch statement,
>as there are not so many commands that require special duration
>relative to a number of commands, the switch
Looks good. Just some minor bits.
On Sat, Sep 29, 2018 at 01:30:15AM +0300, Tomas Winkler wrote:
> 1. TPM2_CC_LAST has moved from 182 to 193
> 2. Convert tpm2_ordinal_duration from an array into a switch statement,
>as there are not so many commands that require special duration
>relative
On Mon, Oct 01, 2018 at 09:42:48PM +, Jethro Beekman wrote:
> 1) Even though the vDSO function exists, userspace may still call
> `ENCLU[EENTER]` manually, so the fault handling as described in the current
> patch should also be maintained.
You mean the way it was is in v13 and not the way it
Hi Bjorn,
After merging the pci tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warning:
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c: In function
'ixgbe_io_slot_reset':
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:11102:6: warning: unused variable
'err' [-Wunused-vari
On Mon, Oct 01, 2018 at 07:29:03AM -0700, Sean Christopherson wrote:
> On Wed, 2018-09-26 at 14:15 -0700, Andy Lutomirski wrote:
> > runs an enclave an returns an error code, and rig up the #PF handler
> > to check if the error happened in the vDSO entry and fix it up rather
> > than sending a sign
1 - 100 of 580 matches
Mail list logo
