<<<>>

Good Day, Hope you are doing great Today.I have a proposed BUSINESS DEAL that will benefit both parties. This is legitimate,legal and your personality will not be compromised.Please Reply to me ONLY if you are interested and consider your self capable for details. Sincerely, Peter OWEN

Re: kmemleak: Cannot allocate a kmemleak_object structure - Kernel 4.19.13

Now it just looks like it crashes on it's own with no issues from anything else (note the surrounding event entries which is just the temperature sensor.): * Jan 06 03:27:03 computername plasmashell[1065]: qml: temp unit: 0 Jan 06 03:27:09 computername plasmashell[1065]: qml: temp unit: 0 Jan

Re: [PATCH] make 'user_access_begin()' do 'access_ok()'

[ Re-sending the message because my first reply bounced - Guenther had mis-typed the lkml address ] On Sun, Jan 6, 2019 at 10:09 AM Guenter Roeck wrote: > > All alpha and sh4 (big and little endian) images fail to boot in qemu > with this patch applied. Reverting it fixes the problem. Funky.

[PATCH V8 0/11] KVM: X86: Introducing ROE Protection Kernel Hardening

-- Summary -- ROE is a hypercall that enables host operating system to restrict guest's access to its own memory. This will provide a hardening mechanism that can be used to stop rootkits from manipulating kernel static data structures and code. Once a memory region is protected the guest kernel

[PATCH V8 02/11] KVM: X86: Add arbitrary data pointer in kvm memslot iterator functions

This will help sharing data into the slot_level_handler callback. In my case I need to a share a counter for the pages traversed to use it in some bitmap. Being able to send arbitrary memory pointer into the slot_level_handler callback made it easy. Signed-off-by: Ahmed Abd El Mawgood ---

[PATCH V8 01/11] KVM: State whether memory should be freed in kvm_free_memslot

The conditions upon which kvm_free_memslot are kind of ad-hock, it will be hard to extend memslot with allocatable data that needs to be freed, so I replaced the current mechanism by clear flag that states if the memory slot should be freed. Signed-off-by: Ahmed Abd El Mawgood ---

[PATCH V8 03/11] KVM: X86: Add helper function to convert SPTE to GFN

Signed-off-by: Ahmed Abd El Mawgood --- arch/x86/kvm/mmu.c | 7 +++ arch/x86/kvm/mmu.h | 1 + 2 files changed, 8 insertions(+) diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c index 098df7d135..bbfe3f2863 100644 --- a/arch/x86/kvm/mmu.c +++ b/arch/x86/kvm/mmu.c @@ -1053,6 +1053,13 @@

[PATCH V8 05/11] KVM: Create architecture independent ROE skeleton

This patch introduces a hypercall that can assist against subset of kernel rootkits, it works by place readonly protection in shadow PTE. The end result protection is also kept in a bitmap for each kvm_memory_slot and is used as reference when updating SPTEs. The whole goal is to protect the guest

[PATCH V8 07/11] KVM: Add support for byte granular memory ROE

This patch documents and implements ROE_MPROTECT_CHUNK, a part of ROE hypercall designed to protect regions of a memory page with byte granularity. This feature provides a key primitive to protect against attacks involving pages remapping. Signed-off-by: Ahmed Abd El Mawgood ---

[PATCH V8 04/11] KVM: Document Memory ROE

ROE version documented here is implemented in the next 2 patches Signed-off-by: Ahmed Abd El Mawgood --- Documentation/virtual/kvm/hypercalls.txt | 40 1 file changed, 40 insertions(+) diff --git a/Documentation/virtual/kvm/hypercalls.txt

[PATCH V8 08/11] KVM: X86: Port ROE_MPROTECT_CHUNK to x86

Apply d->memslot->partial_roe_bitmap to shadow page table entries too. Signed-off-by: Ahmed Abd El Mawgood --- arch/x86/kvm/roe.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/arch/x86/kvm/roe.c b/arch/x86/kvm/roe.c index f787106be8..700f69823b 100644 ---

[PATCH V8 06/11] KVM: X86: Enable ROE for x86

This patch implements kvm_roe_arch_commit_protection and kvm_roe_arch_is_userspace for x86, and invoke kvm_roe via the appropriate vmcall. Signed-off-by: Ahmed Abd El Mawgood --- arch/x86/include/asm/kvm_host.h | 2 +- arch/x86/kvm/Makefile | 4 +- arch/x86/kvm/mmu.c

[PATCH V8 09/11] KVM: Add new exit reason For ROE violations

The problem is that qemu will not be able to detect ROE violations, so one option would be create host API to tell if a given page is ROE protected, or create ROE violation exit reason. Signed-off-by: Ahmed Abd El Mawgood --- arch/x86/kvm/x86.c | 10 +- include/kvm/roe.h|

[PATCH V8 10/11] KVM: Log ROE violations in system log

Signed-off-by: Ahmed Abd El Mawgood --- virt/kvm/kvm_main.c| 3 ++- virt/kvm/roe.c | 25 + virt/kvm/roe_generic.h | 3 ++- 3 files changed, 29 insertions(+), 2 deletions(-) diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c index d92d300539..b3dc7255b0

[PATCH V8 11/11] KVM: ROE: Store protected chunks in red black tree

The old way of storing protected chunks was a linked list. That made linear overhead when searching for chunks. When reaching 2000 chunk, The time taken two read the last chunk was about 10 times slower than the first chunk. This patch stores the chunks as tree for faster search. Signed-off-by:

[PATCH 1/8] nvmem: core: Set the provider read-only when no write callback is given

If no write callback is given the device should be marked as read-only. While at it also move from a bit or to a logical or as that is a logical expression. Signed-off-by: Alban Bedel --- drivers/nvmem/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 2/8] nvmem: core: Fix of_nvmem_cell_get() for optional cells

of_nvmem_cell_get() should return -ENOENT when a cell isn't defined, otherwise callers can't distinguish between a missing cell and other errors. Signed-off-by: Alban Bedel --- drivers/nvmem/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/nvmem/core.c

[PATCH 0/8] nvmem: Various small fixes and improvements

Hi, this series is mostly small bug fixes, but also add a new API to make things simpler in drivers that need to request an optional cell. Alban Bedel (8): nvmem: core: Set the provider read-only when no write callback is given nvmem: core: Fix of_nvmem_cell_get() for optional cells

[PATCH 6/8] nvmem: core: Always reference the device returned by nvmem_device_get()

In nvmem_device_get(), when the device lookup fails with DT it currently fallback on nvmem_find() which is wrong for two reasons. First nvmem_find() return NULL when nothing is found instead of an ERR_PTR. But nvmem_find() also just lookup the device, it doesn't reference the module and increment

[PATCH 4/8] nvmem: core: Fix cell lookup when no cell is found

If the cell list is not empty and nvmem_find_cell_by_node/name() is called for a cell that is not present in the list they will return an invalid pointer instead of NULL. This happen because list_for_each_entry() stop once it reach the list head again, but as the list head is not contained in a

[PATCH 5/8] nvmem: core: Properly handle connection ID in of_nvmem_device_get()

of_nvmem_device_get() would crash if NULL was passed as a connection ID. Rework this to use the usual sementic of assuming the first connection when no connection ID is given. Furthermore of_nvmem_device_get() would return -EINVAL when it failed to resolve the connection, making it impossible to

[PATCH 3/8] nvmem: Add nvmem_cell_get_optional and devm_nvmem_cell_get_optional

Add helper functions to make the driver code simpler when a cell is optional. Using these functions just return NULL when the cell doesn't exists or if nvmem is disabled. Signed-off-by: Alban Bedel --- drivers/nvmem/core.c | 48 ++

[PATCH 7/8] nvmem: core: Fix device reference leak

__nvmem_device_get() make use of bus_find_device() to get the relevant device and this function increase the reference count of the device found, however this is not accounted for anywhere. Fix __nvmem_device_get() and __nvmem_device_put() to properly release this reference count. Signed-off-by:

[PATCH 8/8] nvmem: core: Avoid useless iterations in nvmem_cell_get_from_lookup()

Once the correct cell has been found there is no need to continue iterating, just stop there. While at it replace the goto used to leave the loop with simple break statements. Signed-off-by: Alban Bedel --- drivers/nvmem/core.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff

Re: kernel: xhci_hcd 0000:00:14.0: ERROR unknown event type 37 - Kernel 4.19.13

I'm only posting to say I'm still waiting... The error came up while I slept, and when I copied that log and looked at it (yes, it WAS huge, just as you said), the timestamps at the head/tail were much later than the journal logged times. So I made a little script to monitor the journal kernel

Re: [PATCH] dmaengine: fsl-edma: use struct_size() in kzalloc()

On Fri, Jan 04, 2019 at 03:25:45PM -0600, Gustavo A. R. Silva wrote: > One of the more common cases of allocation size calculations is finding the > size of a structure that has a zero-sized array at the end, along with memory > for some number of elements for that array. For example: > > struct

Re: [GIT PULL] fscrypt update for 4.21

On Sun, Jan 06, 2019 at 09:20:07AM -0800, Eric Biggers wrote: > Hi Ted, that tag is still on an old commit. Probably you forgot to push. My scripts check to see that it was right (at least from my view of git.kernel.org) before it generates the push. I just checked and it's correct now, and I

Re: [PATCH v4 5/6] usb: musb: gadget: implement optional explicit status stage

On Sun, 6 Jan 2019, Paul Elder wrote: > Implement the mechanism for optional explicit status stage for the MUSB > driver. This allows a function driver to specify what to reply for the > status stage. The functionality for an implicit status stage is > retained. > > Signed-off-by: Paul Elder >

Re: [PATCH v2] driver: uio: fix possible memory leak and use-after-free in __uio_register_device

On Fri, 2019-01-04 at 22:19 +0800, liujian wrote: > 'idev' is malloced in __uio_register_device() and leak free it before > leaving from the uio_get_minor() error handing case, it will cause > memory leak. > > Also, in uio_dev_add_attributes() error handing case, idev is used > after >

Re: [GIT PULL] chrome-platform updates for v4.21

The pull request you sent on Fri, 4 Jan 2019 06:53:10 -0800: > git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git > tags/tag-chrome-platform-for-v4.21 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/12133258d7fe309b42a35677549c606b15a0822d Thank

Re: [GIT PULL] hwspinlock updates for v4.21

The pull request you sent on Thu, 3 Jan 2019 12:02:59 -0800: > git://github.com/andersson/remoteproc tags/hwlock-v4.21 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/66e012f6188fb37b18c774277f34fb52278059c3 Thank you! -- Deet-doot-dot, I am a bot.

Re: [GIT PULL] dma-mapping fixes for Linux 4.21-rc1

The pull request you sent on Sun, 6 Jan 2019 19:28:46 +0100: > git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-4.21-1 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/e2b745f469ec0f3165ba5ffaee3ce40f98d77878 Thank you! -- Deet-doot-dot, I am a bot.

Re: [PATCH] make 'user_access_begin()' do 'access_ok()'

On 1/6/19 11:18 AM, Linus Torvalds wrote: [ Re-sending the message because my first reply bounced - Guenther had mis-typed the lkml address ] Sigh. That _always_ happens to me when typing fast. Sorry. On Sun, Jan 6, 2019 at 10:09 AM Guenter Roeck wrote: All alpha and sh4 (big and little

Re: [PATCH] dmaengine: fsl-edma: use struct_size() in kzalloc()

On 1/6/19 1:40 PM, Angelo Dureghello wrote: On Fri, Jan 04, 2019 at 03:25:45PM -0600, Gustavo A. R. Silva wrote: One of the more common cases of allocation size calculations is finding the size of a structure that has a zero-sized array at the end, along with memory for some number of

Re: r8152: data corruption in various scenarios

On 2019-01-06 2:14 p.m., Kai Heng Feng wrote:>> On Jan 5, 2019, at 10:14 PM, Mark Lord wrote: .. >> There is even now a special hack in the upstream r8152.c to attempt to detect >> a Dell TB16 dock and disable RX Aggregation in the driver to prevent such >> issues. >> >> Well.. I have a WD15

Re: r8152: data corruption in various scenarios

On 2019-01-06 4:13 p.m., Mark Lord wrote: > On 2019-01-06 2:14 p.m., Kai Heng Feng wrote:>> On Jan 5, 2019, at 10:14 PM, > Mark Lord > wrote: > .. >>> There is even now a special hack in the upstream r8152.c to attempt to >>> detect >>> a Dell TB16 dock and disable RX Aggregation in the driver

[RFC PATCH v2] media: rcar-vin: Allow independent VIN link enablement

There is a block of code in rvin_group_link_notify() that loops through all entities in the media graph, and prevents enabling a link to a VIN node if any entity is in use. This prevents enabling a VIN link even if there is an in-use entity somewhere in the graph that is independent of the link's

[BUG] v4.20 - bridge not getting DHCP responses? (works in 4.19.13)

Hi, Switching from 4.19.x -> 4.20 resulted in DHCP not working for my VM:s. My firewall (which also runs the dhcpd) runs VM:s and it does this by having physical interfaces attached to bridges - which the VM:s in turn attach to. Since 4.20 the VM:s can't use DHCP, it's odd since the requests

Re: [GIT PULL] fscrypt update for 4.21

The pull request you sent on Sun, 6 Jan 2019 08:49:12 -0500: > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt.git > tags/fscrypt_for_linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/baa6707381285e68cc472efba58e7e736057aacc Thank you! --

Re: [GIT PULL] ext4 bug fixes for 4.21

The pull request you sent on Sun, 6 Jan 2019 08:39:43 -0500: > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git > tags/ext4_for_linus_stable has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/215240462a9672db771bb60adcc1c4fdf40e8ec4 Thank you! --

Video: Linux and license revocation, in American.

We have noticed that many of you have rejected the very idea of waddling through long written soliloquies on the subject. So, the information in a format that is more accessible to you has been prepared. Video: openload.co/f/mT_AH3xmIUM/TruthAboutLinuxandGPLv2__.mp4 Audio: ufile.io/sdhpl

Re: possible deadlock in nr_destroy_socket

syzbot has found a reproducer for the following crash on: HEAD commit:b71acb0e3721 Merge branch 'linus' of git://git.kernel.org/.. git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=165dec0740 kernel config:

Re: [PATCH] mm/mincore: allow for making sys_mincore() privileged

On Sat, Jan 5, 2019 at 5:50 PM Linus Torvalds wrote: > > Slightly updated patch in case somebody wants to try things out. I decided to just apply that patch. It is *not* marked for stable, very intentionally, because I expect that we will need to wait and see if there are issues with it, and

acpi_string with const char * losing casts

include/acpi/actypes.h:typedef char *acpi_string; /* Null terminated ASCII string */ It seems there are cases where a function with an acpi_string argument should instead use const acpi_string. Some acpi function callers cast const char * to non-const to avoid compiler warnings. It would

Fwd: [BUG] v4.20 - bridge not getting DHCP responses? (works in 4.19.13)

[Sorry for the repost, screwed up the netdev address...] Hi, Switching from 4.19.x -> 4.20 resulted in DHCP not working for my VM:s. My firewall (which also runs the dhcpd) runs VM:s and it does this by having physical interfaces attached to bridges - which the VM:s in turn attach to. Since

Re: [PATCH mips-fixes] MIPS: BCM47XX: Setup struct device for the SoC

Hi Rafał, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.20 next-20190103] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

<<<>>

Good Day, Hope you are doing great Today.I have a proposed BUSINESS DEAL that will benefit both parties. This is legitimate,legal and your personality will not be compromised.Please Reply to me ONLY if you are interested and consider your self capable for details. Sincerely, Peter OWEN

Video: Linux and license revocation, in American. (Yes you can revoke)

We have noticed that many of you have rejected the very idea of waddling through long written soliloquies on the subject. So, the information in a format that is more accessible to you has been prepared. Video: openload.co/f/mT_AH3xmIUM/TruthAboutLinuxandGPLv2__.mp4 Audio: ufile.io/sdhpl

linux-next: manual merge of the csky tree with Linus' tree

Hi Guo, Today's linux-next merge of the csky tree got a conflict in: Documentation/features/io/sg-chain/arch-support.txt between commit: 7c703e54cc71 ("arch: switch the default on ARCH_HAS_SG_CHAIN") from Linus' tree and commit: ee8972b1ab82 ("Documentation/features: Add csky kernel

Re: [PATCH v5 11/15] KVM: s390: restore IAM in get_ipm() when IPM is clean

On Wed, 19 Dec 2018 20:17:52 +0100 Michael Mueller wrote: > The patch adds the parameter irq_flags and allows to > restore the Interruption Alert Mask (IAM) in the GISA > atomically while guaranteeing the IPM is clean. > > The function returns the IPM of the GISA. If the returned > value is

Re: [PATCH v8 24/25] powerpc: Adopt nvram module for PPC64

Arnd Bergmann writes: > On Wed, Dec 26, 2018 at 1:43 AM Finn Thain wrote: > >> +static ssize_t ppc_nvram_get_size(void) >> +{ >> + if (ppc_md.nvram_size) >> + return ppc_md.nvram_size(); >> + return -ENODEV; >> +} > >> +const struct nvram_ops arch_nvram_ops = { >> +

Re: [PATCH 1/2] Input: rotary_encoder - Support key events

On Sat, Jan 5, 2019 at 9:36 PM nazgul33 wrote: > > input_sync() is there, at the end of the function. I know. Nonetheless, you need another one between sending distinct key events. Userspace is allowed to accumulate device state until EV_SYN/SYN_REPORT is received, which can result in your key

[PATCH v2] Poll for monitored tasks being alive in fork mode

Following test shows the stat keeps running even if no longer task to monitor (mgen exits at ~5s). perf stat -e cycles -p `pgrep mgen` -I1000 -- sleep 10 time counts unit events 1.000148916 1,308,365,864 cycles 2.000379171 1,297,269,875 cycles

Re: [GIT PULL] more Kbuild updates for v4.21

The pull request you sent on Sun, 6 Jan 2019 10:59:02 +0900: > git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git > tags/kbuild-v4.21-3 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/85e1ffbd42f664965dc05f6e9851c06379f27fb2 Thank you! --

Re: [GIT PULL] perf tooling updates

The pull request you sent on Fri, 4 Jan 2019 13:09:26 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > perf-urgent-for-linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/ac5eed2b41776b05cf03aac761d3bb5e64eea24c Thank you! -- Deet-doot-dot, I

[PATCH v2 1/2] dmaengine: qcom_hidma: initialize tx flags in hidma_prep_dma_*

In async_tx_test_ack(), it uses flags in struct dma_async_tx_descriptor to check the ACK status. As hidma reuses the descriptor in a free list when hidma_prep_dma_*(memcpy/memset) is called, the flag will keep ACKed if the descriptor has been used before. This will cause a BUG_ON in

[PATCH v2 2/2] dmaengine: qcom_hidma: assign channel cookie correctly

When dma_cookie_complete() is called in hidma_process_completed(), dma_cookie_status() will return DMA_COMPLETE in hidma_tx_status(). Then, hidma_txn_is_success() will be called to use channel cookie mchan->last_success to do additional DMA status check. Current code assigns mchan->last_success

Re: [PATCH v2 1/2] f2fs-dev: support multi-device direct IO

On 2019/1/4 19:24, sunqiuyang wrote: > From: Qiuyang Sun > > Changelog v1 ==> v2: > 1. Modify the definition of update_device_state(), >and call it in direct write; > 2. Move some local variables into branches where they are used. > > Signed-off-by: Qiuyang Sun > --- > fs/f2fs/data.c|

Re: [f2fs-dev] [PATCH v2] f2fs: export FS_NOCOW_FL flag to user

On 2019/1/5 4:44, Jaegeuk Kim wrote: > This exports pin_file status to user. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks,

[PATCH 1/2 v5] kdump: add the vmcoreinfo documentation

This document lists some variables that export to vmcoreinfo, and briefly describles what these variables indicate. It should be instructive for many people who do not know the vmcoreinfo, and it also normalizes the exported variables as a convention between kernel and use-space. Suggested-by:

[PATCH 0/2 v5] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo

This patchset did two things: a. add a new document for vmcoreinfo This document lists some variables that export to vmcoreinfo, and briefly describles what these variables indicate. It should be instructive for many people who do not know the vmcoreinfo, and it also normalizes the exported

[PATCH 2/2 v5] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo

For AMD machine with SME feature, makedumpfile tools need to know whether the crash kernel was encrypted or not. If SME is enabled in the first kernel, the crash kernel's page table(pgd/pud/pmd/pte) contains the memory encryption mask, so need to remove the sme mask to obtain the true physical

Re: [PATCH v5 5/6] dt-bindings: pinctrl: mt8183: add binding document

On Fri, 2019-01-04 at 01:55 -0800, Sean Wang wrote: > On Fri, Jan 4, 2019 at 1:40 AM Zhiyong Tao wrote: > > > > On Fri, 2019-01-04 at 01:14 -0800, Sean Wang wrote: > > > On Thu, Jan 3, 2019 at 11:09 PM Zhiyong Tao > > > wrote: > > > > > > > > On Sat, 2018-12-29 at 06:04 +0800, Rob Herring

RE: [PATCH] [V2] usb: chipidea: add a check for the availability of next child

> > diff --git a/drivers/usb/chipidea/ci_hdrc_msm.c > b/drivers/usb/chipidea/ci_hdrc_msm.c > index 880009987460..813673eee815 100644 > --- a/drivers/usb/chipidea/ci_hdrc_msm.c > +++ b/drivers/usb/chipidea/ci_hdrc_msm.c > @@ -250,6 +250,10 @@ static int ci_hdrc_msm_probe(struct platform_device >

[URGENT FIX PATCH] arch: restore generic-y += shmparam.h for some architectures

For some reasons, I accidentally got rid of "generic-y += shmparam.h" from some architectures. Restore them to fix building c6x, h8300, hexagon, m68k, microblaze, openrisc, and unicore32. Fixes: d6e4b3e326d8 ("arch: remove redundant UAPI generic-y defines") Signed-off-by: Masahiro Yamada ---

[PATCH v2 0/5] qcom: spmi: add support for hierarchical IRQ chip

This patch series adds hierarchical IRQ chip support to spmi-gpio so that device tree consumers can request an IRQ directly from the GPIO block rather than having to request an IRQ from the underlying PMIC. The first two patches in this series removes some IRQ count code that was causing the IRQs

[PATCH v2 5/5] ARM: dts: qcom: msm8974: add interrupt controller properties

Add interrupt controller properties now that spmi-gpio is a proper hierarchical IRQ chip. The interrupts property is no longer needed so remove it. Signed-off-by: Brian Masney --- Changes since v1: - Interrupts are now two cells instead of four cells. - Drop unnecessary interrupts property.

[PATCH v2 1/5] spmi: pmic-arb: hardcode IRQ counts

The probing of this driver calls platform_irq_count, which will setup all of the IRQs that are available. This is a problem since some of these IRQs may be setup in an IRQ hierarchy later in the boot process by spmi-gpio. This will cause these hwirqs to be associated with multiple Linux virqs and

[PATCH v2 3/5] spmi: pmic-arb: convert to v2 irq interfaces to support hierarchical IRQ chips

Convert the spmi-pmic-arb IRQ code to use the version 2 IRQ interface in order to support hierarchical IRQ chips. This is necessary so that spmi-gpio can be setup as a hierarchical IRQ chip with pmic-arb as the parent. IRQ chips in device tree should be usable from the start without the consumer

[PATCH v2 4/5] qcom: spmi-gpio: add support for hierarchical IRQ chip

spmi-gpio did not have any irqchip support so consumers of this in device tree would need to call gpio[d]_to_irq() in order to get the proper IRQ on the underlying PMIC. IRQ chips in device tree should be usable from the start without the consumer having to make an additional call to get the

[PATCH v2 2/5] mfd: qcom-spmi-pmic: use devm_mfd_add_devices instead of devm_of_platform_populate

pmic_spmi_probe calls devm_of_platform_populate, which traverses all of the children in device tree from the parent down to the children, grandchildren, etc. of_irq_count is called on most of the nodes (via of_device_alloc) and this initializes all of the IRQs. Further along in the boot process,

Re: [PATCH RFC 1/2] virtio-net: bql support

On 2019/1/2 下午9:59, Michael S. Tsirkin wrote: On Wed, Jan 02, 2019 at 11:28:43AM +0800, Jason Wang wrote: On 2018/12/31 上午2:45, Michael S. Tsirkin wrote: On Thu, Dec 27, 2018 at 06:00:36PM +0800, Jason Wang wrote: On 2018/12/26 下午11:19, Michael S. Tsirkin wrote: On Thu, Dec 06, 2018 at

Linux 5.0-rc1

So this was a fairly unusual merge window with the holidays, and as a result I'm not even going to complain about the pull requests that ended up coming in late. It all mostly worked out fine, I think. And lot of people got their pull requests in early, and hopefully had a calm holiday season.

linux-next: manual merge of the akpm-current tree with Linus' tree

Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: mm/mincore.c between commit: 574823bfab82 ("Change mincore() to count "mapped" pages rather than "cached" pages") from Linus' tree and commit: 86ee23ad82b6 ("mm: fix race between swapoff and mincore") from

[PATCH] nvme: fix out of bounds access in nvme_cqe_pending

There is an out of bounds array access in nvme_cqe_peding(). When enable irq_thread for nvme interrupt, there is racing between the nvmeq->cq_head updating and reading. nvmeq->cq_head is updated in nvme_update_cq_head(), if nvmeq->cq_head equals nvmeq->q_depth and before its value set to zero,

Re: [RFC PATCH V3 0/5] Hi:

On 2019/1/3 上午4:47, Michael S. Tsirkin wrote: On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote: This series tries to access virtqueue metadata through kernel virtual address instead of copy_user() friends since they had too much overheads like checks, spec barriers or even hardware

[PATCH v3 1/2] f2fs-dev: support multi-device direct IO

From: Qiuyang Sun Changelog v1 ==> v2: 1. Modify the definition of update_device_state(), and call it in direct write; 2. Move some local variables into branches where they are used. Changelog v2 ==> v3: Rename update_device_state() to f2fs_update_device_state() like other exported function

Re: [URGENT FIX PATCH] arch: restore generic-y += shmparam.h for some architectures

On Sun, Jan 6, 2019 at 6:08 PM Masahiro Yamada wrote: > > Could you pick up this directly? > Apology for breakage. Oops. I just made rc1. But sure, I'll pick it up. Everybody is likely using the git tree anyway, rather than some random release patches and tarballs. Linus

Re: [snd_hda_intel] snd_hda_intel causes high CPU lockup and system instability if mic disabled in BIOS on Lenovo P50

On Wed, 5 Dec 2018, Takashi Iwai wrote: On Sat, 01 Dec 2018 20:33:16 +0100, Alexander Kappner wrote: On Tue, 27 Nov 2018, Takashi Iwai wrote: On Tue, 27 Nov 2018 06:34:02 +0100, Alexander Kappner wrote: On Mon, 26 Nov 2018, Takashi Iwai wrote: On Mon, 26 Nov 2018 00:17:15 +0100,

RE: [PATCH][next] media: cxd2880-spi: fix two memory leaks of dvb_spi

Hi Colin Thanks for finding that. Acked-by: Yasunari Takiguchi 　 Takiguchi > -Original Message- > From: Colin King [mailto:colin.k...@canonical.com] > Sent: Saturday, December 22, 2018 11:12 PM > To: Takiguchi, Yasunari (SSS); Mauro Carvalho Chehab; > linux-me...@vger.kernel.org > Cc:

Re: [PATCH v2] f2fs: fix sbi->extent_list corruption issue

On 2019/1/5 4:33, Jaegeuk Kim wrote: > On 01/04, Sahitya Tummala wrote: >> On Mon, Nov 26, 2018 at 10:17:20AM +0530, Sahitya Tummala wrote: >>> When there is a failure in f2fs_fill_super() after/during >>> the recovery of fsync'd nodes, it frees the current sbi and >>> retries again. This time the

Re: [PATCH 2/2 v5] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo

On 01/07/19 at 09:47am, Lianbo Jiang wrote: > For AMD machine with SME feature, makedumpfile tools need to know > whether the crash kernel was encrypted or not. If SME is enabled ^ crashed > in the first kernel, the crash kernel's page table(pgd/pud/pmd/pte)

[PATCH v2] vti4: Fix a ipip packet processing bug in 'IPCOMP' virtual tunnel

Recently we run a network test over ipcomp virtual tunnel.We find that if a ipv4 packet needs fragment, then the peer can't receive it. We deep into the code and find that when packet need fragment the smaller fragment will be encapsulated by ipip not ipcomp. So when the ipip packet goes into

Re: [PATCH -next] media: staging/intel-ipu3: Fix err handle of ipu3_css_find_binary

Hi, Haibing Thanks for your patch, it looks fine for me. Reviewed-by: Bingbu Cao On 12/29/2018 10:45 AM, YueHaibing wrote: css->pipes[pipe].bindex = binary;

Re: [PATCH v3 1/2] f2fs-dev: support multi-device direct IO

On 2019/1/7 10:19, sunqiuyang wrote: > From: Qiuyang Sun > > Changelog v1 ==> v2: > 1. Modify the definition of update_device_state(), >and call it in direct write; > 2. Move some local variables into branches where they are used. > > Changelog v2 ==> v3: > Rename update_device_state() to

Re: [PATCH 1/4] pmbus: associate PMBUS_SKIP_STATUS_CHECK with driver_data

Hi, Guenter, Thanks for reply. On 2019/1/4 22:54, Guenter Roeck wrote: > On 1/4/19 12:55 AM, Xiaoting Liu wrote: >> Current code compares device name with name in i2c_device_id to decide >> whether PMBUS_SKIP_STATUS_CHECK should be set in pmbus_platform_data, >> which makes adding new devices

Linux and license revocation, a discussion in American. (Audio/Video)

We have noticed that many of you have rejected the very idea of waddling through long written soliloquies on the subject. So, the information in a format that is more accessible to you has been prepared. Video: openload.co/f/mT_AH3xmIUM/TruthAboutLinuxandGPLv2__.mp4 Audio: ufile.io/sdhpl

[PATCH] ACPI/nfit: delete the redundant header file

From: Xiaochun Lee The header file "intel.h" is repeated here, So delete one. Xiaochun Lee (1): ACPI/nfit: delete the redundant header file drivers/acpi/nfit/core.c | 1 - 1 file changed, 1 deletion(-) -- 1.8.3.1

[PATCH] ACPI/nfit: delete the redundant header file

From: Xiaochun Lee The header file "intel.h" is repeated here, So delete one. Signed-off-by: Xiaochun Lee --- drivers/acpi/nfit/core.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/acpi/nfit/core.c b/drivers/acpi/nfit/core.c index 011d3db..328e464 100644 ---

[PATCH v7 01/22] asm-generic/syscall.h: prepare for inclusion by other files

>From the very beginning and up to now asm-generic/syscall.h is used for documentation purposes only, it could not be included by arch-specific asm/syscall.h files due to static/non-static conflict of function prototypes. Cc: Arnd Bergmann Cc: Oleg Nesterov Cc: Geert Uytterhoeven Cc: Elvira

[PATCH v7 02/22] asm-generic/syscall.h: turn syscall_[gs]et_arguments into wrappers

Add a generic wrapper syscall_get_arguments() that checks its arguments and calls arch-specific __syscall_get_arguments(). Likewise, add a generic wrapper syscall_set_arguments() that checks its arguments and calls arch-specific __syscall_set_arguments(). This is the first step on the way of

[PATCH v7 04/22] Move EM_ARCOMPACT and EM_ARCV2 to uapi/linux/elf-em.h

These should never have been defined in the arch tree to begin with, and now uapi/linux/audit.h header is going to use EM_ARCOMPACT and EM_ARCV2 in order to define AUDIT_ARCH_ARCOMPACT and AUDIT_ARCH_ARCV2 which are needed to implement syscall_get_arch() which in turn is required to extend the

[PATCH v7 03/22] alpha: define remaining syscall_get_* functions

syscall_get_* functions are required to be implemented on all architectures in order to extend the generic ptrace API with PTRACE_GET_SYSCALL_INFO request. This adds remaining 4 syscall_get_* functions as documented in asm-generic/syscall.h: syscall_get_nr, syscall_get_arguments,

[PATCH v7 07/22] h8300: define remaining syscall_get_* functions

syscall_get_* functions are required to be implemented on all architectures in order to extend the generic ptrace API with PTRACE_GET_SYSCALL_INFO request. This adds remaining 3 syscall_get_* functions as documented in asm-generic/syscall.h: syscall_get_error, syscall_get_return_value, and

[PATCH v7 05/22] arc: define syscall_get_arch()

syscall_get_arch() is required to be implemented on all architectures in addition to already implemented syscall_get_nr(), syscall_get_arguments(), syscall_get_error(), and syscall_get_return_value() functions in order to extend the generic ptrace API with PTRACE_GET_SYSCALL_INFO request.

[PATCH v7 09/22] hexagon: define remaining syscall_get_* functions

syscall_get_* functions are required to be implemented on all architectures in order to extend the generic ptrace API with PTRACE_GET_SYSCALL_INFO request. This adds remaining 3 syscall_get_* functions as documented in asm-generic/syscall.h: syscall_get_error, syscall_get_return_value, and

[PATCH v7 06/22] c6x: define syscall_get_arch()

syscall_get_arch() is required to be implemented on all architectures in addition to already implemented syscall_get_nr(), syscall_get_arguments(), syscall_get_error(), and syscall_get_return_value() functions in order to extend the generic ptrace API with PTRACE_GET_SYSCALL_INFO request.

[PATCH v7 08/22] Move EM_HEXAGON to uapi/linux/elf-em.h

This should never have been defined in the arch tree to begin with, and now uapi/linux/audit.h header is going to use EM_HEXAGON in order to define AUDIT_ARCH_HEXAGON which is needed to implement syscall_get_arch() which in turn is required to extend the generic ptrace API with

[PATCH v7 12/22] nios2: define syscall_get_arch()

syscall_get_arch() is required to be implemented on all architectures in addition to already implemented syscall_get_nr(), syscall_get_arguments(), syscall_get_error(), and syscall_get_return_value() functions in order to extend the generic ptrace API with PTRACE_GET_SYSCALL_INFO request.

[PATCH v7 10/22] Move EM_NDS32 to uapi/linux/elf-em.h

This should never have been defined in the arch tree to begin with, and now uapi/linux/audit.h header is going to use EM_NDS32 in order to define AUDIT_ARCH_NDS32 which is needed to implement syscall_get_arch() which in turn is required to extend the generic ptrace API with PTRACE_GET_SYSCALL_INFO

<    1   2   3   4   >