On 7/29/20 4:51 PM, Anson Huang wrote:
> Hi, Randy
>
>
>> Subject: Re: [PATCH V7 1/6] clk: imx6sl: Use BIT(x) to avoid shifting signed
>> 32-bit value by 31 bits
>>
>> On 7/29/20 7:48 AM, Anson Huang wrote:
>>> Use readl_relaxed() instead of __raw_readl(), and use BIT(x) instead
>>> of (1 << X) t
Allow IPE to leverage the stacked security blob infrastructure,
and enlighten IPE to the block_device security blob.
This allows IPE to have a property to express rules around a device-mapper
verity volume whose root-hash has been signed, and the signature has been
verified against the system keyr
Add a tool for the generation of an IPE policy to be compiled into the
kernel. This policy will be enforced until userland deploys and activates
a new policy.
Signed-off-by: Deven Bowers
---
MAINTAINERS | 6 ++
scripts/Makefile | 1 +
scripts/ipe/Makefile
Overview:
IPE is a Linux Security Module which allows for a configurable
policy to enforce integrity requirements on the whole system. It
attempts to solve the issue of Code Integrity: that any code being
executed (or files being read), are identical to the ver
Add IPE's documentation to the kernel tree.
Signed-off-by: Deven Bowers
Acked-by: Jonathan Corbet
---
Documentation/admin-guide/LSM/index.rst | 1 +
Documentation/admin-guide/LSM/ipe.rst | 508 ++
.../admin-guide/kernel-parameters.txt | 12 +
MAINTAINERS
Add a security hook call to set a security property of a block_device
in dm-verity with the root-hash that was passed to device-mapper.
Signed-off-by: Deven Bowers
---
drivers/md/dm-verity-target.c | 8
include/linux/device-mapper.h | 1 +
2 files changed, 9 insertions(+)
diff --git a/
Adds the policy parser and the policy loading to IPE, along with the
related securityfs entries and audit events.
Signed-off-by: Deven Bowers
---
security/ipe/Kconfig |2 +
security/ipe/Makefile|3 +
security/ipe/ipe-audit.c | 74 +-
security/ipe/ipe-aud
Remove trailing whitespaces and align the integrity #defines in
linux/uapi/audit.h
Signed-off-by: Deven Bowers
---
include/uapi/linux/audit.h | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/include/uapi/linux/audit.h b/include/uapi/linux/aud
30.07.2020 02:54, Sowjanya Komatineni пишет:
>
> On 7/29/20 4:42 PM, Dmitry Osipenko wrote:
>> 29.07.2020 20:55, Sowjanya Komatineni пишет:
>>> On 7/29/20 10:08 AM, Dmitry Osipenko wrote:
28.07.2020 19:04, Sowjanya Komatineni пишет:
...
>>> +void tegra_mipi_cancel_calibration(struct
Add a property to allow IPE policy to express rules around a specific
root-hash of a dm-verity volume.
This can be used for revocation, (when combined with the previous dm-verity
property) or the authorization of a single dm-verity volume.
Signed-off-by: Deven Bowers
---
security/ipe/ipe-blobs.
Add a property for IPE policy to express trust of the first superblock
where a file would be evaluated to determine trust.
Signed-off-by: Deven Bowers
---
security/ipe/Kconfig| 2 +
security/ipe/Makefile | 4 ++
security/ipe/ipe-engine.c | 4
Add the core logic of the IPE LSM, the evaluation loop (engine),
a portion of the audit system, and the skeleton of the policy
structure.
Signed-off-by: Deven Bowers
---
MAINTAINERS | 1 +
include/uapi/linux/audit.h | 4 +
security/Kconfig | 12 +-
Add a security blob and associated allocation, deallocation and set hooks
for a block_device structure.
Signed-off-by: Deven Bowers
---
fs/block_dev.c| 8
include/linux/fs.h| 1 +
include/linux/lsm_hook_defs.h | 5 +++
include/linux/lsm_hooks.h | 12 ++
Add a security hook call to set a security property of a block_device
in dm-verity with the results of a verified, signed root-hash.
Signed-off-by: Deven Bowers
---
drivers/md/dm-verity-target.c | 2 +-
drivers/md/dm-verity-verify-sig.c | 14 +++---
drivers/md/dm-verity-verify-sig.h
On 7/29/20 5:27 PM, Sowjanya Komatineni wrote:
On 7/29/20 4:59 PM, Sowjanya Komatineni wrote:
On 7/29/20 4:25 PM, Dmitry Osipenko wrote:
28.07.2020 18:59, Sowjanya Komatineni пишет:
...
+ ret = tegra_mipi_finish_calibration(csi_chan->mipi);
+ if (ret < 0)
+ dev_err
30.07.2020 03:27, Sowjanya Komatineni пишет:
...
>>> Secondly, perhaps a failed calibration isn't a very critical error?
>>> Hence just printing a warning message should be enough.
>>
>> Using dev_err to report calibration failure. Are you suggesting to use
>> dev_warn instead of dev_err?
I meant
On 7/29/20 5:43 PM, Dmitry Osipenko wrote:
30.07.2020 03:27, Sowjanya Komatineni пишет:
...
Secondly, perhaps a failed calibration isn't a very critical error?
Hence just printing a warning message should be enough.
Using dev_err to report calibration failure. Are you suggesting to use
dev_wa
On 7/29/20 5:52 PM, Sowjanya Komatineni wrote:
On 7/29/20 5:43 PM, Dmitry Osipenko wrote:
30.07.2020 03:27, Sowjanya Komatineni пишет:
...
Secondly, perhaps a failed calibration isn't a very critical error?
Hence just printing a warning message should be enough.
Using dev_err to report cali
"Rafael J. Wysocki" writes:
> On Wednesday, July 29, 2020 7:46:08 AM CEST Francisco Jerez wrote:
>>
>> --==-=-=
>> Content-Type: multipart/mixed; boundary="=-=-="
>>
>> --=-=-=
>> Content-Type: text/plain; charset=utf-8
>> Content-Disposition: inline
>> Content-Transfer-Encoding: quoted-printab
30.07.2020 03:55, Sowjanya Komatineni пишет:
>
> On 7/29/20 5:52 PM, Sowjanya Komatineni wrote:
>>
>> On 7/29/20 5:43 PM, Dmitry Osipenko wrote:
>>> 30.07.2020 03:27, Sowjanya Komatineni пишет:
>>> ...
>> Secondly, perhaps a failed calibration isn't a very critical error?
>> Hence just pri
On 2020/7/30 6:03, Jakub Kicinski wrote:
> On Wed, 29 Jul 2020 08:59:19 +0800 Luo bin wrote:
>> add support to generate mailbox random id for VF to ensure that
>> the mailbox message from VF is valid and PF should check whether
>> the cmd from VF is supported before passing it to hw.
>
> This is h
On Wed, 29 Jul 2020 at 20:21, Vitaly Kuznetsov wrote:
>
> Wanpeng Li writes:
>
> > From: Wanpeng Li
> >
> > Commit 8566ac8b (KVM: SVM: Implement pause loop exit logic in SVM) drops
> > disable pause loop exit/pause filtering capability completely, I guess it
> > is a merge fault by Radim since d
After 2f96593ecc37 ("of_address: Add bus type match for pci ranges parser"),
the last user of of_bus_pci_get_flags when CONFIG_PCI is disabled had gone.
This caused unused function warning when compiling without CONFIG_PCI.
Fix by guarding it with CONFIG_PCI.
Signed-off-by: Jiaxun Yang
Reported-
Hi Steve,
On Thu, 16 Jul 2020 10:27:03 +0900
Masami Hiramatsu wrote:
> Hi Steve,
>
> On Wed, 15 Jul 2020 20:02:12 -0400
> Steven Rostedt wrote:
>
> > On Thu, 16 Jul 2020 07:38:43 +0900
> > Masami Hiramatsu wrote:
> >
> >
> > > > So the end of the initrd would have:
> > > >
> > > > [data]
Christoph,
I see the same issue on my AMD 3990x using v5.8rc7:
[ 10.229424] bpfilter: Loaded bpfilter_umh pid 1906
[ 10.229467] Started bpfilter
[ 10.229538] pos invalid: -131326014643272
[ 10.229539] bpfilter: write fail -22
[ 10.229603] pos invalid: -2127991714
[ 10.229604] bpfilter
On 7/29/20 5:53 PM, Dmitry Osipenko wrote:
30.07.2020 03:55, Sowjanya Komatineni пишет:
On 7/29/20 5:52 PM, Sowjanya Komatineni wrote:
On 7/29/20 5:43 PM, Dmitry Osipenko wrote:
30.07.2020 03:27, Sowjanya Komatineni пишет:
...
Secondly, perhaps a failed calibration isn't a very critical err
On Wed, Jul 29, 2020 at 06:04:57PM +0300, Andy Shevchenko wrote:
> On Wed, Jul 29, 2020 at 4:35 PM Waiman Long wrote:
> > On 7/29/20 8:28 AM, Herbert Xu wrote:
>
> ...
>
> > This patch series looks good to me. I just wonder if we should also move
> > ATOMIC64_INIT() to types.h for symmetry purpo
On 7/29/20 12:01 PM, Souptick Joarder wrote:
First, when memory allocation for sg_list_unaligned failed, there
is no point of calling put_pages() as we haven't pinned any pages.
Second, if get_user_pages_fast() failed we should unpinned num_pinned
pages, no point of checking till num_pages.
Hi
在 2020/7/29 下午6:31, Stephen Rothwell 写道:
Hi all,
After merging the mips tree, today's linux-next build (powerpc
allnoconfig) produced this warning:
drivers/of/address.c:104:21: warning: 'of_bus_pci_get_flags' defined but not
used [-Wunused-function]
104 | static unsigned int of_bus_pci_g
On Wed, 29 Jul 2020 09:13:21 +0300
Ard Biesheuvel wrote:
> On Wed, 29 Jul 2020 at 04:51, Masami Hiramatsu wrote:
> >
> > On Tue, 28 Jul 2020 20:51:08 +0300
> > Ard Biesheuvel wrote:
> >
> > > On Tue, 28 Jul 2020 at 16:35, Masami Hiramatsu
> > > wrote:
> > > >
> > > > On Tue, 28 Jul 2020 13:56
30.07.2020 04:06, Sowjanya Komatineni пишет:
...
> Will have v6 and add additional patch at the end to do enable/disable
> separately.
>
> Separating this out with additional patch before adding sensor support
> patch requires all patches to be updated.
>
> So I am ok either ways. Please let me k
On July 29, 2020 8:47:36 PM GMT-03:00, Ian Rogers wrote:
>On Fri, Jul 24, 2020 at 3:07 AM Wang ShaoBo
> wrote:
>>
>> Function jvmti_write_code called by compiled_method_load_cb may
>return
>> error in using fwrite_unlocked, this failure should be captured and
>> warned.
>>
>> Signed-off-by: Wan
Hi, Randy
> Subject: Re: [PATCH V7 1/6] clk: imx6sl: Use BIT(x) to avoid shifting signed
> 32-bit value by 31 bits
>
> On 7/29/20 4:51 PM, Anson Huang wrote:
> > Hi, Randy
> >
> >
> >> Subject: Re: [PATCH V7 1/6] clk: imx6sl: Use BIT(x) to avoid shifting
> >> signed 32-bit value by 31 bits
> >>
commit 9dc55f1389f9 ("iomap: add support for sub-pagesize buffered I/O
without buffer heads") replace the per-block structure buffer_head with
the per-page structure iomap_page. However, iomap_page can't track the
dirty state of sub pages, which will cause performance issue since sub
pages will be
HI Maxime,
Any comments on thermal and other patches?
I hope these patches can be integrated into the mainline as soon as possible.
Thx,
Yangtao
Nowdays, there are more and more requirements of building SoC specific drivers
as
modules, such as Android GKI (generic kernel image), this patch set supports
building
i.MX ARMv8 SoCs clock drivers as modules,
The CLK_IMXxxx is introduced for i.MX ARMv7 platforms in order to make the
build opti
Export clk_hw_register_composite() to support user built as module.
ERROR: modpost: "clk_hw_register_composite" [drivers/clk/imx/mxc-clk.ko]
undefined!
Signed-off-by: Anson Huang
Reviewed-by: Stephen Boyd
---
no change.
---
drivers/clk/clk-composite.c | 1 +
1 file changed, 1 insertion(+)
dif
Add CONFIG_CLK_xxx for i.MX ARMv7 platforms, and use it as build option
instead of CONFIG_SOC_xxx, the CONFIG_CLK_xxx will be selected by default
according to CONFIG_SOC_xxx.
Signed-off-by: Anson Huang
Reviewed-by: Dong Aisheng
Reviewed-by: Stephen Boyd
---
no change.
---
drivers/clk/imx/Kconf
Use readl_relaxed() instead of __raw_readl(), and use BIT(x)
instead of (1 << X) to fix below build warning reported by kernel
test robot:
drivers/clk/imx/clk-imx6sl.c:149:49: warning: Shifting signed 32-bit
value by 31 bits is undefined behaviour [shiftTooManyBitsSigned]
while (!(__raw_readl
Hi Joerg,
> On Jul 24, 2020, at 9:02 AM, Joerg Roedel wrote:
>
> From: Joerg Roedel
>
> Hi,
>
> here is a rebased version of the latest SEV-ES patches. They are now
> based on latest tip/master instead of upstream Linux and include the
> necessary changes.
Thanks for the updated patches! I a
There are more and more requirements of building SoC specific drivers
as modules, add support for building i.MX common clock driver as module
to meet the requirement.
Signed-off-by: Anson Huang
Reviewed-by: Stephen Boyd
---
no change.
---
drivers/clk/imx/Kconfig| 8 ++--
driver
Change configuration to "tristate", add module author, description
and license to support building i.MX8M SoCs clock driver as module.
Signed-off-by: Anson Huang
Reviewed-by: Dong Aisheng
Reviewed-by: Stephen Boyd
---
no change.
---
drivers/clk/imx/Kconfig | 16
drivers/c
Change configuration to "tristate", add module author, description and
license to support building i.MX8QXP clock drivers as module.
Signed-off-by: Anson Huang
Reviewed-by: Stephen Boyd
---
no change.
---
drivers/clk/imx/Kconfig| 10 ++
drivers/clk/imx/Makefile |
"Rafael J. Wysocki" writes:
> From: Rafael J. Wysocki
>
> Move the locking away from intel_pstate_set_energy_pref_index()
> into its only caller and drop the (now redundant) return_pref label
> from it.
>
> Also move the "raw" EPP value check into the caller of that function,
> so as to do it be
On Wed, 2020-07-29 at 18:18 +0800, Matthias Brugger wrote:
>
> On 29/07/2020 12:02, Crystal Guo wrote:
> > update mtk-wdt document for MT8192 platform
>
>
> should be two patches. one fixing the compatibles and second adding new board.
>
> >
> > Signed-off-by: Crystal Guo
> > ---
> > Docume
On Mon, Jul 27, 2020 at 10:59:33PM -0700, Andrii Nakryiko wrote:
> On Mon, Jul 27, 2020 at 4:15 PM Roman Gushchin wrote:
> >
> > On Mon, Jul 27, 2020 at 03:05:11PM -0700, Andrii Nakryiko wrote:
> > > On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin wrote:
> > > >
> > > > As bpf is not using memloc
Hi Jiaxun,
On Thu, 30 Jul 2020 09:04:40 +0800 Jiaxun Yang wrote:
>
> Btw: Neither James nor Ralf is still active at Linux-MIPS.
Interesting. I have just them listed as my contacts for MIPS. Should
I change to just Thomes (Thomas Bogendoerfer
)?
--
Cheers,
Stephen Rothwell
pgpZ0vKpdBB_0.pgp
When configuring the IPU for packed YUV 4:2:2, depending on the scaling
ratios given by the source and destination resolutions, it is possible
to crash the IPU block beyond repair, to the point where a software
reset of the IP does not fix it. This can happen anytime, in the first
few frames, or af
Hi,
A few more patches to the ingenic-drm IPU driver.
Patch [1/3] fixes the behaviour on newer SoCs at high resolutions /
framerates.
Patch [2/3] drops YUV 4:2:2 support on the JZ4725B SoC because of what I
think is a hardware bug.
Patch [3/3] makes the IPU clock enabled/disabled when needed.
Instead of keeping the IPU clock enabled constantly, enable and disable
it on demand, when the IPU plane is used.
Signed-off-by: Paul Cercueil
---
drivers/gpu/drm/ingenic/ingenic-ipu.c | 23 ---
1 file changed, 20 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/in
On older SoCs, it is necessary to restart manually the IPU when a frame
is done processing. Doing so on newer SoCs (JZ4760/70) kinds of work
too, until the input or output resolutions or the framerate are too
high.
Make it work properly on newer SoCs by letting the LCD controller
trigger the IPU f
Hi Alex,
On 7/30/20 4:03 AM, Alex Williamson wrote:
On Tue, 14 Jul 2020 13:57:00 +0800
Lu Baolu wrote:
The iommu aux-domain api's work only when IOMMU_DEV_FEAT_AUX is enabled
for the device. Add this check to avoid misuse.
Shouldn't this really be the IOMMU driver's responsibility to test?
On 07/28/20 at 08:11am, Mike Rapoport wrote:
> From: Mike Rapoport
>
> for_each_memblock_type() is not used outside mm/memblock.c, move it there
> from include/linux/memblock.h
>
> ---
> include/linux/memblock.h | 5 -
> mm/memblock.c| 5 +
> 2 files changed, 5 insertions(+)
On 07/28/20 at 08:11am, Mike Rapoport wrote:
> From: Mike Rapoport
>
> The only user of memblock_dbg() outside memblock was s390 setup code and it
> is converted to use pr_debug() instead.
> This allows to stop exposing memblock_debug and memblock_dbg() to the rest
> of the kernel.
>
> Signed-of
Mapping as little as 64GB can take more than 10 seconds,
triggering issues on kernels with CONFIG_PREEMPT_NONE=y.
ib_umem_get() already splits the work in 2MB units on x86_64,
adding a cond_resched() in the long-lasting loop is enough
to solve the issue.
Note that sg_alloc_table() can still use m
在 2020/7/30 上午9:40, Stephen Rothwell 写道:
Hi Jiaxun,
On Thu, 30 Jul 2020 09:04:40 +0800 Jiaxun Yang wrote:
Btw: Neither James nor Ralf is still active at Linux-MIPS.
Interesting. I have just them listed as my contacts for MIPS. Should
I change to just Thomes (Thomas Bogendoerfer
)?
Yes,
Hi, Guenter
> Subject: Re: [PATCH V2 1/2] watchdog: imx7ulp: Strictly follow the sequence
> for wdog operations
>
> On 7/29/20 8:32 AM, Anson Huang wrote:
> > Hi, Guenter
> >
> >
> >> Subject: Re: [PATCH V2 1/2] watchdog: imx7ulp: Strictly follow the
> >> sequence for wdog operations
> >>
> >> O
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: d3590ebf6f91350192737dd1d1b219c05277f067
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 6 weeks ago
config: riscv-randconfig-s031-20200729
When kernel idle, system will enter wait/stop mode, wdog should continue
running in this scenario, and the refresh thread can wake up system from
wait/stop mode.
Signed-off-by: Anson Huang
---
no change.
---
drivers/watchdog/imx7ulp_wdt.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
According to reference manual, the i.MX7ULP WDOG's operations except
refresh should follow below sequence:
1. disable global interrupts;
2. unlock the wdog and wait unlock bit set;
3. reconfigure the wdog and wait for reconfiguration bit set;
4. enabel global interrupts.
Strictly follow the recom
Hi, Philipp/Rob
> Subject: Re: [PATCH V3 3/3] pci: imx: Select RESET_IMX7 by default
>
> On Wed, 2020-07-29 at 09:26 -0600, Rob Herring wrote:
> > On Mon, Jul 20, 2020 at 8:26 AM Anson Huang
> wrote:
> > > i.MX7 reset driver now supports module build and it is no longer
> > > built in by defaul
On Wed, Jul 29, 2020 at 5:09 PM Linus Torvalds
wrote:
>
> Removing the __latent_entropy marker obviously fixes things.
Ok, I did that for now. I spent a few minutes looking at the gcc
plugin in case I'd be hit by some sudden stroke of genius, but that
didn't happen, so let's avoid the issue until
在 2020/7/30 上午2:06, Hugh Dickins 写道:
> On Wed, 29 Jul 2020, Alex Shi wrote:
>>
>> Is there any comments or suggestion for this patchset?
>> Any hints will be very appreciated.
>
> Alex: it is now v5.8-rc7, obviously too late for this patchset to make
> v5.9, so I'm currently concentrated on che
> -Original Message-
> From: David Hildenbrand
> Sent: Wednesday, July 29, 2020 5:35 PM
> To: Mike Rapoport ; Justin He
> Cc: Dan Williams ; Vishal Verma
> ; Catalin Marinas ;
> Will Deacon ; Greg Kroah-Hartman
> ; Rafael J. Wysocki ; Dave
> Jiang ; Andrew Morton ;
> Steve Capper ; Mark
On Wed, 29 Jul 2020, Kees Cook wrote:
> From: Scott Branden
>
> Move kernel_read_file* out of linux/fs.h to its own linux/kernel_read_file.h
> include file. That header gets pulled in just about everywhere
> and doesn't really need functions not related to the general fs interface.
>
> Suggeste
On 07/28/20 at 08:11am, Mike Rapoport wrote:
> From: Mike Rapoport
>
> Currently for_each_mem_range() iterator is the most generic way to traverse
> memblock regions. As such, it has 8 parameters and it is hardly convenient
> to users. Most users choose to utilize one of its wrappers and the only
On Wed, 29 Jul 2020 22:48:05 +0300, Maxim Levitsky wrote:
> virtio-scsi currently has limit of 8 outstanding notifications so when more
> that
> 8 LUNs are unplugged, some are missed.
>
> Commit 5ff843721467 ("scsi: virtio_scsi: unplug LUNs when events missed")
> Fixed this by checking the 'even
On Wed, 29 Jul 2020 13:18:38 +0800, Stanley Chu wrote:
> This patchset introduces and applies DELAY_AFTER_LPM device quirk in MediaTek
> platforms.
>
> Stanley Chu (2):
> scsi: ufs: Introduce device quirk "DELAY_AFTER_LPM"
> scsi: ufs-mediatek: Apply DELAY_AFTER_LPM quirk to Micron devices
>
On Wed, 29 Jul 2020, Kees Cook wrote:
> In preparation for refactoring kernel_read_file*(), remove the redundant
> "size" argument which is not needed: it can be included in the return
> code, with callers adjusted. (VFS reads already cannot be larger than
> INT_MAX.)
>
> Acked-by: Scott Branden
"tReceiverResponse 15 ms Section 6.6.2
The receiver of a Message requiring a response Shall respond
within tReceiverResponse in order to ensure that the
sender’s SenderResponseTimer does not expire."
When the cpu complex is busy running other lower priority
work items, TCPM's work queue sometimes
On Wed, 29 Jul 2020, Kees Cook wrote:
> In preparation for further refactoring of kernel_read_file*(), rename
> the "max_size" argument to the more accurate "buf_size", and correct
> its type to size_t. Add kerndoc to explain the specifics of how the
> arguments will be used. Note that with buf_si
Hi Kuai,
On Thu, Jul 30, 2020 at 09:19:01AM +0800, Yu Kuai wrote:
> commit 9dc55f1389f9 ("iomap: add support for sub-pagesize buffered I/O
> without buffer heads") replace the per-block structure buffer_head with
> the per-page structure iomap_page. However, iomap_page can't track the
> dirty stat
Fix below warnings reported by coccicheck:
./arch/um/drivers/vector_user.c:403:2-7: WARNING: NULL check before some
freeing functions is not needed.
Signed-off-by: Li Heng
---
arch/um/drivers/vector_user.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/um/drivers/vec
On Wed, Jul 29, 2020 at 07:12:58PM -0700, Linus Torvalds wrote:
> On Wed, Jul 29, 2020 at 5:09 PM Linus Torvalds
> wrote:
> >
> > Removing the __latent_entropy marker obviously fixes things.
>
> Ok, I did that for now. I spent a few minutes looking at the gcc
> plugin in case I'd be hit by some s
On Wed, 29 Jul 2020, Kees Cook wrote:
> In preparation for adding partial read support, add an optional output
> argument to kernel_read_file*() that reports the file size so callers
> can reason more easily about their reading progress.
>
> Acked-by: Scott Branden
> Reviewed-by: Mimi Zohar
> R
allnoconfig
x86_64 randconfig-a004-20200729
x86_64 randconfig-a005-20200729
x86_64 randconfig-a002-20200729
x86_64 randconfig-a006-20200729
x86_64 randconfig-a003-20200729
x86_64 randconfig-a001
defconfig
x86_64 randconfig-a004-20200729
x86_64 randconfig-a005-20200729
x86_64 randconfig-a002-20200729
x86_64 randconfig-a006-20200729
x86_64 randconfig-a003-20200729
x86_64 randconfig-a001-20200729
i386
On Thu, 30 Jul 2020, Stephen Rothwell wrote:
> > I am still applying the above patch ...
>
> The merge window is coming up fast ... is anything happening about this
> failure?
A new patch is coming, but I'm not sure this code has had enough review
from the core VFS folk.
Please drop secure_uff
On Wed, Jul 29, 2020 at 06:23:41PM -0400, Arvind Sankar wrote:
> On Wed, Jul 29, 2020 at 03:04:43PM -0700, Kees Cook wrote:
> > On Fri, Jul 17, 2020 at 04:17:54PM -0400, Arvind Sankar wrote:
> > > Same as v5 previously posted, but rebased onto next-20200717.
> > >
> > > v5:
> > > https://lore.ker
Hi Greg,
Sure just sent the new patch v3.
Patch applies cleanly on my end. So wondering what I am missing.
Just in case if you are still noticing merge conflicts.
Here is the git log of my local tree:
633198cd2945b7 (HEAD -> usb-next-1) usb: typec: tcpm: Migrate
workqueue to RT priority for proc
On Tue, 2020-07-28 at 20:30 +0800, Qii Wang wrote:
> Newer MTK chip support more than 8GB of dram. Replace support_33bits
> with more general dma_max_support and remove mtk_i2c_set_4g_mode.
>
> Signed-off-by: Qii Wang
Qii,
After you remove I2C_DMA_4G_MODE Matthias mentioned, you can have:
Revi
From: Zhang Qiang
Due to cpu hotplug, the "cpuup_canceled" func be called, it's currently
manipulating the alien cache for the canceled cpu's node and this node
may be the same as the node which node's alien cache being operated in
the "__cache_free_alien" func, so we should add a protect for nod
Hi Alex,
On 7/30/20 4:32 AM, Alex Williamson wrote:
On Tue, 14 Jul 2020 13:57:03 +0800
Lu Baolu wrote:
Replace iommu_aux_at(de)tach_device() with iommu_aux_at(de)tach_group().
It also saves the IOMMU_DEV_FEAT_AUX-capable physcail device in the
vfio_group data structure so that it could be reu
Hi all,
After merging the pm tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
drivers/acpi/processor_idle.c: In function 'acpi_idle_enter_s2idle':
drivers/acpi/processor_idle.c:666:4: warning: 'return' with no value, in
function returning non-void [-Wreturn-type]
666
Lee Jones 於 2020年7月29日 週三 下午6:12寫道：
>
> On Wed, 29 Jul 2020, Gene Chen wrote:
>
> > Lee Jones 於 2020年7月27日 週一 下午8:43寫道：
> > >
> > > On Fri, 17 Jul 2020, Gene Chen wrote:
> > >
> > > > From: Gene Chen
> > > >
> > > > Remove unuse register definition.
> > >
> > > This should not be in here.
> > >
Hi,
Summary should specified this patch is for MediaTek:
dt-bindings: add MediaTek keypad devicetree documentation
On Mon, 2020-07-27 at 19:45 +0800, Fengping Yu wrote:
> From: "fengping.yu"
> Add Mediatek matrix keypad dt-bindings doc as yaml schema.
>
> Signed-off-by: fengping.yu
> ---
>
Hi James,
On Thu, 30 Jul 2020 12:35:03 +1000 (AEST) James Morris
wrote:
>
> On Thu, 30 Jul 2020, Stephen Rothwell wrote:
>
> > > I am still applying the above patch ...
> >
> > The merge window is coming up fast ... is anything happening about this
> > failure?
>
> A new patch is coming,
Fixes coccicheck warning:
./drivers/scsi/mvsas/mv_init.c:244:11-29: WARNING: dma_alloc_coherent use in
mvi -> tx already zeroes out memory, so memset is not needed
./drivers/scsi/mvsas/mv_init.c:250:15-33: WARNING: dma_alloc_coherent use in
mvi -> rx_fis already zeroes out memory, so memset is
Add a warning if CPU being onlined did not report QS already. This is to
simplify the code in the CPU onlining path and also to make clear about
where QS is reported. The act of QS reporting in CPU onlining path is
is likely unnecessary as shown by code reading and testing with
rcutorture's TREE03
At least since v4.19, the FQS loop no longer reports quiescent states
unless it is a dire situation where an offlined CPU failed to report
a quiescent state. Let us clarify the comment in rcu_gp_init() inorder
to keep the comment current.
Signed-off-by: Joel Fernandes (Google)
---
kernel/rcu/tre
On 7/29/20 7:28 PM, Badhri Jagan Sridharan wrote:
> Hi Greg,
>
> Sure just sent the new patch v3.
>
> Patch applies cleanly on my end. So wondering what I am missing.
I expected your patch to conflict with Hans' patch series.
Maybe those are in a different tree/branch ?
Guenter
> Just in case
Hi Greg,
On 7/28/20 11:17 PM, Greg KH wrote:
On Tue, Jul 28, 2020 at 08:46:35PM -0700, Hemant Kumar wrote:
This MHI client driver allows userspace clients to transfer
raw data between MHI device and host using standard file operations.
Device file node is created with format
/dev/mhi__
Curren
This warning should be fixed also.
Should I send another patch?
Thanks !
On Thu, 2020-07-30 at 12:55 +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the pm tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> drivers/acpi/processor_idle.c: In function 'ac
Make use of the flex_array_size() helper to calculate the size of a
flexible array member within an enclosing structure.
This helper offers defense-in-depth against potential integer
overflows, while at the same time makes it explicitly clear that
we are dealing with a flexible array member.
Sign
On 2020/7/30 10:27, Gao Xiang wrote:
Hi Kuai,
On Thu, Jul 30, 2020 at 09:19:01AM +0800, Yu Kuai wrote:
commit 9dc55f1389f9 ("iomap: add support for sub-pagesize buffered I/O
without buffer heads") replace the per-block structure buffer_head with
the per-page structure iomap_page. However, iomap
On Wed, Jul 29, 2020 at 04:43:04PM -0700, Linus Torvalds wrote:
> On Wed, Jul 29, 2020 at 4:08 PM Stephen Rothwell
> wrote:
> >
> > include/linux/random.h:123:24: error: variable 'net_rand_state' with
> > 'latent_entropy' attribute must not be local
> > 123 | DECLARE_PER_CPU(struct rnd_state,
On Thu, Jul 30, 2020 at 09:19:01AM +0800, Yu Kuai wrote:
> +++ b/fs/iomap/buffered-io.c
> @@ -29,7 +29,9 @@ struct iomap_page {
> atomic_tread_count;
> atomic_twrite_count;
> spinlock_t uptodate_lock;
> + spinlock_t dir
On Wed, Jul 29, 2020 at 02:45:10PM -0700, Andrew Morton wrote:
> On Wed, 29 Jul 2020 14:21:12 -0700 Kees Cook wrote:
>
> > On Sun, Jul 26, 2020 at 01:01:17PM +0200, Alexander A. Klimov wrote:
> > > Rationale:
> > > Reduces attack surface on kernel devs opening the links for MITM
> > > as HTTPS tr
Hi Kees,
On Wed, Jul 29, 2020 at 08:17:48PM -0700, Kees Cook wrote:
> And just another heads-up, the patch[1] (which was never sent to a public
> list) also breaks arm64 (circular header needs?):
(...)
Definitely, we've just got a report about this, I'll have a look once
I'm at the office. I'd li
On Wed, Jul 15, 2020 at 10:45 PM Suren Baghdasaryan wrote:
>
> syzbot report [1] describes a deadlock when write operation against an
> ashmem fd executed at the time when ashmem is shrinking its cache results
> in the following lock sequence:
>
> Possible unsafe locking scenario:
>
> CPU0
801 - 900 of 1246 matches
Mail list logo
