On Tue, Aug 29, 2017 at 07:58:52AM +0200, Krzysztof Kozlowski wrote:
> On Tue, Aug 29, 2017 at 4:52 AM, Hoegeun Kwon
> wrote:
> > Hi Krzysztof,
> >
> > The driver has been merged into exynos-drm-misc.
> > Could you please check this patch(3/3).
>
> Hi, OK, no problems for me but it is too late f
On Fri, Sep 08, 2017 at 06:40:15PM +0200, Krzysztof Kozlowski wrote:
> On Thu, Sep 07, 2017 at 06:10:00PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > From: Willy Wolff
> >
> > Odroid XU3/4 boards have thermal sensors per 4 pairs of A7+A15
> > cores but currently there is only one thermal-zone (in
On Wed, Aug 30, 2017 at 03:41:18PM +0100, Dietmar Eggemann wrote:
> The following 'capacity-dmips-mhz' dt property values are used:
>
> Cortex-A15: 1024, Cortex-A7: 539
>
> They have been derived from the cpu_efficiency values:
>
> Cortex-A15: 3891, Cortex-A7: 2048
>
> by scaling them so that t
On Sat, 2017-09-09 at 05:57 +1000, James Morris wrote:
> On Fri, 8 Sep 2017, Linus Torvalds wrote:
>
> > Now the whole security pull will be ignored because of this thing. I
> > refuse to pull garbage where I notice major fundamental problems in
> > code that has obviously never ever been tested.
On Wed, Aug 30, 2017 at 03:41:19PM +0100, Dietmar Eggemann wrote:
> The following 'capacity-dmips-mhz' dt property values are used:
>
> Cortex-A15: 1024, Cortex-A7: 539
>
> They have been derived form the cpu_efficiency values:
>
> Cortex-A15: 3891, Cortex-A7: 2048
>
> by scaling them so that t
On 26/07/2017 12:01, Srinivas Kandagatla wrote:
>
> On 18/07/17 05:52, Oleksij Rempel wrote:
>> Hallo all,
>>
>> Here Gentle Ping to the Old King ;)
>>
>> DT is already ACKed.
>
> Thanks for patience, As this is a new driver it will be queued for 4.14 just
> before 4.13-rc5 is released.
>
> thanks
Changes since v3:
- make the naming to be consistent as mtk_pmic or MTK_PMIC
- add suspend/resume functions to enable/disable irq
- change binding properties to define wakeup sources
Changes since v2:
- use standard properties for keycodes and debounce time
- change to use platform_get_irq in leaf
The core driver should create and manage irq mappings instead of
leaf drivers. This patch change to pass irq domain to
devm_mfd_add_devices() and it will create mapping for irq resources
automatically. And remove irq mapping in rtc driver since this has
been done in core driver.
Acked-for-MFD-by:
This patch adds the device tree binding documentation for the MediaTek
pmic keys found on PMIC MT6397/MT6323.
Signed-off-by: Chen Zhong
---
.../devicetree/bindings/input/mtk-pmic-keys.txt| 41
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetre
This patch adds documentation for device tree bindings for keys support
as the subnode of MT6397/MT6323 PMIC.
Acked-by: Rob Herring
Acked-for-MFD-by: Lee Jones
Signed-off-by: Chen Zhong
---
Documentation/devicetree/bindings/mfd/mt6397.txt |6 ++
1 file changed, 6 insertions(+)
diff --
This patch add support to handle MediaTek PMIC MT6397/MT6323 key
interrupts including pwrkey and homekey, also add setting for
long press key shutdown behavior.
Signed-off-by: Chen Zhong
---
drivers/input/keyboard/Kconfig |9 +
drivers/input/keyboard/Makefile|1 +
drivers
This patch adds compatible strings and interrupts for pmic keys
which serves as child device of MFD.
Acked-for-MFD-by: Lee Jones
Signed-off-by: Chen Zhong
---
drivers/mfd/mt6397-core.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/mt639
From: Markus Elfring
Date: Sun, 17 Sep 2017 10:03:45 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Improve three size determinations
drivers/media/tuners/tda18212.c | 13
From: Markus Elfring
Date: Sun, 17 Sep 2017 09:33:58 +0200
* Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
* Add a jump target so that the function "kfree" will be always called
with a non-null pointer.
Sig
From: Markus Elfring
Date: Sun, 17 Sep 2017 09:42:17 +0200
Replace the specification of data structures by variable references
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
Signed-off-by: Markus
Add hi3521a.dtsi and hi3521a-rs-dm290e.dts for RaySharp CCTV systems,
marketed under the name Samsung SDR-B74301N
Signed-off-by: Marty E. Plummer
---
arch/arm/boot/dts/Makefile | 2 +
arch/arm/boot/dts/hi3521a-rs-dm290e.dts | 52 ++
arch/arm/boot/dts/hi3521a.dtsi | 3
Greetings,
I'd like the community's feedback on the following patchset. I've attempted to
split my changes up in what I believe to be a sensible setup.
The device I'm working against is the 'SamsungSV SDR-B74301' HD CCTV
surveillance
system, which uses a Hisilicon Hi3521A arm SoC as its basis.
Enable Hisilicon Hi3521A/Hi3520DCV300 SoC. This SoC series includes
hardware mutlimedia codec cores, commonly used in consumer cctv/dvr
security systems and ipcameras. The arm core is a Cortex A7.
Signed-off-by: Marty E. Plummer
---
arch/arm/mach-hisi/Kconfig | 6 ++
1 file changed, 6 insert
Add CRG driver for Hi3521A SoC. CRG (Clock and Reset Generator) module
generates clock and reset signals used by other module blocks on SoC.
Signed-off-by: Marty E. Plummer
---
drivers/clk/hisilicon/Kconfig | 7 +
drivers/clk/hisilicon/Makefile| 1 +
drivers/clk/hisil
From: Markus Elfring
Date: Sun, 17 Sep 2017 11:11:02 +0200
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Improve a size determination
drivers/media/usb/airspy/airspy.c | 6 ++
From: Markus Elfring
Date: Sun, 17 Sep 2017 11:00:09 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/media/usb/airspy/airspy.c | 4 +---
1 file changed, 1 insertio
From: Markus Elfring
Date: Sun, 17 Sep 2017 11:03:21 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was det
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
A single fix addressing the missing CP8 feature bit in CPUID for a range of
AMD ZEN models/mask revisions.
Thanks,
tglx
On (09/17/17 15:26), Sergey Senozhatsky wrote:
[..]
> > Anyway, it seems that we will need to update all the tools
> > for the different time stamps, see
> > https://lkml.kernel.org/r/1504613201-23868-1-git-send-email-pra...@redhat.com
> > Then we will be more clever how painful it is.
may be we c
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
Fix for an off by one error in a cpumask result comparison.
Thanks,
tglx
-->
Thomas Gleixner (1):
genirq: Fix cpum
Linus,
please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
This update contains:
- A fix for a user space regression in /proc/$PID/stat
- A couple of objtool fixes:
- Plug a memory leak
-
The error handling path at label 'accept_err' already performs these
'sock_release()' and 'mutex_unlock()' calls. The order is reversed, but
it is not important.
So avoid code duplication and 'goto accept_err'.
While at it, add some missing spaces around a '='.
Signed-off-by: Christophe JAILLET
From: Markus Elfring
Date: Sun, 17 Sep 2017 11:40:31 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/media/usb/au0828/au0828-core.c | 4 +---
1 file changed, 1 ins
we can find the logic in domain_dirty_limits() that
when dirty bg_thresh is bigger than dirty thresh,
bg_thresh will be set as thresh * 1 / 2.
if (bg_thresh >= thresh)
bg_thresh = thresh / 2;
But actually we can set dirty_background_raio bigger than
dirty_ratio successfully
The function can return a negativ value in case of errors,
don't use it blindly as array index.
Detected by CoverityScan CID#1418067 ("Memory - illegal accesses")
Fixes: f384b352cbf0 ("mtd: spi-nor: parse Serial Flash Discoverable
Parameters (SFDP) tables")
Signed-off-by: Richard Weinberger
---
When reading data from trace_pipe, tracing_wait_pipe() performs a
check to see if tracing has been turned off after some data was read.
Currently, this check always looks at global trace state, but it
should be checking the trace instance where trace_pipe is located at.
Because of this bug, cat in
Hi Guy,
> Guy Shapiro hat am 17. September 2017 um 09:35
> geschrieben:
>
>
> On 26/07/2017 12:01, Srinivas Kandagatla wrote:
> >
> > On 18/07/17 05:52, Oleksij Rempel wrote:
> >> Hallo all,
> >>
> >> Here Gentle Ping to the Old King ;)
> >>
> >> DT is already ACKed.
> >
> > Thanks for patienc
From: Srinivas Kandagatla
Hi Greg,
snvs nvmem provider driver was missed in first and second set of
nvmem patches, this driver has been acked and reviewed.
Could you please pick this up for 4.14.
Thanks,
srini
Oleksij Rempel (2):
Oleksij Rempel (2):
nvmem: dt: document SNVS LPGPR binding
From: Oleksij Rempel
Documentation bindings for the Low Power General Purpose Register
available on i.MX6 SoCs in the Secure Non-Volatile Storage.
Signed-off-by: Oleksij Rempel
Acked-by: Rob Herring
Signed-off-by: Srinivas Kandagatla
---
.../devicetree/bindings/nvmem/snvs-lpgpr.txt |
From: Oleksij Rempel
This is a driver for Low Power General Purpose Register (LPGPR)
available on i.MX6 SoCs in Secure Non-Volatile Storage (SNVS)
of this chip.
It is a 32-bit read/write register located in the low power domain.
Since LPGPR is located in the battery-backed power domain, LPGPR ca
On 17/09/17 08:35, Guy Shapiro wrote:
On 26/07/2017 12:01, Srinivas Kandagatla wrote:
On 18/07/17 05:52, Oleksij Rempel wrote:
Hallo all,
Here Gentle Ping to the Old King ;)
DT is already ACKed.
Thanks for patience, As this is a new driver it will be queued for 4.14 just
before 4.13-rc5
On (09/15/17 07:29), Mark Salyzyn wrote:
> On 09/15/2017 06:28 AM, Petr Mladek wrote:
> > I am still slightly nervous that external tools would need updating.
> > Also they might have troubles to interpret the time stamps especially
> > when the source is changed at runtime via
> > /sys/module/prin
Modify baycom driver to use the new parallel port device model.
Signed-off-by: Sudip Mukherjee
---
Not tested on real hardware, only tested on qemu and verified that the
device is binding to the driver properly in epp_open but then unbinding
as the device was not found.
drivers/net/hamradio/ba
On Sun, Sep 17, 2017 at 8:04 AM, Eric Biggers wrote:
> This should jump to 'err_enckey', otherwise it will leak 'enckey'.
Yikes, good catch, thanks!
>
> Otherwise the changes all look good; after fixing the above, feel free to add
> my
> Reviewed-by.
Ack.
> Yes, AES-GCM is the right choice he
This started out as just replacing the use of crypto/rng with
get_random_bytes_wait, so that we wouldn't use bad randomness at boot time.
But, upon looking further, it appears that there were even deeper
underlying cryptographic problems, and that this seems to have been
committed with very little
On Fri, Sep 8, 2017 at 5:13 PM, Colin King wrote:
> From: Colin Ian King
>
> The call to kfd_device_by_id can potentially return null, so check that
> dev is null and return with -EINVAL to avoid a null pointer dereference.
>
> Detected by CoverityScan CID#1454629 ("Dereference null return value"
We missed freeing intent and intent->data on error conditions.
Signed-off-by: Sudip Mukherjee
---
drivers/rpmsg/qcom_glink_native.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/rpmsg/qcom_glink_native.c
b/drivers/rpmsg/qcom_glink_native.c
index 5a5e927..2e64c
If delay_drop_debugfs_init() fails in any of the operations to create
debugfs, it is calling delay_drop_debugfs_cleanup() as part of its
cleanup. But delay_drop_debugfs_cleanup() checks for 'dbg' and since
we have not yet pointed 'dbg' to the debugfs we need to cleanup the
cleanup fails and we are
On 9/15/2017 11:08 AM, Arnd Bergmann wrote:
> My recent bug fix introduced another bug, which caused rmem_dma_device_init
> to always fail, as rmem->priv is never set to anything.
>
> This restores the previous behavior, calling dma_init_coherent_memory()
> whenever ->priv is NULL.
>
> Fixes: d35
If 'clk_data' is not allocated we returned but we failed to free 'rtc'.
Signed-off-by: Sudip Mukherjee
---
drivers/rtc/rtc-sun6i.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-sun6i.c b/drivers/rtc/rtc-sun6i.c
index 3d2216c..5bc28ee 100644
--- a/drivers/
On 09/15/2017 01:51 PM, Josef Bacik wrote:
> Finally got access to a box to run this down myself. This patch on top of
> the other patches fixes the problem for me, could you verify it works for
> you? Thanks,
>
Yup I can confirm that patch fixes things when applied on top of the
previous 3 p
From: Markus Elfring
Date: Sun, 17 Sep 2017 15:25:35 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
Use common error handling code in cpia2_usb_probe()
Adjust two function calls together with a variable assignment
Delete unneces
From: Markus Elfring
Date: Sun, 17 Sep 2017 12:40:14 +0200
Add a jump target so that a bit of exception handling can be better reused
at the end of this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/media/usb/cpia2/cpia2_usb.c | 1
From: Markus Elfring
Date: Sun, 17 Sep 2017 12:56:50 +0200
The script "checkpatch.pl" pointed information out like the following.
ERROR: do not use assignment in if condition
Thus fix the affected source code places.
Signed-off-by: Markus Elfring
---
drivers/media/usb/cpia2/cpia2_usb.c | 7 +
2017-09-15 23:03 GMT+02:00 Daniel Lezcano :
> On Thu, Sep 14, 2017 at 09:56:52AM +0200, Benjamin Gaignard wrote:
>> 16 bits timers aren't accurate enough to be used as
>> clocksource, remove them from stm32f4 and stm32f7 devicetree.
>
> Do you really want to remove the description? The timers are d
From: Markus Elfring
Date: Sun, 17 Sep 2017 13:23:47 +0200
The script "checkpatch.pl" pointed information out like the following.
WARNING: kfree(NULL) is safe and this check is probably not required
Thus fix the affected source code place.
Signed-off-by: Markus Elfring
---
drivers/media/usb/
From: Markus Elfring
Date: Sun, 17 Sep 2017 13:32:45 +0200
The script "checkpatch.pl" pointed information out like the following.
WARNING: void function return statements are not generally useful
Thus remove such a statement in the affected function.
Signed-off-by: Markus Elfring
---
drivers
On Sat, 16 Sep 2017, Rob Landley wrote:
> So, I added a workaround with a printk in hopes of embarassing them into
> someday fixing it.
Oh, it will be fixed in Debian alright. I am just waiting the issue to
settle a bit to file the bug reports, or maybe even send in the Debian
patches myself (not
On Sat, Sep 16, 2017 at 07:34:03AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> Provide support for Secure Encrypted Virtualization (SEV). This initial
> support defines a flag that is used by the kernel to determine if it is
> running with SEV active.
>
> Cc: Thomas Gleixner
> Cc: Ingo
On Sat, Sep 16, 2017 at 07:34:04AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> When SEV is active the initrd/initramfs will already have already been
> placed in memory encrypted so do not try to encrypt it.
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: "H. Peter Anvin"
> Cc: Boris
On Sat, Sep 16, 2017 at 07:34:08AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> EFI data is encrypted when the kernel is run under SEV. Update the
> page table references to be sure the EFI memory areas are accessed
> encrypted.
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: "H. Peter
On Sat, Sep 16, 2017 at 07:34:06AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> When Secure Encrypted Virtualization (SEV) is active, boot data (such as
> EFI related data, setup data) is encrypted and needs to be accessed as
> such when mapped. Update the architecture override in early_m
On Sat, Sep 16, 2017 at 07:34:07AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> The current code checks only for sme_active() when determining whether
> to perform the encryption attribute change. Include sev_active() in this
> check so that memory attribute changes can occur under SME a
On Sat, Sep 16, 2017 at 07:34:05AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> When SEV is active the trampoline area will need to be in encrypted
> memory so only mark the area decrypted if SME is active.
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: "H. Peter Anvin"
> Cc: Borisla
On Sat, Sep 16, 2017 at 07:34:09AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> The walk_iomem_res_desc(), walk_system_ram_res() and walk_system_ram_range()
> functions each have much of the same code. Create a new function that
> consolidates the common code from these functions in one
On Sat, Sep 16, 2017 at 07:34:11AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> In order for memory pages to be properly mapped when SEV is active, we
> need to use the PAGE_KERNEL protection attribute as the base protection.
> This will insure that memory mapping of, e.g. ACPI tables, re
On Sat, Sep 16, 2017 at 07:34:12AM -0500, Brijesh Singh wrote:
Add a verb to patch subject:
Subject: x86/mm: Add DMA support for ...
> From: Tom Lendacky
>
> DMA access to encrypted memory cannot be performed when SEV is active.
> In order for DMA to properly work when SEV is active, the SWIOT
Dear Talented,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a
Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story
of
The build of msp71xx_defconfig was failing with the error:
arch/mips/pmcs-msp71xx/msp_smp.c: In function 'msp_vsmp_int_init':
arch/mips/pmcs-msp71xx/msp_smp.c:72:2: error:
implicit declaration of function 'set_vi_handler';
did you mean 'irq_set_handler'? [-Werror=implicit-function-d
header.major is of type u8 and cannot be negative.
Detected by CoverityScan CID#1417858 ("Integer handling issues")
Fixes: f384b352cbf0 ("mtd: spi-nor: parse Serial Flash Discoverable
Parameters (SFDP) tables")
Signed-off-by: Richard Weinberger
---
Cyrille,
I'm not sure what exactly you wanted
The driver would happily accept buswidth of 16/32/64 bytes and program
garbage to its registers.
Signed-off-by: Stefan Brüns
---
drivers/dma/edma.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c
index 3879f80a4815..c944ea339425 100
Linus Torvalds:
> On Wed, Sep 13, 2017 at 11:46 PM, Miklos Szeredi wrote:
> >
> > d_real() is currently is *the* overlayfs-op:
>
> I know. And it's ugly as #%^! hell.
>
> We don't want to make it uglier.
>
> And honestly, if you think that "it's only for overlayfs, so I can do
> anything I damn w
On Sat, Sep 16, 2017 at 07:34:13AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> Early in the boot process, add checks to determine if the kernel is
> running with Secure Encrypted Virtualization (SEV) active.
>
> Checking for SEV requires checking that the kernel is running under a
> hyp
Obviously, the current value for the burst widths are wrong, and if this
value is retrieved from some other subsystem using dma_get_slave_caps,
it will wrongly assume burst width of e.g. 3 bytes are supported.
Each bit in the bitmask corresponds to a supported width, but it uses
an encoding of BIT
Since commit bc6245e5efd7 ("bug: split BUILD_BUG stuff out into
"), #include is better
to pull minumam headers needed for BUILG_BUG() family.
Signed-off-by: Masahiro Yamada
---
include/linux/bitfield.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/bitfield.h
This include was added by commit 187f1882b5b0 ("BUG: headers with
BUG/BUG_ON etc. need linux/bug.h") because BUG_ON() was used in
this header at that time.
Some time later, commit 6d75f366b924 ("lib: radix-tree: check
accounting of existing slot replacement users") removed the use of
BUG_ON() from
checkpatch.pl does not check missing blank line before module_*_driver.
I want it to behave likewise for builtin_*_driver.
Signed-off-by: Masahiro Yamada
---
scripts/checkpatch.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index dd2c262aebb
> Am 16.09.2017 um 15:20 schrieb Jon Maloy .
>>
>> What part of "very time critical" have you verified and benchmarked as
>> inconsequential?
>>
>> Please post your results.
>
> I agree with Joe here. This change does not simplify anything, it does not
> reduce the amount of code, plus that it
Commit 069f0cd00df0 ("printk: Make the printk*once() variants return
a value") surrounded the macro implementation with ({ ... }).
Now, the inner do { ... } while (0); is redundant.
Signed-off-by: Masahiro Yamada
---
include/linux/printk.h | 6 ++
1 file changed, 2 insertions(+), 4 deletio
On Sat, Sep 16, 2017 at 07:34:14AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> Secure Encrypted Virtualization (SEV) does not support string I/O, so
> unroll the string I/O operation into a loop operating on one element at
> a time.
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc: "H.
On Sat, Sep 16, 2017 at 11:20:47AM -0700, Linus Torvalds wrote:
> Sure, generic_file_write_iter() does take that lock exclusively, but
> not everybody uses generic_file_write_iter() at all for writing.
>
> For example, xfs still uses that i_rwsem, but for block-aligned writes
> it will only get it
Thanks a lot Arnd,
applied to the dma-mapping tree for 4.14.
Dear Talented,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a
Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story
of
On Sat, Sep 16, 2017 at 07:34:15AM -0500, Brijesh Singh wrote:
> Some KVM-specific custom MSRs share the guest physical address with the
> hypervisor in early boot. When SEV is active, the shared physical address
> must be mapped with memory encryption attribute cleared so that both
> hypervisor an
On Sun, Sep 17, 2017 at 8:17 AM, Christoph Hellwig wrote:
>
> Only for direct I/O, and IMA and direct I/O don't work together.
> From ima_collect_measurement:
>
> if (file->f_flags & O_DIRECT) {
> audit_cause = "failed(directio)";
> r
Fengguang,
it looks like the kernel build robot _only_ tests the actual rc
kernels, and doesn't bisect down where the error started.
Any change that when it notices an error, it would bisect it, like it
does for linux-next?
Linus
On Sat, Sep 16, 2017 at 11:02 PM, kbuild test ro
On Sat, Sep 16, 2017 at 11:26 PM, Sergey Senozhatsky
wrote:
>
> so... I think we don't have to update 'struct printk_log'. we can store
> that "extended data" at the beginning of every message, right after the
> prefix.
No, we really can't. That just means that all the tools would have to
be chan
On Sun, Sep 17, 2017 at 08:28:40AM -0700, Linus Torvalds wrote:
> The issue is that somebody else can come in - using direct IO - at the
> same time as the first person is collecting measurements, and thus
> race with the collector.
>
> So now the measurements are not trustworthy any more.
Yes. A
On Mon, Apr 24, 2017 at 06:39:28PM +0300, Cyrill Gorcunov wrote:
> With current epoll architecture target files are addressed
> with file_struct and file descriptor number, where the last
> is not unique. Moreover files can be transferred from another
> process via unix socket, added into queue and
This fixes a 32-bit boot warning, a 32-bit boot oddity that seems
unsymtomatic right now, and a potential userspace corruption issue
across EFI calls if PCID is enabled.
With this series applied, the only remaining issue I'm aware of is
the paging-structure cache laziness problem.
I've tested SMP
Putting the logical ASID into CR3's PCID bits directly means that we
have two cases to consider separately: ASID == 0 and ASID != 0.
This means that bugs that only hit in one of these cases trigger
nondeterministically.
There were some bugs like this in the past, and I think there's
still one in c
For unknown historical reasons (i.e. Borislav doesn't recall),
32-bit kernels invoke cpu_init() on secondary CPUs with
intiial_page_table loaded into CR3. Then they set
current->active_mm to &init_mm and call enter_lazy_tlb() before
fixing CR3. This means that the x86 TLB code gets invoked while
Otherwise we might have the PCID feature bit set during cpu_init().
This is just for robustness. I haven't seen any actual bugs here.
Fixes: cba4671af755 ("x86/mm: Disable PCID on 32-bit kernels")
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/cpu/bugs.c | 8
arch/x86/kernel/cpu
Current, the code that assembles a value to load into CR3 is
open-coded everywhere. Factor it out into helpers build_cr3() and
build_cr3_noflush().
This makes one semantic change: __get_current_cr3_fast() was wrong
on SME systems. No one noticed because the only caller is in the
VMX code, and th
On Sun, 2017-09-17 at 08:28 -0700, Linus Torvalds wrote:
> On Sun, Sep 17, 2017 at 8:17 AM, Christoph Hellwig wrote:
> >
> > Only for direct I/O, and IMA and direct I/O don't work together.
> > From ima_collect_measurement:
> >
> > if (file->f_flags & O_DIRECT) {
> >
> -Original Message-
> From: Thomas Meyer [mailto:tho...@m3y3r.de]
> Sent: Sunday, September 17, 2017 11:00
> To: Jon Maloy
> Cc: Joe Perches ; Ying Xue ;
> net...@vger.kernel.org; tipc-discuss...@lists.sourceforge.net; linux-
> ker...@vger.kernel.org; da...@davemloft.net
> Subject: Re:
On Sun, Sep 17, 2017 at 9:15 AM, Mimi Zohar wrote:
>
> Unless I'm missing something, that would only be possible with an IMA
> policy rule that permits direct IO (eg. permit_directio). Otherwise
> the direct IO is denied.
Note that the "XFS and directio" was only an example.
There is absolutely
On Sun, Sep 17, 2017 at 09:34:01AM -0700, Linus Torvalds wrote:
> Now, I suspect most (all?) do, but that's a historical artifact rather
> than "design". In particular, the VFS layer used to do the locking for
> the filesystems, to guarantee the POSIX requirements (POSIX requires
> that writes be s
On 09/16/2017 12:30 AM, Dmitry Torokhov wrote:
> On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski
> wrote:
>> On 09/15/2017 08:34 PM, Dmitry Torokhov wrote:
>>> On Thu, Sep 14, 2017 at 1:58 PM, Pavel Machek wrote:
On Thu 2017-09-14 21:31:31, Jacek Anaszewski wrote:
> Hi David and Pavel,
Hi,
On 09/16/2017 03:58 AM, Pavel Machek wrote:
> Hi!
>
>> These patch series add the LED_BRIGHTNESS_FAST flag support for
>> ledtrig-transient to use hrtimer so that platforms with high-resolution
>> timer
>> support can have better accuracy in the trigger duration timing. The
fs/ubifs/tnc.c: In function ‘search_dh_cookie’:
fs/ubifs/tnc.c:1893: warning: ‘err’ is used uninitialized in this function
Indeed, err is always used uninitialized.
According to an original review comment from Hyunchul, acknowledged by
Richard, err should be initialized to -ENOENT to avoid the fi
On Thu, Sep 14, 2017 at 10:46:37PM -0700, h...@zytor.com wrote:
> On September 14, 2017 10:31:55 PM PDT, Ingo Molnar wrote:
> >
> >* Andy Lutomirski wrote:
> >
> >> >> > diff --git a/arch/x86/entry/entry_64.S
> >b/arch/x86/entry/entry_64.S
> >> >> > index 4916725..3bab6af 100644
> >> >> > --- a/a
Below is the list of build error/warning regressions/improvements in
v4.14-rc1[1] compared to v4.13[2].
Summarized:
- build errors: +7/-0
- build warnings: +1099/-6353
Happy fixing! ;-)
Thanks to the linux-next team for providing the build service.
[1]
http://kisskb.ellerman.id.au/kisskb/h
On Sat, 2017-09-16 at 23:42 -0700, Joel Fernandes wrote:
>
> Yes I understand. However with my 'strong sync' patch, such a
> balancing check could be useful which is what I was trying to do in a
> different way in my patch - but it could be that my way is not good
> enough and potentially the old
Am Sonntag, 17. September 2017, 10:32:20 CEST schrieb Geert Uytterhoeven:
> fs/ubifs/tnc.c: In function ‘search_dh_cookie’:
> fs/ubifs/tnc.c:1893: warning: ‘err’ is used uninitialized in this function
>
> Indeed, err is always used uninitialized.
>
> According to an original review comment from H
1 - 100 of 292 matches
Mail list logo
