pm_runtime_get_sync() increments the runtime PM usage counter even
when it returns an error code. Thus a pairing decrement is needed on
the error handling path to keep the counter balanced. For other error
paths after this call, things are the same.
Fix this by adding pm_runtime_put_noidle()
Jianyong Wu wrote on Sun, Jun 28, 2020:
> These code has been commented out since 2007 and lied in kernel
> since then. it's time to remove thest no used code.
Good point, happy to take this - please resend without RFC separately
(the two commits aren't related) after fixing the commit message
On Thu, Jun 25, 2020 at 5:47 PM H. Nikolaus Schaller wrote:
>
> strsep() is neither standard C nor POSIX and used outside
> the kernel code here. Using it here requires that the
> build host supports it out of the box which is e.g.
> not true for a Darwin build host and using a cross-compiler.
>
On Fri, Jun 26, 2020 at 8:43 AM Peter Zijlstra wrote:
>
> I ended up with something like the below.. but it is too warm to think
> properly.
>
> I don't particularly like WQ_FLAG_PAGEWAITERS, but I liked open-coding
> all that even less.
Ugh.
I think I have a much simpler approach, actually.
>
> Could you reword this and add it to the patch description.
>
Fine. I will fix this in the next version of patch.
Regards,
Dinghao
> -Original Message-
> From: Ben Greear
> Sent: Saturday, June 27, 2020 8:58 PM
> To: Rakesh Pillai ; ath...@lists.infradead.org
> Cc: linux-wirel...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] ath10k: Add history for tracking certain events
>
>
>
> On
From: Sven Van Asbroeck Sent: Thursday, June 25, 2020
10:01 PM
> On imx6, the ethernet reference clock (clk_enet_ref) can be generated by
> either the imx6, or an external source (e.g. an oscillator or the PHY). When
> generated by the imx6, the clock source (from ANATOP) must be routed to the
>
Fixed a coding style issue.
Signed-off-by: B K Karthik
---
drivers/staging/media/atomisp/i2c/atomisp-ov2680.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/media/atomisp/i2c/atomisp-ov2680.c
b/drivers/staging/media/atomisp/i2c/atomisp-ov2680.c
index
Userspace applications may use /dev/adb to send Talk requests. Such
requests always have req->reply_expected == 1. The same is true of Talk
requests sent by the kernel, except for poll requests queued internally
by the via-macii driver. Those requests have req->reply_expected == 0.
Consequently,
Various issues with the via-macii driver have become apparent over the
years. Some examples:
- A Talk command response can be lost. This can result in phantom devices
being probed or an incorrect device handler ID being retrieved.
- A reply packet containing a null byte can get truncated. Such
Poll the most recently polled device by default, rather than the lowest
device address that happens to be enabled in autopoll_devs. This improves
input latency. Re-use macii_queue_poll() rather than duplicate that logic.
This eliminates a static struct and function.
Fixes: d95fd5fce88f0 ("m68k:
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/macintosh/via-macii.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/macintosh/via-macii.c b/drivers/macintosh/via-macii.c
index 8d5ef77b4a435..e143ddb81de34 100644
---
The driver state machine may enter the 'read_done' state when leaving the
'idle' or 'reading' state. This transition is pointless, as is the extra
interrupt it requires. The interrupt is produced by the transceiver
(even when it has no data to send) because an extra EVEN/ODD toggle
was signalled
The adb_request struct can be stored on the stack because the request
is synchronous and is completed before the function returns.
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/macintosh/via-macii.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/macintosh/via-macii.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/macintosh/via-macii.c b/drivers/macintosh/via-macii.c
index e143ddb81de34..447273967e1e8 100644
--- a/drivers/macintosh/via-macii.c
The function prototype correctly specifies the 'static' storage class.
Let the function definition match the declaration for better readability.
Signed-off-by: Finn Thain
---
drivers/macintosh/via-macii.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The interrupt handler should be excluded when accessing the autopoll_devs
variable.
Fixes: d95fd5fce88f0 ("m68k: Mac II ADB fixes") # v5.0+
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/macintosh/via-macii.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff
I'm told that the /CTLR_IRQ signal from the ADB transceiver gets
interpreted by MacOS to mean SRQ, bus timeout or end-of-packet depending
on the circumstances, and that Linux's via-macii driver does not
correctly interpret this signal.
Instead, the via-macii driver interprets certain received
On Sun, 21 Jun 2020, Guenter Roeck wrote:
> > When a DMA coherent pool is depleted, allocation failures may or may not
> > get reported in the kernel log depending on the allocator.
> >
> > The admin does have a workaround, however, by using coherent_pool= on the
> > kernel command line.
> >
>
On Sat, 27 Jun 2020, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: c91e241f569e7f9b0e2946841ef884b22a09f624 ("mm, slub: introduce
> kmem_cache_debug_flags()-fix")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git
> -Original Message-
> From: Alex Williamson
> Sent: Sunday, June 28, 2020 12:09
> To: Wang, Haiyue
> Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org;
> maxime.coque...@redhat.com; David Marchand
> ; Kevin Traynor
> Subject: Re: [PATCH] vfio/pci: Fix SR-IOV VF handling with MMIO
On 2020/6/26 7:24, Bjorn Helgaas wrote:
> On Wed, Jun 24, 2020 at 06:23:09PM -0500, Bjorn Helgaas wrote:
>> On Tue, Dec 10, 2019 at 11:15:27AM +0800, Xiang Zheng wrote:
>>> 7ea7e98fd8d0 ("PCI: Block on access to temporarily unavailable pci
>>> device") suggests that the "pci_lock" is
Hi Bjorn,
Sorry for the late reply, I had Dragon Boat Festival these days.
On 2020/6/25 7:23, Bjorn Helgaas wrote:
> On Tue, Dec 10, 2019 at 11:15:27AM +0800, Xiang Zheng wrote:
>> 7ea7e98fd8d0 ("PCI: Block on access to temporarily unavailable pci
>> device") suggests that the "pci_lock" is
On Sun, 28 Jun 2020 03:12:12 +
"Wang, Haiyue" wrote:
> > -Original Message-
> > From: kvm-ow...@vger.kernel.org On Behalf Of
> > Alex Williamson
> > Sent: Friday, June 26, 2020 00:57
> > To: alex.william...@redhat.com
> > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org;
> >
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 916a3b0fc1206f7e7ae8d00a21a3114b1dc67794
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 9 days ago
config: x86_64-randconfig-s031-20200628
On Sat, Jun 27, 2020 at 9:25 PM Domenico Andreoli
wrote:
>
> From: Domenico Andreoli
>
> Make 'make tar-pkg' install dtbs.
>
> v4:
> - Install the dtbs before modules & kernel, not after
> - Check for the dtbs_install target before attempting to invoke it
>
> v3:
> - Check for
On Sun, Jun 28, 2020 at 6:21 AM Domenico Andreoli
wrote:
>
> On Sat, Jun 27, 2020 at 09:02:52PM +0900, Masahiro Yamada wrote:
> > On Sat, Jun 27, 2020 at 6:40 AM Domenico Andreoli
> > wrote:
> > > On Fri, Jun 26, 2020 at 03:16:58PM +0900, Masahiro Yamada wrote:
> > > > On Fri, Jun 26, 2020 at
syzbot has found a reproducer for the following crash on:
HEAD commit:1590a2e1 Merge tag 'acpi-5.8-rc3' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=164b959b10
kernel config:
On 06/24/2020 08:08 PM, Markus Elfring wrote:
How do you think about to extend source code analysis tools accordingly?
I have no good idea,
maybe some simple match check tools can do this.
Would you like to help with any additional software development resources
(besides your current
Fixed an inconsistent use of GFP flags in nft_obj_notify() that used
GFP_KERNEL when a GFP flag was passed in to that function. Given this
allocated memory was then used in audit_log_nfcfg() it led to an audit
of all other GFP allocations in net/netfilter/nf_tables_api.c and a
modification of
On 06/24/2020 09:12 PM, Markus Elfring wrote:
There exists potential resource leaks in the error path, fix them.
Would you like to reconsider this change description?
https://lore.kernel.org/linux-mips/be3acb13-2963-ddf1-a867-7e30fd23a...@loongson.cn/
https://lkml.org/lkml/2020/6/24/498
…
> -Original Message-
> From: kvm-ow...@vger.kernel.org On Behalf Of Alex
> Williamson
> Sent: Friday, June 26, 2020 00:57
> To: alex.william...@redhat.com
> Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org;
> maxime.coque...@redhat.com
> Subject: [PATCH] vfio/pci: Fix SR-IOV VF
Hallo, ich habe ein Geschäft von 24,5 Mio. USD, das ich mit Ihnen teilen kann.
Wenn Sie interessiert sind? Bitte schreibe zurück und ich werde dir mehr
Details geben.
Grüße,
William.
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Hi Luca,
On Sat, Jun 27, 2020 at 09:02:30PM +0200, Luca Stefani wrote:
> If the kernel is built with CFI we hit a __cfi_check_fail
> while mounting a partition
>
> Call trace:
> __cfi_check_fail+0x1c/0x24
> name_to_dev_t+0x0/0x404
> iget5_locked+0x594/0x5e8
> ntfs_fill_super+0xbfc/0x43ec
>
On Sat, 27 Jun 2020 16:20:02 +
guo...@kernel.org wrote:
> From: Guo Ren
>
> Unfortunately, the current code couldn't be compiled, because
> BUILD_BUG_ON needs a static defined value, not a dynamic
> variable with a0 regs. Just use it inline as a solution.
>
> CC
- Add to account and show per-log dirty_seg, full_seg and valid_blocks
in debugfs.
- reformat printed info.
TYPEsegnosecno zoneno dirty_seg full_seg valid_blk
- COLD data: 1523 1523 1523 1 0399
- WARM data: 769 769
Filesystem including f2fs should support stable page for special
device like software raid, however there is one missing path that
page could be updated while it is writeback state as below, fix
this.
- gc_node_segment
- f2fs_move_node_page
- __write_node_page
- set_page_writeback
-
On 2020/6/26 22:39, Liu Song via Linux-f2fs-devel wrote:
> From: Liu Song
>
> The value of state must be equal to FREE_NID, so the if
> condition judgment can be removed.
>
> Signed-off-by: Liu Song
> ---
> fs/f2fs/node.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 916a3b0fc1206f7e7ae8d00a21a3114b1dc67794
commit: 8e20fc3917117b42de316e87f073a1ca43d94c9f serial_core: Move sysrq
functions from header file
date: 6 months ago
config: arm64-randconfig-s032-20200628
On 6/26/20 1:21 PM, Andy Lutomirski wrote:
> The SYSENTER frame setup was nonsense. It worked by accident
> because the normal code into which the Xen asm jumped
> (entry_SYSENTER_32/compat) threw away SP without touching the stack.
> entry_SYSENTER_compat was recently modified such that it
Hello,
syzbot found the following crash on:
HEAD commit:1590a2e1 Merge tag 'acpi-5.8-rc3' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1070059b10
kernel config: https://syzkaller.appspot.com/x/.config?x=20c907630cbdbe5
On 2020-06-26 08:44, Alan Stern wrote:
> On Fri, Jun 26, 2020 at 08:07:51AM -0700, Bart Van Assche wrote:
>> As far as I know runtime power management support in the sd driver is working
>> fine and is being used intensively by the UFS driver. The following commit
>> was
>> submitted to fix a bug
On 2020/6/25 20:40, Liu Song via Linux-f2fs-devel wrote:
> stakable/stackable
>
> Signed-off-by: Liu Song
Reviewed-by: Chao Yu
Thanks,
On 2020/6/24 9:21, Jaegeuk Kim wrote:
> If two readahead threads having same offset enter in readpages, every read
> IOs are split and issued to the disk which giving lower bandwidth.
>
> This patch tries to avoid redundant readahead calls.
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/data.c
Hi Hari,
If in [4/11], get_exclude_memory_ranges() turns out to be unnecessary
,then this patch is abundant either. As my understanding, memblock has
already helped to achieved the purpose that get_exclude_memory_ranges()
wants.
Thanks,
Pingfan
On 06/27/2020 03:04 AM, Hari Bathini wrote:
>
On Thu, Jun 25, 2020 at 11:53 PM Mauro Carvalho Chehab
wrote:
>
> The logic handling find on split mode is currently broken.
> Fix it, making it work again as expected.
>
> Reported-by: Maxim Levitsky
> Signed-off-by: Mauro Carvalho Chehab
> ---
Applied to linux-kbuild.
Thanks.
>
Hi Hari,
After a quick through for this series, I have a few question/comment on
this patch for the time being. Pls see comment inline.
On 06/27/2020 03:05 AM, Hari Bathini wrote:
> crashkernel region could have an overlap with special memory regions
> like opal, rtas, tce-table & such. These
These code has been commented out since 2007 and lied in kernel
since then. it's time to remove thest no used code.
Signed-off-by: Jianyong Wu
---
fs/9p/vfs_inode.c | 53 ---
1 file changed, 53 deletions(-)
diff --git a/fs/9p/vfs_inode.c
In the current setattr implementation in 9p, fid will always retrieved from
dentry no matter file instance exist or not when setattr. There will
be some info related to open file instance dropped. so it's better
to retrieve fid from file instance if file instance is passed to setattr.
for
in the current implementation in setattr in 9p, fid will always be retrieved
from dentry, which may be against the original intension of user and lead to
bug.
also, remove no used code in 9p.
Signed-off-by: Jianyong Wu
Jianyong Wu (2):
9p: retrive fid from file when file instance exist.
9p:
Hi Dan,
> -Original Message-
> From: Dan Carpenter
> On Sat, Jun 27, 2020 at 10:51:44PM +0530, Alim Akhtar wrote:
> > Hi Dan
> >
> > > -Original Message-
> > > The "head" pointer can't be NULL because it points to an address in
the
> > middle
> > > of a ufs_hba struct. Looking
CFLAGS_REMOVE_.o works per object, that is, there is no
convenient way to filter out flags for every object in a directory.
Add ccflags-remove-y and asflags-remove-y to make it easily.
Use ccflags-remove-y to clean up some Makefiles.
Suggested-by: Sami Tolvanen
Signed-off-by: Masahiro Yamada
Hi Jonas Karlman,
在 2020/6/26 22:19, Jonas Karlman 写道:
On 2020-06-17 14:07, Huang Jiachai wrote:
Hi Jonas Karlman,
Is there an another yuv 10bit format with 4:4:4 sub-simpling but
has no padding?
Maybe we can call it DRM_FORMAT_NV30:
{ .format = DRM_FORMAT_NV30,.depth =
From: Zqiang
After the device is disconnected from the host side, the interface of
the device is reset. If the userspace operates the device again,
an error code should be returned.
Signed-off-by: Zqiang
---
drivers/usb/gadget/function/f_printer.c | 36 +
1 file
Current police action must set 'rate' and 'burst'. 'mtu' parameter
set the max frame size and could be set alone without 'rate' and 'burst'
in some situation. Offloading to hardware for example, 'mtu' could limit
the flow max frame size.
Signed-off-by: Po Liu
---
tc/m_police.c | 4 ++--
1 file
On 2020/6/25 6:31, Jaegeuk Kim wrote:
> On 06/18, Chao Yu wrote:
>> - Add to account and show per-log dirty_seg, full_seg and valid_blocks
>> in debugfs.
>> - reformat printed info.
>>
>> TYPEsegnosecno zoneno dirty_seg full_seg valid_blk
>> - COLD data: 1523
Hi John,
I love your patch! Yet something to improve:
[auto build test ERROR on pinctrl/devel]
[also build test ERROR on linux/master linus/master v5.8-rc2 next-20200626]
[cannot apply to tip/irq/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting
From: Yubo Feng
There is no necessery to hold write_lock in fat_ioctl_get_attributes.
write_lock may make an impact on concurrency of fat_ioctl_get_attributes.
Signed-off-by: Yubo Feng
---
fs/fat/file.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/fat/file.c
On 2020/6/24 23:55, Jaegeuk Kim wrote:
> On 06/22, Chao Yu wrote:
>> On 2020/6/22 0:38, Jaegeuk Kim wrote:
>>> On 06/20, Chao Yu wrote:
On 2020/6/20 6:47, Jaegeuk Kim wrote:
> On 06/19, Chao Yu wrote:
>> On 2020/6/19 13:49, Jaegeuk Kim wrote:
>>> On 06/19, Chao Yu wrote:
From: Bin Meng
Drop CONFIG_MTD_M25P80 that was removed in
commit b35b9a10362d ("mtd: spi-nor: Move m25p80 code in spi-nor.c")
Signed-off-by: Bin Meng
---
Changes in v2:
- add CONFIG_MTD_SPI_NOR=y in axm55xx_defconfig
arch/arm/configs/axm55xx_defconfig | 2 +-
发件人: linux-usb-ow...@vger.kernel.org 代表
qiang.zh...@windriver.com
发送时间: 2020年6月15日 17:46
收件人: ba...@kernel.org
抄送: gre...@linuxfoundation.org; linux-...@vger.kernel.org;
linux-kernel@vger.kernel.org
主题: [PATCH] usb: gadget: function: printer: Add
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.I am confident that both of us can work out this transaction
perfectly well to the benefit of both parties. Reach to me
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 42afe7d1c6ef77212250af3459e549d1a944cc8a
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 9 days ago
config: riscv-randconfig-s031-20200628 (attached
From: linmiaohe
Date: Sat, 27 Jun 2020 15:47:51 +0800
> From: Miaohe Lin
>
> We can't cast sk_buff to rtable by (struct rtable *)hint. Use skb_rtable().
>
> Fixes: 02b24941619f ("ipv4: use dst hint for ipv4 list receive")
>
> Signed-off-by: Miaohe Lin
Please do not put empty lines between
On 6/19/2020 8:26 AM, Jason Gunthorpe wrote:
On Sat, Jun 13, 2020 at 04:19:03AM +0800, kernel test robot wrote:
Fixes: 8a69220b659c ("RDMA/qedr: Fix synchronization methods and memory leaks in
qedr")
Signed-off-by: kernel test robot
---
qedr_iw_cm.c |2 +-
1 file changed, 1
Fix the following sparse warning:
arch/arm64/xen/../../arm/xen/enlighten.c:244: warning: macro
"GRANT_TABLE_PHYSADDR" is not used [-Wunused-macros]
It is an isolated macro, and should be removed when its last user
was deleted in the following commit 3cf4095d7446 ("arm/xen: Use
On 2020/6/28 8:52, David Miller wrote:
> From: Luo bin
> Date: Sat, 27 Jun 2020 14:52:37 +0800
>
>> patch #1: support to set and get pause params with
>> "ethtool -A/a" cmd
>> patch #2: support to set and get irq coalesce params with
>> "ethtool -C/c" cmd
>> patch #3: support
On 6/26/20 3:07 AM, Christoph Hellwig wrote:
> The code handling non-coherent DMA depends on being able to remap code
> as non-cached. But that can't be done without an MMU, so using this
> option on NOMMU builds is broken.
I'm working on a nommu j-core board that's doing DMA behind the OS's
Hi Will，
My apologies for reply later because of a short holiday in China.
在 2020/6/24 18:55, Will Deacon 写道:
> On Wed, Jun 24, 2020 at 05:08:56PM +0800, Shaokun Zhang wrote:
>> +Will Deacon,
>>
>> Hi Will,
>>
>> There's a build failure on arm64:
>>
>> CALLscripts/atomic/check-atomics.sh
From: Luo bin
Date: Sat, 27 Jun 2020 14:52:37 +0800
> patch #1: support to set and get pause params with
> "ethtool -A/a" cmd
> patch #2: support to set and get irq coalesce params with
> "ethtool -C/c" cmd
> patch #3: support to do self test with "ethtool -t" cmd
> patch #4:
> On Jun 27, 2020, at 7:10 PM, Eric Biggers wrote:
>
> This bug also got reported 2 days later by the kernel test robot
> (lore.kernel.org/lkml/20200623090213.GW5535@shao2-debian/).
> Then it was fixed by commit 437edcaafbe3, so telling syzbot:
>
> #syz fix: mm, slab/slub: improve error
After a page request is handled, software must response the device which
raised the page request with the handling result. This is done through
the iommu ops.page_response if the request was reported to outside of
vendor iommu driver through iommu_report_device_fault(). This adds the
VT-d
Hi,
This series adds page request event reporting and response support to
the Intel IOMMU driver. This is necessary when the page requests must
be processed by any component other than the vendor IOMMU driver. For
example, when a guest page table was bound to a PASID through the
There are several places in the code that need to get the pointers of
svm and sdev according to a pasid and device. Add a helper to achieve
this for code consolidation and readability.
Signed-off-by: Lu Baolu
---
drivers/iommu/intel/svm.c | 121 +-
1 file
It is refactored in two ways:
- Make it global so that it could be used in other files.
- Make bus/devfn optional so that callers could ignore these two returned
values when they only want to get the coresponding iommu pointer.
Signed-off-by: Lu Baolu
---
drivers/iommu/intel/iommu.c | 55
A pasid might be bound to a page table from a VM guest via the iommu
ops.sva_bind_gpasid. In this case, when a DMA page fault is detected
on the physical IOMMU, we need to inject the page fault request into
the guest. After the guest completes handling the page fault, a page
response need to be
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 4e99b32169e84b4ece5a1d74eb0b7e4ef07866b3
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to
define address spaces
date: 9 days ago
config: arm64-randconfig-s031-20200628 (attached
in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/B-K-Karthik/fbtft-bus-c-Removing-that-prohibited-space-before/20200627-125315
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
92cd1b5d65f5c67147c7da39a3c2ad7e6ff81027
config: x86_64
On 6/26/20 3:39 PM, Tyler Hicks wrote:
Take the properties of the kexec kernel's inode and the current task
ownership into consideration when matching a KEXEC_CMDLINE operation to
the rules in the IMA policy. This allows for some uniformity when
writing IMA policy rules for KEXEC_KERNEL_CHECK,
Hallo, ich habe ein Geschäft von 24,5 Mio. USD, das ich mit Ihnen teilen kann.
Wenn Sie interessiert sind? Bitte schreibe zurück und ich werde dir mehr
Details geben.
Grüße,
William.
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
On 6/26/20 3:38 PM, Tyler Hicks wrote:
Use ima_validate_rule() to ensure that the combination of a hook
function and the keyrings conditional is valid and that the keyrings
conditional is not specified without an explicit KEY_CHECK func
conditional. This is a code cleanup and has no user-facing
On Sat, Jun 27, 2020 at 03:14:14PM -0700, Andy Lutomirski wrote:
>
> > On Jun 27, 2020, at 2:46 PM, Paul E. McKenney wrote:
> >
> > On Sat, Jun 27, 2020 at 02:02:15PM -0700, Andy Lutomirski wrote:
> >>> On Fri, Jun 26, 2020 at 2:05 PM Paul E. McKenney
> >>> wrote:
> >>>
> >>> Currently,
27.06.2020 23:43, Laurent Pinchart пишет:
> Hi Dmitry,
>
> Thank you for the patch.
>
> On Mon, Jun 22, 2020 at 01:27:42AM +0300, Dmitry Osipenko wrote:
>> This patch adds missing BUS fields to the display panel descriptions of
>> the panels which are found on NVIDIA Tegra devices:
>>
>> 1.
On 6/26/20 3:38 PM, Tyler Hicks wrote:
The KEXEC_CMDLINE hook function only supports the pcr conditional. Make
this clear at policy load so that IMA policy authors don't assume that
other conditionals are supported.
Since KEXEC_CMDLINE's inception, ima_match_rules() has always returned
true on
On 6/26/20 3:38 PM, Tyler Hicks wrote:
The KEY_CHECK function only supports the uid, pcr, and keyrings
conditionals. Make this clear at policy load so that IMA policy authors
don't assume that other conditionals are supported.
Fixes: 5808611cccb2 ("IMA: Add KEY_CHECK func to measure keys")
On Sat, Jun 27, 2020 at 5:48 AM Arnaldo Carvalho de Melo
wrote:
>
> Em Fri, Jun 26, 2020 at 02:57:59PM -0700, Andi Kleen escreveu:
> > > The name could be a metric or an event, the logic for each is quite
> >
> > I would say collisions are unlikely. Event names follow quite structured
> >
[+Cc linux-mm; +Bcc linux-fsdevel]
On Mon, Jun 22, 2020 at 03:28:09AM -0400, Qian Cai wrote:
>
>
> > On Jun 22, 2020, at 2:42 AM, Dmitry Vyukov wrote:
> >
> > There is a reason, it's still important for us.
> > But also it's not our strategy to deal with bugs by not testing
> > configurations
The pull request you sent on Sat, 27 Jun 2020 15:11:00 -0500:
> git://git.samba.org/sfrench/cifs-2.6.git tags/5.8-rc2-smb3-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/916a3b0fc1206f7e7ae8d00a21a3114b1dc67794
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sat, 27 Jun 2020 20:20:57 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8bf9865187f6c3130b5c748a3212d591c9d563de
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sat, 27 Jun 2020 08:25:18 -0600:
> git://github.com/awilliam/linux-vfio.git tags/vfio-v5.8-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c322f5399fc36300ae870db8fbcf793e063aaae5
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sat, 27 Jun 2020 10:35:24 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3cd1c5d582f42fead949947a6e3c8f51797580c9
Thank you!
--
Deet-doot-dot, I am a bot.
On Sat, Jun 27, 2020 at 09:02:05PM +0800, Hillf Danton wrote:
> > So, to hit this syzkaller one of these must have happened:
> > 1) rdma_addr_cancel() didn't work and the process_one_work() is still
> > runnable/running
>
> What syzbot reported indicates that the kworker did survive not only
On Fri, Jun 26, 2020 at 12:58 AM Christoph Hellwig wrote:
>
> as part of removing set_fs entirely (for which I have a working
> prototype), we need to stop calling ->read and ->write with kernel
> pointers under set_fs.
>
> My previous "clean up kernel_{read,write} & friends v5" series, on which
> On Jun 27, 2020, at 2:46 PM, Paul E. McKenney wrote:
>
> On Sat, Jun 27, 2020 at 02:02:15PM -0700, Andy Lutomirski wrote:
>>> On Fri, Jun 26, 2020 at 2:05 PM Paul E. McKenney wrote:
>>>
>>> Currently, can_stop_idle_tick() prints "NOHZ: local_softirq_pending HH"
>>> (where "HH" is the
On Sat, 20 Jun 2020 13:41:36 +0300
Mike Rapoport wrote:
> From: Mike Rapoport
>
> Since the commit a148866489fb ("sched: Replace rq::wake_list")
> task_struct and CSD_TYPE_TTWU objects can be on the same queue and this
> requires that have "layout similar enough".
>
> This assumption is
On Fri, Jun 26, 2020 at 7:03 AM Arnd Bergmann wrote:
>
> How about moving that warning from W=1 to W=2?
That sounds like the right thing to do, perhaps with some extra
warnings about W=2 (and W=3) being things that you definitely
shouldn't be running in automated environments (unless you are
MONEY-GRAM TRANSFERRED PAYMENT INFO:
Below is the sender’s information
1. MG. REFERENCE NO#: 36360857
2. SENDER'S NAME: Johnson Williams
3. AMOUNT TO PICKUP: US$10,000
Go to any Money Gram office near you and pick up the payment Track the
Reference Number by visiting and click the link
Greeting
Please forgive me for stressing you with my predicaments and I sorry
to approach you through this media it is because it serves the fastest
means of communication. I came across your E-mail from my personal
search and I decided to contact you believing you will be honest to
fulfill my
On Sat, Jun 27, 2020 at 02:02:15PM -0700, Andy Lutomirski wrote:
> On Fri, Jun 26, 2020 at 2:05 PM Paul E. McKenney wrote:
> >
> > Currently, can_stop_idle_tick() prints "NOHZ: local_softirq_pending HH"
> > (where "HH" is the hexadecimal softirq vector number) when one or more
> > non-RCU softirq
On Sat, Jun 27, 2020 at 05:34:47PM +0300, Mike Rapoport wrote:
> From: Mike Rapoport
>
> Replace pte_alloc_one(), pte_free() and pte_free_kernel() with the generic
> implementation. The only actual functional change is the addition of
> __GFP_ACCOUT for the allocation of the user page tables.
>
1 - 100 of 412 matches
Mail list logo
