> On 2020/06/18 22:11, Sungjong Seo wrote:
> >> BTW
> >> Even with this patch applied, VOL_DIRTY remains until synced in the
> >> above case.
> >> It's not easy to reproduce as rmdir, but I'll try to fix it in the
> future.
> >
> > I think it's not a problem not to clear VOL_DIRTY under real erro
> On Aug 5, 2020, at 2:15 PM, Mimi Zohar wrote:
>
> On Wed, 2020-08-05 at 09:59 -0700, James Morris wrote:
>> On Wed, 5 Aug 2020, James Bottomley wrote:
>>
>>> I'll leave Mimi to answer, but really this is exactly the question that
>>> should have been asked before writing IPE. However, sinc
The underlying Ethernet device may request necessary tailroom to be
allocated by setting needed_tailroom. This driver should also set
needed_tailroom to request the tailroom needed by the underlying
Ethernet device to be allocated.
Cc: Willem de Bruijn
Cc: Martin Schiller
Signed-off-by: Xie He
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 449dc8c97089a6e09fb2dac4d92b1b7ac0eb7c1e
commit: 38fc6f295726366a0135ca87ab98f3ab92afd81f regulator: add support for
SY8827N regulator
date: 5 weeks ago
config: x86_64-randconfig-r003-20200809 (attached as
On Sat, Aug 08, 2020 at 05:29:58PM +0200, Greg Kroah-Hartman wrote:
> On Sat, Aug 08, 2020 at 04:05:00PM +0100, Catalin Marinas wrote:
> > On Sat, Aug 08, 2020 at 02:42:42PM +0200, Greg Kroah-Hartman wrote:
> > > diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
> > > index 87e81d2
binfmt_flat loader uses the gap between text and data to store data
segment pointers for the libraries. Even in the absence of shared
libraries it stores at least one pointer to the executable's own data
segment. Text and data can go back to back in the flat binary image and
without offsetting data
+Andy
Andy, can you please review this one?
Thanks,
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org ow...@vger.kernel.org> On Behalf Of Divya Bharathi
> Sent: Thursday, July 30, 2020 9:31 AM
> To: dvh...@infradead.org
> Cc: LKML; platform-driver-...@vger.kernel.or
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 449dc8c97089a6e09fb2dac4d92b1b7ac0eb7c1e
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 7 weeks ago
config: openrisc-randconfig-s032-20200809 (attac
pmbus_do_probe doesn't use the id information provided in its second
argument, so this can be removed, which then allows using the
single-parameter i2c probe function ("probe_new") for probes.
This avoids scanning the identifier tables during probes.
Drivers which didn't use the id are converted
Hi Youri,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 11030fe96b57ad843518b0e9430f3cd4b3610ce2
commit: 3b2abda7d28c69f564c1157b9b9c21ef40092ee9 soc: fsl: dpio: Replace QMAN
array mode with ring mode enqueue
date
On Thu, 6 Aug 2020 at 14:38, Ezequiel Garcia wrote:
>
> From: Jernej Skrabec
>
> When dealing with with interlaced frames, reference lists must tell if
> each particular reference is meant for top or bottom field. This info
> is currently not provided at all in the H264 related controls.
>
> Make
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 11030fe96b57ad843518b0e9430f3cd4b3610ce2
commit: cd486e627e67ee9ab66914d36d3127ef057cc010 ath9k_htc: Discard undersized
packets
date: 10 months ago
config: sparc64-randconfig-s032-20200809 (attached as .co
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 11030fe96b57ad843518b0e9430f3cd4b3610ce2
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 7 weeks ago
config: x86_64-randconfig-s031-20200809 (attache
Megha,
"Dey, Megha" writes:
> On 8/7/2020 9:47 AM, Thomas Gleixner wrote:
>> I'm all for sharing code and making the life of driver writers simple
>> because that makes my life simple as well, but not by creating a layer
>> at the wrong level and then hacking it into submission until it finally
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 11030fe96b57ad843518b0e9430f3cd4b3610ce2
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 7 weeks ago
config: sparc64-randconfig-s032-20200809 (attach
On Sat, Aug 8, 2020 at 3:11 PM Crt Mori wrote:
>
> Document internal/private struct for mlx90632 device.
Thanks. The only issue with it is that it should go before the one
that adds member(s) to the struct.
--
With Best Regards,
Andy Shevchenko
On Sat, Aug 8, 2020 at 3:10 PM Crt Mori wrote:
>
> Since the second patch is dependent on the first and was still not
> merged, I have decided to send them together. First patch just makes
> second one more readable as it splits out the repeated calculation and
> that enables the second patch to t
On Sat, Aug 8, 2020 at 3:10 PM Crt Mori wrote:
>
> TAdut4 was calculated each iteration although it did not change. In light
> of near future additions of the Extended range DSP calculations, this
> function refactoring will help reduce unrelated changes in that series as
> well as reduce the numb
On Sat, Aug 8, 2020 at 3:11 PM Crt Mori wrote:
>
> For some time the market wants medical grade accuracy in medical range,
> while still retaining the declared accuracy outside of the medical range
> within the same sensor. That is why we created extended calibration
> which is automatically switc
On Sat, Aug 8, 2020 at 3:10 PM Crt Mori wrote:
>
> Since the second patch is dependent on the first and was still not
> merged, I have decided to send them together. First patch just makes
> second one more readable as it splits out the repeated calculation and
> that enables the second patch to t
On Sat, Aug 8, 2020 at 3:10 PM Crt Mori wrote:
>
> Since the second patch is dependent on the first and was still not
> merged, I have decided to send them together. First patch just makes
> second one more readable as it splits out the repeated calculation and
> that enables the second patch to t
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 11030fe96b57ad843518b0e9430f3cd4b3610ce2
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 7 weeks ago
config: riscv-randconfig-s031-20200809 (attached
-randconfig-s032-20200808 (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version
tags from KBUILD_OUTPUT directory
Reply-To:
running 'make ARCH=x86_64 COMPILED_SOURCE=1 cscope tags' in
KBUILD_OUTPUT directory produces lots of "No such file or directory"
warnings from realpath
it seems like commit 4f491bb6ea2a greatly improved tags generation when
COMPILED_SOURCE=1 is set, bu
Hi Daniel,
Thank you for the patch.
On Fri, Aug 07, 2020 at 05:35:30AM -0300, Daniel W. S. Almeida wrote:
> From: "Daniel W. S. Almeida"
>
> Fixes the following coccinelle report:
>
> drivers/media/usb/uvc/uvc_ctrl.c:1860:5-11:
> ERROR: invalid reference to the index variable of the iterator o
Hi Daniel,
Thank you for the patch.
On Fri, Aug 07, 2020 at 05:35:31AM -0300, Daniel W. S. Almeida wrote:
> From: "Daniel W. S. Almeida"
>
> Fixes the following coccinelle reports:
>
> drivers/media/usb/uvc/uvc_v4l2.c:840:8-13:
> ERROR: invalid reference to the index variable of the iterator o
Hi Daniel,
On Sat, Aug 08, 2020 at 11:40:13PM +0300, Laurent Pinchart wrote:
> On Fri, Aug 07, 2020 at 05:35:30AM -0300, Daniel W. S. Almeida wrote:
> > From: "Daniel W. S. Almeida"
> >
> > Fixes the following coccinelle report:
> >
> > drivers/media/usb/uvc/uvc_ctrl.c:1860:5-11:
> > ERROR: inv
Hi Linus,
Please pull the arm64 updates below. The fix addresses a symbol export
for the tegra194-cpufreq module that made its way into mainline (the
issue was found in -next but still debating an alternative fix without
exporting __cpu_logical_map).
Thanks.
The following changes since commit 0e
On Fri, Oct 04, 2019 at 03:39:46PM +0300, Mika Westerberg wrote:
> This is otherwise similar to pcie_wait_for_link() but allows passing
> custom activation delay in milliseconds.
>
> Signed-off-by: Mika Westerberg
> ---
> drivers/pci/pci.c | 21 ++---
> 1 file changed, 18 inserti
I forgot to add that my mostly hanging boots look like this:
https://photos.app.goo.gl/HJvTraYYZbiNTNE39
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/
Hi Prabhakar,
Thank you for the patches.
On Fri, Aug 07, 2020 at 06:49:47PM +0100, Lad Prabhakar wrote:
> Hi All,
>
> This patch series adds support for DU and LVDS to r8a7742
> SoC and enables LCD support on r8a7742-iwg21d-q7 board.
>
> This patch series applies on top of [1].
>
> [1] https:/
Hi Prabhakar,
Thank you for the patch.
On Fri, Aug 07, 2020 at 06:49:48PM +0100, Lad Prabhakar wrote:
> Document the RZ/G1H (R8A7742) SoC in the R-Car DU bindings.
>
> Signed-off-by: Lad Prabhakar
> Reviewed-by: Marian-Cristian Rotariu
>
Reviewed-by: Laurent Pinchart
> ---
> Documentation
pmbus_do_probe doesn't use the id information provided in its second
argument, so this can be removed, which then allows using the
single-parameter i2c probe function ("probe_new") for probes.
This avoids scanning the identifier tables during probes.
Drivers which didn't use the id are converted
On 2020-08-06 17:12, Ezequiel Garcia wrote:
> The prediction weight parameters are only required under
> certain conditions, which depend on slice header parameters.
>
> As specified in section 7.3.3 Slice header syntax, the prediction
> weight table is present if:
>
> ((weighted_pred_flag && (sl
Hi Prabhakar,
Thank you for the patch.
On Fri, Aug 07, 2020 at 06:49:49PM +0100, Lad Prabhakar wrote:
> Add direct support for the r8a7742 (RZ/G1H).
>
> The RZ/G1H shares a common, compatible configuration with the r8a7790
> (R-Car H2) so that device info structure is reused, the only difference
Hi Prabhakar,
Thank you for the patch.
On Fri, Aug 07, 2020 at 06:49:50PM +0100, Lad Prabhakar wrote:
> Document the RZ/G1H (R8A7742) LVDS bindings.
>
> Signed-off-by: Lad Prabhakar
> Reviewed-by: Marian-Cristian Rotariu
>
Reviewed-by: Laurent Pinchart
> ---
> .../devicetree/bindings/disp
On Sun, Aug 09, 2020 at 12:03:27AM +0300, Laurent Pinchart wrote:
> Hi Prabhakar,
>
> Thank you for the patch.
>
> On Fri, Aug 07, 2020 at 06:49:50PM +0100, Lad Prabhakar wrote:
> > Document the RZ/G1H (R8A7742) LVDS bindings.
> >
> > Signed-off-by: Lad Prabhakar
> > Reviewed-by: Marian-Cristia
Hi Prabhakar,
Thank you for the patch.
On Fri, Aug 07, 2020 at 06:49:51PM +0100, Lad Prabhakar wrote:
> The LVDS encoders on RZ/G1H SoC is identical to the R-Car Gen2 family. Add
> support for RZ/G1H (R8A7742) SoC to the LVDS encoder driver.
>
> Signed-off-by: Lad Prabhakar
> Reviewed-by: Maria
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 11030fe96b57ad843518b0e9430f3cd4b3610ce2
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 7 weeks ago
config: mips-randconfig-s032-20200809 (attached
From: Johan Hovold
Date: Thu, 6 Aug 2020 17:37:53 +0200
> A recent commit introduced a late error path in phy_device_create()
> which fails to release the device name allocated by dev_set_name().
>
> Fixes: 13d0ab6750b2 ("net: phy: check return code when requesting PHY driver
> module")
> Cc:
Hi Prabhakar,
Thank you for the patch.
On Fri, Aug 07, 2020 at 06:49:53PM +0100, Lad Prabhakar wrote:
> Add LVDS encoder node to r8a7742 SoC DT.
>
> Signed-off-by: Lad Prabhakar
> Reviewed-by: Marian-Cristian Rotariu
>
> ---
> arch/arm/boot/dts/r8a7742.dtsi | 54 +
Hi Prabhakar,
Thank you for the patch.
On Fri, Aug 07, 2020 at 06:49:52PM +0100, Lad Prabhakar wrote:
> Add du node to r8a7742 SoC DT. Boards that want to enable the DU
> need to specify the output topology.
>
> Signed-off-by: Lad Prabhakar
> Reviewed-by: Marian-Cristian Rotariu
>
Reviewed-b
From: Nick Desaulniers
Date: Thu, 6 Aug 2020 11:29:39 -0700
> From: Jakub Kicinski
>
> When ur_load_imm_any() is inlined into jeq_imm(), it's possible for the
> compiler to deduce a case where _val can only have the value of -1 at
> compile time. Specifically,
>
> /* struct bpf_insn: _s32 imm
Hi Stephen,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on bcf876870b95592b52519ed4aafcf9d95999bc9c]
url:
https://github.com/0day-ci/linux/commits/Stephen-Kitt/hwmon-pmbus-use-simple-i2c-probe-function/20200809-025818
base:bcf876870b95592b52519ed4aafcf
The pull request you sent on Sat, 8 Aug 2020 21:53:12 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/06a81c1c7db9bd5de0bd38cd5acc44bb22b99150
Thank you!
--
Deet-doot-dot, I am a bot
From: linmiaohe
Date: Thu, 6 Aug 2020 19:52:24 +0800
> From: Miaohe Lin
>
> Use helper function fdput() to fput() the file iff FDPUT_FPUT is set.
>
> Signed-off-by: Miaohe Lin
Applied.
From: linmiaohe
Date: Thu, 6 Aug 2020 19:53:16 +0800
> From: Miaohe Lin
>
> We should fput() file iff FDPUT_FPUT is set. So we should set fput_needed
> accordingly.
>
> Fixes: 00e188ef6a7e ("sockfd_lookup_light(): switch to fdget^W^Waway from
> fget_light")
> Signed-off-by: Miaohe Lin
Appli
Hi Prabhakar,
Thank you for the patch.
On Fri, Aug 07, 2020 at 06:49:54PM +0100, Lad Prabhakar wrote:
> The iwg21d comes with a 7" capacitive touch screen, therefore
> add support for it.
I can't review most of this properly as I don't have access to the
schematics. Is there a way to get it ?
>
From: linmiaohe
Date: Thu, 6 Aug 2020 19:54:19 +0800
> From: Miaohe Lin
>
> The out_fs jump label has nothing to do but goto out.
>
> Signed-off-by: Miaohe Lin
Applied.
From: linmiaohe
Date: Thu, 6 Aug 2020 19:57:18 +0800
> From: Miaohe Lin
>
> Use helper function ip_is_fragment() to check ip fragment.
>
> Signed-off-by: Miaohe Lin
Applied.
Hello,
syzbot found the following issue on:
HEAD commit:c0842fbc random32: move the pseudo-random 32-bit definitio..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=127a8d6690
kernel config: https://syzkaller.appspot.com/x/.config?x=cf567e8c7428377e
das
From: linmiaohe
Date: Sat, 8 Aug 2020 16:23:10 +0800
> From: Miaohe Lin
>
> Convert the uses of fallthrough comments to fallthrough macro.
>
> Signed-off-by: Miaohe Lin
Applied.
Hi Vinay,
On Fri, Aug 07, 2020 at 06:22:59PM +0530, Vinay Simha B N wrote:
> Hi All,
>
> Please Review the patch
I'm afraid I won't have time for at least a couple of weeks.
> On Wed, Jul 29, 2020 at 6:01 PM Vinay Simha B N wrote:
>
> > Hi All,
> >
> > Please Review the patch
> >
> > On Fri,
On Fri, Aug 7, 2020 at 11:46 PM Takashi Iwai wrote:
>
> On Sat, 08 Aug 2020 02:23:24 +0200,
> John Stultz wrote:
> >
> > On Thu, Aug 6, 2020 at 3:33 AM Takashi Iwai wrote:
> > >
> > > Linus,
> > >
> > > please pull sound updates for v5.9 from:
> > >
> > > git://git.kernel.org/pub/scm/linux/kern
Any pre-existing caller of this function uses 'true' to signal to use
notifications or not, but we now also have signaled notifications.
Update existing callers that specify 'true' for notify to use the
updated TWA_RESUME instead.
This was noted in the original commit as well:
e91b48162332 ("task
Hi!
Next has been unusable for a while, but today I got dmesg.
Screen is blinking, machine is very unhappy, and ssh is slow/hangs,
but I got this:
This is recurring patern, usually machine dies like this within 30
minutes of boot.
[ 455.019838] perf: interrupt took too long (2509 > 2500), low
On Sat, Aug 08, 2020 at 09:22:29PM +0800, Alex Shi wrote:
>
>
> 在 2020/8/5 下午9:02, Alex Shi 写道:
> >
> >
> > 在 2020/8/5 下午8:28, Alex Shi 写道:
> >> The last patch has a problem on define. this version could fix it.
> >>
> >> BTW, I see some !memcg happens when MEMCG compilered but disabled by
> >
Hello My Dearest
Please I appeal to you to exercise a little patience and read through
my mail carefully, I am contacting you personally for investment
assistance and a long term business relationship in your Country.
I am Mrs. Sophia Robin a citizen of the united state of America; I
work in HSBC
Hi,
I am very sorry you missed them, I thought you saw it (reply on v3 of
the patch). Maybe something happened to that mail, as it contained
link to datasheet, so I will omit it now.
Except for the order, only the remarks below are still open (did you
get the polling trail I did?)
On Sat, 8 Aug 2
Hi Nick,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 11030fe96b57ad843518b0e9430f3cd4b3610ce2
commit: 9f4069b055d1508c833115df7493b6e0001e5c9b drm/i915: re-disable
-Wframe-address
date: 3 months ago
config: x8
Hi!
> Thanks for the lively discussion. I have tried to answer some of the
> comments below.
> > There are options today, e.g.
> >
> > a) If the restriction is only per-alias, you can have distinct aliases
> >where one is writable and another is executable, and you can make it
> >hard to
Hi!
> Good morning, I hope the week is progressing well for everyone.
>
> > > CPUs starting from Icelake use Total Memory Encryption (TME) in
> > > the place of MEE. TME throws away the Merkle tree, which means
> > > losing integrity and anti-replay protection but also enables
> > > variable size
Hello Linus,
This is the MTD PR for 5.9.
Thanks,
Miquèl
The following changes since commit dcb7fd82c75ee2d6e6f9d8cc71c52519ed52e258:
Linux 5.8-rc4 (2020-07-05 16:20:22 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git tags/mtd/for-5
On Thu, Aug 06, 2020 at 09:02:29PM +0200, Luc Van Oostenryck wrote:
> On Thu, Aug 06, 2020 at 06:07:25AM +0900, Stafford Horne wrote:
> > Now that __user annotations are fixed for openrisc uaccess api's we can
> > add checking to the access_ok macro. This patch adds the __chk_user_ptr
> > check, o
Starting from commit 17839856fd58 ("gup: document and work around "COW can
break either way" issue", 2020-06-02), explicit copy-on-write behavior is
enforced for private gup pages even if it's a read-only. It is achieved by
always passing FOLL_WRITE to emulate a write.
That should fix the COW iss
-20200808 (attached as .config)
compiler: powerpc64-linux-gcc (GCC) 9.3.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.2-118
On Thu, Aug 06, 2020 at 09:04:49PM +0200, Luc Van Oostenryck wrote:
> On Thu, Aug 06, 2020 at 06:07:24AM +0900, Stafford Horne wrote:
> > ---
> > arch/openrisc/kernel/signal.c | 14 +++---
> > 1 file changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/arch/openrisc/kernel/signal
On Thu, Aug 06, 2020 at 09:11:46PM +0200, Luc Van Oostenryck wrote:
> On Thu, Aug 06, 2020 at 06:07:19AM +0900, Stafford Horne wrote:
> > Hello,
> >
> > Changes since v1:
> > - in "io: Fixup defines and move include to the end" added a linux/types.h
> >include as there were compiler failurs p
On 2020-08-06 02:11, Daejun Park wrote:
> +static void ufshpb_issue_hpb_reset_query(struct ufs_hba *hba)
> +{
> + int err;
> + int retries;
> +
> + for (retries = 0; retries < HPB_RESET_REQ_RETRIES; retries++) {
> + err = ufshcd_query_flag(hba, UPIU_QUERY_OPCODE_SET_FLAG,
>
Hello!
Thanks to Jason for getting this conversation back on track.
Yes: in general, {} or a partial initializer /will/ zero padding bits.
However, there is a bug in some versions of GCC where {} will /not/ zero
padding bits; actually, Jason's test program in this mail
https://lore.kernel.org/
On 2020-08-06 02:02, Daejun Park wrote:
> @@ -537,6 +548,7 @@ struct ufs_dev_info {
> u8 *model;
> u16 wspecversion;
> u32 clk_gating_wait_us;
> + u8 b_ufs_feature_sup;
> u32 d_ext_ufs_feature_sup;
> u8 b_wb_buffer_type;
> u32 d_wb_alloc_units;
>
Hmm ... sh
Now that __user annotations are fixed for openrisc uaccess api's we can
add checking to the access_ok macro. This patch adds the __chk_user_ptr
check, on normal builds the added check is a nop.
Signed-off-by: Stafford Horne
Reviewed-by: Luc Van Oostenryck
---
Changes since v2:
- Remove __force
As suggested by Linus when reviewing commit 9cb2feb4d21d
("arch/openrisc: Fix issues with access_ok()") last year; making
__range_ok an inline function also fixes the used twice issue that the
commit was fixing. I agree it's a good cleanup. This patch addresses
that as I am currently working on t
This didn't seem to cause any issues, but while working on fixing up
sparse annotations for OpenRISC I noticed this. This patch moves the
include of asm-generic/io.h to the end of the file. Also, we add
defines of ioremap and iounmap, that way we don't get duplicate
definitions from asm-generic/i
The __user annotations in signal.c were mostly missing. The missing
annotations caused the warnings listed below. This patch fixes them up
by adding the __user annotations.
arch/openrisc/kernel/signal.c:71:38: warning: incorrect type in initializer
(different address spaces)
arch/openrisc/kerne
Since commit b48b2c3e5043 ("openrisc: use generic strnlen_user()
function") the macro __addr_ok is no longer used. It is safe to remove
so this patch removes it.
Signed-off-by: Stafford Horne
---
arch/openrisc/include/asm/uaccess.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/open
The OpenRISC user access functions put_user(), get_user() and
clear_user() were missing proper sparse annotations. This generated
warnings like the below.
This patch adds the annotations to fix the warnings.
Example warnings:
net/ipv4/ip_sockglue.c:759:29: warning: incorrect type in argument 1
Hello,
Changes since v1:
- in "io: Fixup defines and move include to the end" added a linux/types.h
include as there were compiler failurs pointed out by kbuild.
- Remove some __force's suggested by Luc Van Oostenryck
This a series of fixes for OpenRISC sparse warnings. The kbuild robots r
On Sun, Aug 09, 2020 at 07:48:22AM +0900, Stafford Horne wrote:
> On Thu, Aug 06, 2020 at 09:04:49PM +0200, Luc Van Oostenryck wrote:
> > On Thu, Aug 06, 2020 at 06:07:24AM +0900, Stafford Horne wrote:
> > > ---
> > > arch/openrisc/kernel/signal.c | 14 +++---
> > > 1 file changed, 7 inser
On Mon, Jul 20, 2020 at 05:55:14PM +0200, Ahmed S. Darwish wrote:
> Preemption must be disabled before entering a sequence count write side
> critical section. Failing to do so, the seqcount read side can preempt
> the write side section and spin for the entire scheduler tick. If that
> reader be
On Sat, Aug 08, 2020 at 04:21:22PM -0700, Guenter Roeck wrote:
> On Mon, Jul 20, 2020 at 05:55:14PM +0200, Ahmed S. Darwish wrote:
> > Preemption must be disabled before entering a sequence count write side
> > critical section. Failing to do so, the seqcount read side can preempt
> > the write si
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 06a81c1c7db9bd5de0bd38cd5acc44bb22b99150
commit: ec4b0925089826af45e99cdf78a8ac84c1d005f1 NFS: inter ssc open
date: 10 months ago
config: openrisc-randconfig-m031-20200809 (attached as .config)
compiler: or
From: Kan Liang
[ Upstream commit 2af834f1faab3f1e218fcbcab70a399121620d62 ]
When counting IMC uncore events on some TGL machines, an oops will be
triggered.
[ 393.101262] BUG: unable to handle page fault for address:
b45200e15858
[ 393.101269] #PF: supervisor read access in kernel mod
From: Zhenzhong Duan
[ Upstream commit 5d7f7d1d5e01c22894dee7c9c9266500478dca99 ]
The original code is a nop as i_mce.status is or'ed with part of itself,
fix it.
Fixes: a1300e505297 ("x86/ras/mce_amd_inj: Trigger deferred and thresholding
errors interrupts")
Signed-off-by: Zhenzhong Duan
Sig
From: Giovanni Gherdovich
[ Upstream commit 51beea8862a3095559862df39554f05042e1195b ]
There may be CPUs that support turbo boost but don't declare any turbo
ratio, i.e. their MSR_TURBO_RATIO_LIMIT is all zeroes. In that condition
scale-invariant calculations can't be performed.
Fixes: 1567c3e3
From: Peng Liu
[ Upstream commit 9b1b234bb86bcdcdb142e900d39b599185465dbb ]
During sched domain init, we check whether non-topological SD_flags are
returned by tl->sd_flags(), if found, fire a waning and correct the
violation, but the code failed to correct the violation. Correct this.
Fixes: 1
From: Christophe JAILLET
[ Upstream commit c3d4eb3bf6ad32466555b31094f33a299444f795 ]
The call to tegra_bpmp_get() must be balanced by a call to
tegra_bpmp_put() in case of error, as already done in the remove
function.
Add an error handling path and corresponding goto.
Fixes: 52d15dd23f0b ("m
From: Herbert Xu
[ Upstream commit 3906f640224dbe7714b52b66d7d68c0812808e19 ]
The crypto notify call occurs with a read mutex held so you must
not do any substantial work directly. In particular, you cannot
call crypto_alloc_* as they may trigger further notifications
which may dead-lock in the
From: Giovanni Cabiddu
[ Upstream commit 528f776df67c440361b2847b4da400d8754bf030 ]
Allow AES-XTS requests that are not multiple of the block size.
If a request is smaller than the block size, return -EINVAL.
This fixes the following issue reported by the crypto testmgr self-test:
alg: skcip
From: Qais Yousef
[ Upstream commit d81ae8aac85ca2e307d273f6dc7863a721bf054e ]
struct uclamp_rq was zeroed out entirely in assumption that in the first
call to uclamp_rq_inc() they'd be initialized correctly in accordance to
default settings.
But when next patch introduces a static key to skip
From: Giovanni Gherdovich
[ Upstream commit e2b0d619b400ae326f954a018a1d65d736c237c5 ]
The product mcnt * arch_max_freq_ratio can overflows u64.
For context, a large value for arch_max_freq_ratio would be 5000,
corresponding to a turbo_freq/base_freq ratio of 5 (normally it's more like
1500-200
From: Lu Wei
[ Upstream commit 71fbe886ce6dd0be17f20aded9c63fe58edd2806 ]
In the function check_acpi_dev(), if it fails to create
platform device, the return value is ERR_PTR() or NULL.
Thus it must use IS_ERR_OR_NULL() to check return value.
Fixes: ecc83e52b28c ("intel-hid: new hid event drive
From: Lu Wei
[ Upstream commit 64dd4a5a7d214a07e3d9f40227ec30ac8ba8796e ]
In the function check_acpi_dev(), if it fails to create
platform device, the return value is ERR_PTR() or NULL.
Thus it must use IS_ERR_OR_NULL() to check return value.
Fixes: 332e081225fc ("intel-vbtn: new driver for Int
From: Qiushi Wu
[ Upstream commit 17ed808ad243192fb923e4e653c1338d3ba06207 ]
When kobject_init_and_add() returns an error, it should be handled
because kobject_init_and_add() takes a reference even when it fails. If
this function returns an error, kobject_put() must be called to properly
clean u
From: Sudeep Holla
[ Upstream commit fcd2e0deae50bce48450f14c8fc5611b08d7438c ]
Currently we are not initializing the scmi clock with discrete rates
correctly. We fetch the min_rate and max_rate value only for clocks with
ranges and ignore the ones with discrete rates. This will lead to wrong
in
From: Finn Thain
[ Upstream commit 931fc82a6aaf4e2e4a5490addaa6a090d78c24a7 ]
When writing values to the IOP status/control register make sure those
values do not have any extraneous bits that will clear interrupt flags.
To place the SCC IOP into bypass mode would be desirable but this is not
a
From: Kees Cook
[ Upstream commit 47e33c05f9f07cac3de833e531bcac9ae052c7ca ]
When SECCOMP_IOCTL_NOTIF_ID_VALID was first introduced it had the wrong
direction flag set. While this isn't a big deal as nothing currently
enforces these bits in the kernel, it should be defined correctly. Fix
the def
From: Vladimir Zapolskiy
[ Upstream commit 9177514ce34902b3adb2abd490b6ad05d1cfcb43 ]
The change corrects registration and deregistration on error path
of a regulator, the problem was manifested by a reported memory
leak on deferred probe:
as3722-regulator as3722-regulator: regulator 13 reg
From: Tiezhu Yang
[ Upstream commit 652d54e77a438cf38a5731d8f9983c81e72dc429 ]
In the function htvec_of_init(), system resource "parent_irq"
was not released in an error case. Thus add a jump target for
the completion of the desired exception handling.
Fixes: 818e915fbac5 ("irqchip: Add Loongso
From: Arnd Bergmann
[ Upstream commit 44623b2818f4a442726639572f44fd9b6d0ef68c ]
The clang integrated assembler complains about movzxw:
arch/x86/crypto/crc32c-pcl-intel-asm_64.S:173:2: error: invalid instruction
mnemonic 'movzxw'
It seems that movzwq is the mnemonic that it expects instead,
a
101 - 200 of 453 matches
Mail list logo
