On 2018-04-20 11:58, Paul Moore wrote:
> On Fri, Apr 20, 2018 at 9:46 AM, Richard Guy Briggs wrote:
> > On 2018-04-17 18:06, Paul Moore wrote:
> >> On Wed, Apr 11, 2018 at 8:46 AM, Richard Guy Briggs
> >> wrote:
> >> > Tie syscall information to FEATURE_CHANGE calls since it is a result of
> >>
On Fri, Apr 20, 2018 at 09:31:58AM +0200, Michal Hocko wrote:
> On Fri 20-04-18 14:29:39, Tetsuo Handa wrote:
> > Eric Biggers wrote:
> > > But, there is still a related bug: when mounting sysfs, if
> > > register_shrinker()
> > > fails in sget_userns(), then kernfs_kill_sb() gets called, which fr
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86-
> ow...@vger.kernel.org] On Behalf Of Randy Dunlap
> Sent: Friday, April 20, 2018 12:53 PM
> To: Limonciello, Mario; dvh...@infradead.org; Andy Shevchenko
> Cc: LKML; platform-driver-...@vge
this is a test mail
--
software engineer
rajagiri school of engineering and technology
2018-04-20 7:55 GMT-07:00 Tom Talpey :
> Looks good, but I have two possibly style-related comments.
>
>
> On 4/19/2018 5:38 PM, Long Li wrote:
>>
>> From: Long Li
>>
>> The data buffer allocated on the stack can't be DMA'ed, ib_dma_map_page
>> will
>> return an invalid DMA address for a buffer on
On Tue, Apr 10, 2018 at 09:33:39AM +, Kirill A. Shutemov wrote:
> AMD SME claims one bit from physical address to indicate whether the
> page is encrypted or not. To achieve that we clear out the bit from
> __PHYSICAL_MASK.
>
> The capability to adjust __PHYSICAL_MASK is required beyond AMD SM
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
f
Hello,
syzbot hit the following crash on upstream commit
87ef12027b9b1dd0e0b12cf311fbcb19f9d92539 (Wed Apr 18 19:48:17 2018 +)
Merge tag 'ceph-for-4.17-rc2' of git://github.com/ceph/ceph-client
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=83699adeb2d13579c31e
C reproduce
2018-04-20 10:37 GMT-07:00 Steve French :
> I noticed a similar problem with the tcon link leak on that (which
> Colin and Gustavo pointed out - thank you!) but also in another return
> statement, so updated the original patch of Ronnie's merging the fixes
>
> https://git.samba.org/sfrench/cifs-2.6
On Fri, Apr 20, 2018 at 01:05:17PM +, Ghannam, Yazen wrote:
> Okay, I can do that. What about using mce_rdmsrl()? The value gets set to
> 0 and a user gets a single warning. This may be more clear to the user. Also,
> it shouldn't affect code that checks for non-zero values, like in
> __print_
On Tue, Apr 17, 2018 at 12:02:52PM +0300, Jani Nikula wrote:
> On Mon, 16 Apr 2018, "Srivatsa, Anusha" wrote:
> >>-Original Message-
> >>From: Jani Nikula [mailto:jani.nik...@linux.intel.com]
> >>Sent: Wednesday, April 11, 2018 5:27 AM
> >>To: Ian W MORRISON
> >>Cc: Vivi, Rodrigo ; Srivat
hello,
the following is the error found...
---
protection_keys.c:421:5: error: conflicting types for ‘pkey_set’
int pkey_set(int pkey, unsigned long rights, unsigned long flags)
^~~~
-
On 4/20/18 1:19 AM, Peter Zijlstra wrote:
On Sat, Apr 14, 2018 at 09:27:38PM -0700, Yonghong Song wrote:
This patch adds a preprocessor guard NO_BPF_WORKAROUND around the
asm_volatile_goto based static_cpu_has(). NO_BPF_WORKAROUND is set
at toplevel Makefile when compiler supports asm-goto. T
Tom, you used the wrong GPL license header. Please fix that to be v2 not v3.
The
+# SPDX-License-Identifier: GPL-2.0
is correct but the adi-test.c one is not.
On 04/20/2018 10:34 AM, Tom Hromatka wrote:
Add a selftest for the sparc64 privileged ADI driver. These
tests verify the read(), prea
Caller of uprobe_register is required to keep the inode and containing
mount point referenced.
There was misuse of igrab() in uprobes.c and trace_uprobe.c. This is
because igrab() will not prevent umount of the containing mount point.
To fix this, we added path to struct trace_uprobe, which keeps
On chromebooks we depend on wakeup count to identify the wakeup source.
But currently USB devices do not increment the wakeup count when they
trigger the remote wake. This patch addresses the same.
Resume condition is reported differently on USB 2.0 and USB 3.0 devices.
On USB 2.0 devices, a wake
On Fri, Apr 20, 2018 at 10:29 AM, Alan Stern wrote:
> On Fri, 20 Apr 2018, Ravi Chandra Sadineni wrote:
>
>> On chromebooks we depend on wakeup count to identify the wakeup source.
>> But currently USB devices do not increment the wakeup count when they
>> trigger the remote wake. This patch addre
On 20.04.2018 17:23, Arnd Bergmann wrote:
> On Thu, Apr 19, 2018 at 8:51 AM, Baolin Wang wrote:
>> The read_persistent_clock() uses a timespec, which is not year 2038 safe
>> on 32bit systems. On parisc architecture, we have implemented generic RTC
>> drivers that can be used to compensate the sys
On Fri, Apr 20, 2018 at 11:47 AM, Stephen Boyd wrote:
> Quoting Rob Herring (2018-04-18 15:29:05)
>> diff --git a/Documentation/devicetree/bindings/example-schema.yaml
>> b/Documentation/devicetree/bindings/example-schema.yaml
>> new file mode 100644
>> index ..fe0a3bd1668e
>> --- /de
Doggonit! Thanks, Wim.
I'll send out a new revision shortly.
Tom
On 04/20/2018 12:08 PM, Wim Coekaerts wrote:
Tom, you used the wrong GPL license header. Please fix that to be v2
not v3.
The
+# SPDX-License-Identifier: GPL-2.0
is correct but the adi-test.c one is not.
On 04/20/2018 10:
When out of memory and we can't add ctrl vq buffers,
probe fails. Unfortunately the error handling is
out of spec: it calls del_vqs without bothering
to reset the device first.
To fix, call the full cleanup function in this case.
Cc: sta...@vger.kernel.org
Signed-off-by: Michael S. Tsirkin
---
Will make it reusable for error handling.
Signed-off-by: Michael S. Tsirkin
---
drivers/char/virtio_console.c | 72 +--
1 file changed, 36 insertions(+), 36 deletions(-)
diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
index 2d87
For cleanup it's helpful to be able to simply scan all vqs and discard
all data. Add an iterator to do that.
Signed-off-by: Michael S. Tsirkin
---
include/linux/virtio.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/virtio.h b/include/linux/virtio.h
index 988c735..fa1b5da
Turns out virtio console tries to take a buffer out of an active vq.
Works by sheer luck, and is explicitly forbidden by spec. And while
going over it I saw that error handling is also broken -
failure is easy to trigger if I force allocations to fail.
Lightly tested.
Michael S. Tsirkin (6):
v
We now cleanup all VQs on device removal - no need
to handle the control VQ specially.
Signed-off-by: Michael S. Tsirkin
---
drivers/char/virtio_console.c | 17 -
1 file changed, 17 deletions(-)
diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
index 26a
an allocated buffer doesn't need to be tied to a vq -
only vq->vdev is ever used. Pass the function the
just what it needs - the vdev.
Signed-off-by: Michael S. Tsirkin
---
drivers/char/virtio_console.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/ch
On Fri, Apr 20, 2018 at 9:51 AM Vince Weaver
wrote:
> On Fri, 20 Apr 2018, Vince Weaver wrote:
> > > AFAICT it works on Power and possibly ARM.
> >
> > at least some ARMs are a bit more honest about it than x86
> >
> > ivybridge:
> > Performance counter stats for '/bin/ls':
> > 1,368
Console driver is out of spec. The spec says:
A driver MUST NOT decrement the available idx on a live
virtqueue (ie. there is no way to “unexpose” buffers).
and it does exactly that by trying to detach unused buffers
without doing a device reset first.
Defer detaching the buffers u
Hi Jacob,
On Mon, Apr 16, 2018 at 10:48:54PM +0100, Jacob Pan wrote:
[...]
> +/**
> + * enum iommu_inv_granularity - Generic invalidation granularity
> + *
> + * When an invalidation request is sent to IOMMU to flush translation caches,
> + * it may carry different granularity. These granularity l
On Fri, 20 Apr 2018, Ravi Chandra Sadineni wrote:
> On chromebooks we depend on wakeup count to identify the wakeup source.
> But currently USB devices do not increment the wakeup count when they
> trigger the remote wake. This patch addresses the same.
>
> Resume condition is reported differentl
This patch adds generic io{read|write}64[be]{_lo_hi|_hi_lo} macros if
they are not already defined by the architecture. (As they are provided
by the generic iomap library).
The patch also points io{read|write}64[be] to the variant specified by the
header name.
This is because new drivers are enco
Fix an asymmetry in the io{read|write}XXbe functions in that the
big-endian variants make use of the raw io accessors while the
little-endian variants use the regular accessors. Some architectures
implement barriers to order against both spinlocks and DMA accesses
and for these case, the big-endian
Clean up the ifdefs which conditionally defined the io{read|write}64
functions in favour of the new common io-64-nonatomic-lo-hi header.
Per a nit from Andy Shevchenko, the include list is also made
alphabetical.
Signed-off-by: Logan Gunthorpe
Reviewed-by: Andy Shevchenko
Cc: Jon Mason
---
dr
Clean up the extra ifdefs which defined the wr_reg64 and rd_reg64
functions in non-64bit cases in favour of the new common
io-64-nonatomic-lo-hi header.
To be consistent with CAAM engine HW spec: in case of 64-bit registers,
irrespective of device endianness, the lower address should be read from
Now that ioread64 and iowrite64 are available in io-64-nonatomic,
we can remove the hack at the top of ntb_hw_intel.c and replace it
with an include.
Signed-off-by: Logan Gunthorpe
Reviewed-by: Andy Shevchenko
Acked-by: Dave Jiang
Acked-by: Allen Hubbe
Acked-by: Jon Mason
---
drivers/ntb/hw/
In order to provide non-atomic functions for io{read|write}64 that will
use readq and writeq when appropriate. We define a number of variants
of these functions in the generic iomap that will do non-atomic
operations on pio but atomic operations on mmio.
These functions are only defined if readq a
This is v14 of my cleanup series to push a number of instances of people
defining their own io{read|write}64 functions into common headers seing
they don't exist in non-64bit systems. This series adds inline functions to the
io-64-nonatomic headers and then cleans up the drivers that defined their
Add support for io{read|write}64() functions in parisc architecture.
These are pretty straightforward copies of similar functions which
make use of readq and writeq.
Also, indicate that the lo_hi and hi_lo variants of these functions
are not provided by this architecture.
Signed-off-by: Logan Gun
On Tue, Apr 17, 2018 at 08:10:47PM +0100, Alex Williamson wrote:
[...]
> > + /* Assign guest PASID table pointer and size order */
> > + ctx_lo = (pasidt_binfo->base_ptr & VTD_PAGE_MASK) |
> > + (pasidt_binfo->pasid_bits - MIN_NR_PASID_BITS);
>
> Where does this IOMMU API interface d
Hi Linus,
Please pull the following watchdog changes for the v4.17 release cycle.
This series contains:
- fall-through fixes
- MAINTAINER change for hpwdt
- renesas-wdt: Add support for WDIOF_CARDRESET
- aspeed: set bootstatus during probe
The output from git request-pull:
--
On Fri, 20 Apr 2018 11:08:47 -0700
Song Liu wrote:
> For uprobes.c sisde, igrab() is not necessary. So we removed it and
You don't need to send another patch, but what is the above sentence
suppose to say?
-- Steve
> added comments on requirements to callers of uprobe_register().
On Fri, 20 Apr 2018 16:58:46 +0100 Al Viro wrote:
> Assorted fixes. Some of that is only a matter with fault injection
> (broken handling of small allocation failure in various mount-related places),
> but the last one is a root-triggerable stack overflow, and combined with
> userns it get
On Fri, 20 Apr 2018 09:56:24 -0700
Song Liu wrote:
> s Miklos reported and suggested:
>
> This pattern repeats two times in trace_uprobe.c and in
> kernel/events/core.c as well:
>
> ret = kern_path(filename, LOOKUP_FOLLOW, &path);
> if (ret)
> goto fail_address_parse;
>-Original Message-
>From: Vivi, Rodrigo
>Sent: Friday, April 20, 2018 11:04 AM
>To: Jani Nikula
>Cc: Srivatsa, Anusha ; Ian W MORRISON
>; airl...@linux.ie; Greg KH
>; intel-...@lists.freedesktop.org; linux-
>ker...@vger.kernel.org; sta...@vger.kernel.org; dri-
>de...@lists.freedesktop.o
> On Apr 20, 2018, at 11:29 AM, Steven Rostedt wrote:
>
> On Fri, 20 Apr 2018 11:08:47 -0700
> Song Liu wrote:
>
>> For uprobes.c sisde, igrab() is not necessary. So we removed it and
>
> You don't need to send another patch, but what is the above sentence
> suppose to say?
>
> -- Steve
>
> On 19 Apr 2018, at 09.39, Hans Holmberg
> wrote:
>
> From: Hans Holmberg
>
> The write error recovery path is incomplete, so rework
> the write error recovery handling to do resubmits directly
> from the write buffer.
>
> When a write error occurs, the remaining sectors in the chunk are
> m
On Fri, 20 Apr 2018 18:36:38 +
Song Liu wrote:
> > On Apr 20, 2018, at 11:29 AM, Steven Rostedt wrote:
> >
> > On Fri, 20 Apr 2018 11:08:47 -0700
> > Song Liu wrote:
> >
> >> For uprobes.c sisde, igrab() is not necessary. So we removed it and
> >
> > You don't need to send another pa
> Subject: Re: [Patch v4] cifs: Allocate validate negotiation request through
> kmalloc
>
> Looks good, but I have two possibly style-related comments.
>
> On 4/19/2018 5:38 PM, Long Li wrote:
> > From: Long Li
> >
> > The data buffer allocated on the stack can't be DMA'ed,
> > ib_dma_map_page w
On Fri, Apr 20, 2018 at 11:59 AM, Mark Brown wrote:
> On Wed, Apr 18, 2018 at 05:29:05PM -0500, Rob Herring wrote:
>> The current DT binding documentation format of freeform text is painful
>> to write, review, validate and maintain.
>>
>> This is just an example of what a binding in the schema fo
Adds two IR keymaps for NVIDIA devices.
The RC types are SONY12 and NEC.
Jun Yan (1):
media: rc: Add NVIDIA IR keymapping
drivers/media/rc/keymaps/Makefile| 2 +
drivers/media/rc/keymaps/rc-nvidia-nec.c | 66
drivers/media/rc/keymaps/rc-nvidia.c | 66 +
From: Jun Yan
Add keymap with NEC and SONY12 protocol for NVIDIA IR
Signed-off-by: Jun Yan
Signed-off-by: marting
Signed-off-by: Daniel Fu
Signed-off-by: Vladislav Zhurba
---
drivers/media/rc/keymaps/Makefile| 2 +
drivers/media/rc/keymaps/rc-nvidia-nec.c | 66 +
On Tue, Apr 17, 2018 at 05:59:36PM -0700, Luis R. Rodriguez wrote:
> On Thu, Dec 21, 2017 at 12:03:29PM +0100, Jan Kara wrote:
> > Hello,
> >
> > I think I owe you a reply here... Sorry that it took so long.
>
> Took me just as long :)
>
> > On Fri 01-12-17 22:13:27, Luis R. Rodriguez wrote:
> >
> On Apr 20, 2018, at 11:40 AM, Steven Rostedt wrote:
>
> On Fri, 20 Apr 2018 18:36:38 +
> Song Liu wrote:
>
>>> On Apr 20, 2018, at 11:29 AM, Steven Rostedt wrote:
>>>
>>> On Fri, 20 Apr 2018 11:08:47 -0700
>>> Song Liu wrote:
>>>
For uprobes.c sisde, igrab() is not necessary. S
> On 19 Apr 2018, at 09.39, Hans Holmberg
> wrote:
>
> From: Hans Holmberg
>
> Write failures should not happen under normal circumstances,
> so in order to bring the chunk back into a known state as soon
> as possible, evacuate all the valid data out of the line and let the
> fw judge if the
On 4/20/2018 2:41 PM, Long Li wrote:
Subject: Re: [Patch v4] cifs: Allocate validate negotiation request through
kmalloc
Looks good, but I have two possibly style-related comments.
On 4/19/2018 5:38 PM, Long Li wrote:
From: Long Li
The data buffer allocated on the stack can't be DMA'ed,
ib_d
> On 19 Apr 2018, at 09.39, Hans Holmberg
> wrote:
>
> From: Hans Holmberg
>
> Smeta write errors were previously ignored. Skip these
> lines instead and throw them back on the free
> list, so the chunks will go through a reset cycle
> before we attempt to use the line again.
>
> Signed-off-b
On 2018-04-18 11:11, Channa wrote:
On 2018-04-18 07:52, Rob Herring wrote:
On Tue, Apr 17, 2018 at 5:12 PM, wrote:
On 2018-04-17 10:43, risha...@codeaurora.org wrote:
On 2018-04-16 07:59, Rob Herring wrote:
On Tue, Apr 10, 2018 at 01:08:12PM -0700, Rishabh Bhatnagar wrote:
Documentation
From: Daniel Fu
Remove STATE_TRAILER_SPACE from state machine.
Causing 2 issue:
- can not decode the keycode, if it didn't following with
another keycode/repeat code
- will generate one more code in current logic.
i.e. key_right + repeat code + key_left + repeat code.
expect: key_right, key
On Tue, Apr 10, 2018 at 08:24:59AM -0500, Bjorn Helgaas wrote:
> Remove some unused microblaze PCI code.
>
> I can merge these via PCI if you like, Michal. I have some related
> changes coming for some sparc resource claim issues. Or it's fine if
> you pick them up.
I applied these to pci/micro
edid should be freed once it's finished being used.
Fixes: 56fe8b6f4991 ("drm/bridge: Add RGB to VGA bridge support")
Cc: Rob Herring
Cc: Sean Paul
Cc: Maxime Ripard
Cc: Archit Taneja
Cc: Andrzej Hajda
Cc: Laurent Pinchart
Cc: # v4.9+
Signed-off-by: Sean Paul
---
drivers/gpu/drm/bridge/du
On Fri, Apr 20, 2018 at 1:48 PM, Richard Guy Briggs wrote:
> On 2018-04-20 11:58, Paul Moore wrote:
>> On Fri, Apr 20, 2018 at 9:46 AM, Richard Guy Briggs wrote:
>> > On 2018-04-17 18:06, Paul Moore wrote:
>> >> On Wed, Apr 11, 2018 at 8:46 AM, Richard Guy Briggs
>> >> wrote:
>> >> > Tie syscal
On 04/18/2018 10:55 PM, Stephen Boyd wrote:
> Quoting David Collins (2018-03-22 18:30:06)
>> On 03/21/2018 12:07 PM, Stephen Boyd wrote:
>>> Quoting David Collins (2018-03-16 18:09:10)
diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
index 097f617..e0ecd0a 100644
--
On Fri, Apr 20, 2018 at 11:29:45AM -0700, Andrew Morton wrote:
> On Fri, 20 Apr 2018 16:58:46 +0100 Al Viro wrote:
>
> > Assorted fixes. Some of that is only a matter with fault injection
> > (broken handling of small allocation failure in various mount-related
> > places),
> > but the last
The following two bugs were reported by Fengguang Wu:
kernel reboot-without-warning in early-boot stage, last printk:
early console in setup code
https://lkml.org/lkml/2018/4/18/797
And, also:
[per_cpu_ptr_to_phys] PANIC: early exception 0x0d
IP 10:a892f15f error 0 cr2 0x88001fbff000
Hi!
> >> Hi! Sorry I lost this email in my inbox. It seems this is specific to
> >> a particular subset of arm architectures? (My local builds of arm all
> >> succeed, for example. Can you send your failing config?) I'll take a
> >> closer look on Monday if Daniel doesn't beat me to it.
> >
> > Da
> Subject: Re: [Patch v4] cifs: Allocate validate negotiation request through
> kmalloc
>
> On 4/20/2018 2:41 PM, Long Li wrote:
> >> Subject: Re: [Patch v4] cifs: Allocate validate negotiation request
> >> through kmalloc
> >>
> >> Looks good, but I have two possibly style-related comments.
> >>
On 20 April 2018 at 15:15, Pavel Machek wrote:
> Hi!
>
>> >> Hi! Sorry I lost this email in my inbox. It seems this is specific to
>> >> a particular subset of arm architectures? (My local builds of arm all
>> >> succeed, for example. Can you send your failing config?) I'll take a
>> >> closer loo
Wolfram Sang writes:
> This header only contains platform_data. Move it to the proper directory.
>
> Signed-off-by: Wolfram Sang
For mach-pxa:
Acked-by: Robert Jarzmik
Take it through your tree, no problem for the pxa part.
Cheers.
--
Robert
On Fri, 2018-04-20 at 14:44 +0800, yuank...@codeaurora.org wrote:
> On 2018-04-20 09:47 AM, yuank...@codeaurora.org wrote:
[]
> > [ZJ] Further prototyping has been given based on gcc for both of
> > x86_64 and armv8-a,
> > unsigned int and bool share the same 1 bytes without the
> > addtional
On Thu, Apr 19, 2018 at 05:02:17PM -0700, Andrew Morton wrote:
> On Wed, 21 Feb 2018 22:23:39 +0300 Alexey Dobriyan
> wrote:
>
> > /proc/*/cmdline is not different from /proc/*/environ as it accesses
> > target task's memory (and can access the very same region of memory)
> > but it doesn't go t
On Fri 2018-04-20 15:18:32, Daniel Micay wrote:
> On 20 April 2018 at 15:15, Pavel Machek wrote:
> > Hi!
> >
> >> >> Hi! Sorry I lost this email in my inbox. It seems this is specific to
> >> >> a particular subset of arm architectures? (My local builds of arm all
> >> >> succeed, for example. Can
On 04/19/2018 05:08 AM, Mark Brown wrote:
> On Wed, Apr 18, 2018 at 10:55:49PM -0700, Stephen Boyd wrote:
Is this regulator-microvolt-offset? Ah I guess it's a thing in the RPMh
registers. This probably needs to be pushed into the framework and come
down through a 'set_headroom' op i
The patch diff itself looks fine, just some comments on the submission
of this.
#1, the subject should be: [PATCH] init: Call mm_init() before trap_init()
Need "PATCH" and not "v1". The versions start with the second update of
a patch, and then it would be "[PATCH v2]"
On Fri, 20 Apr 2018 15:1
Well, that's not related, it's just this:
#ifdef __GNUC__
#if (__GNUC__ == 3 && __GNUC_MINOR__ < 3)
#error Your compiler is too buggy; it is known to miscompile kernels.
#errorKnown good compilers: 3.3, 4.x
#endif
#if GCC_VERSION >= 40800 && GCC_VERSION < 40803
#error Your compiler is too bugg
On 2018-04-20 06:26 AM, Kalle Valo wrote:
Andres Rodriguez writes:
This reduces the unnecessary spew when trying to load optional firmware:
"Direct firmware load for ... failed with error -2"
Signed-off-by: Andres Rodriguez
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c
Long,
> If num_cpus=1, we don't have any sub channels.
>
> The host offers one sub channel for VM with 5 CPUs, after that it offers
> an additional sub channel every 4 CPUs.
>
> The primary channel is always offered.
Applied to 4.17/scsi-fixes. Thanks!
--
Martin K. Petersen Oracle Linux E
Syscall CallAvgTime AvgSize
Count (ticks) (bytes)
---
read 3 1196388133
pread 4 1181646741
write 3 3394428133
pwrite4 2801346741
seek
ADI is a feature supported on SPARC M7 and newer processors to allow
hardware to catch rogue accesses to memory. ADI is supported for data
fetches only and not instruction fetches. An app can enable ADI on its
data pages, set version tags on them and use versioned addresses to
access the data pages
Signed-off-by: Tom Hromatka
Reviewed-by: Khalid Aziz
Reviewed-by: Shannon Nelson
Reviewed-by: Anthony Yznaga
---
drivers/char/Kconfig | 12 +++
drivers/char/Makefile | 1 +
drivers/char/adi.c| 240 ++
3 files changed, 253 insertions(+)
c
[+Philip]
On 2018-04-20 10:47 AM, Michel Dänzer wrote:
> On 2018-04-11 11:37 AM, Christian König wrote:
>> Am 11.04.2018 um 06:00 schrieb Gabriel C:
>>> 2018-04-09 11:42 GMT+02:00 Christian König
>>> :
Am 07.04.2018 um 00:00 schrieb Jean-Marc Valin:
> Hi Christian,
>
> Thanks for
Long,
> This is a best effort for estimating on how busy the ring buffer is
> for that channel, based on available buffer to write in percentage. It
> is still possible that at the time of actual ring buffer write, the
> space may not be available due to other processes may be writing at
> the ti
On Fri, Apr 20, 2018 at 02:44:02PM -0300, Ezequiel Garcia wrote:
> Hi Sebastian,
>
> On Fri, 2018-04-20 at 19:24 +0200, Sebastian Reichel wrote:
> > The current reset-gpio support triggers an interrupt storm on platforms
> > using the maxtouch with level based interrupt. The Motorola Droid 4,
> >
Use new return type vm_fault_t for page_mkwrite and
fault handler. For now, this is just documenting that
the function returns a VM_FAULT value rather than an
errno. Once all instances are converted, vm_fault_t
will become a distinct type.
Reference id -> 1c8f422059ae ("mm: change return type to
On 04/20/2018 03:16 AM, Thomas Gleixner wrote:
>> pageattr.c is not friendly when it encounters empty (zero) PTEs. The
>> kernel linear map is exempt from these checks, but kernel text is not.
>> This patch adds the code to also exempt kernel text from these checks.
> Bah. Changelogs should tell t
On Thu, Apr 19, 2018 at 05:15:20PM -0700, Andrew Morton wrote:
> On Wed, 21 Feb 2018 22:30:09 +0300 Alexey Dobriyan
> wrote:
>
> > "rv" variable is used both as a counter of bytes transferred and
> > an error value holder but it can be reduced solely to error values
> > if original start of user
Hi Jerome,
I love your patch! Yet something to improve:
[auto build test ERROR on clk/clk-next]
[also build test ERROR on v4.17-rc1 next-20180420]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On 04/20/2018 07:45 PM, Yury Norov wrote:
> On Fri, Apr 20, 2018 at 05:08:23PM +0300, Andrey Ryabinin wrote:
>>
>>
>> On 04/19/2018 06:01 AM, Fengguang Wu wrote:
>>> Hello,
>>>
>>> FYI this happens in mainline kernel 4.17.0-rc1.
>>> It at least dates back to v4.8 .
>>>
>>> [ 25.697463]
>>> [ 25
On 04/20/18 11:15, Rob Herring wrote:
> On Fri, Apr 20, 2018 at 11:47 AM, Stephen Boyd wrote:
>> Quoting Rob Herring (2018-04-18 15:29:05)
>>> diff --git a/Documentation/devicetree/bindings/example-schema.yaml
>>> b/Documentation/devicetree/bindings/example-schema.yaml
>>> new file mode 100644
>>
Hi Neil,
On Mon, 16 Apr 2018 09:42:30 +1000
NeilBrown wrote:
> Winbond spi-nor flash 32MB and larger have an 'Extended Address
> Register' as one option for addressing beyond 16MB (Macronix
> has the same concept, Spansion has EXTADD bits in the Bank Address
> Register).
>
> According to sectio
Currently the driver adjusts time by reading the current time and then
modifying it before writing to SYSTIM register. This can introduce
inaccuracies in SYSTIM. With a PREEMPT_RT kernel, spinlocks may be
interrupted, which in the existing implementation may lead to increased
time between the read
On Fri, 20 Apr 2018 20:09:56 +0100 Al Viro wrote:
> On Fri, Apr 20, 2018 at 11:29:45AM -0700, Andrew Morton wrote:
> > On Fri, 20 Apr 2018 16:58:46 +0100 Al Viro wrote:
> >
> > > Assorted fixes. Some of that is only a matter with fault injection
> > > (broken handling of small allocation fai
On 04/04/2018 12:17 PM, jgli...@redhat.com wrote:
> From: Jérôme Glisse
>
> https://cgit.freedesktop.org/~glisse/linux/log/?h=generic-write-protection-rfc
>
> This is an RFC for LSF/MM discussions. It impacts the file subsystem,
> the block subsystem and the mm subsystem. Hence it would benefit
On Fri, Apr 20, 2018 at 10:23 AM, Randy Dunlap wrote:
> On 04/20/18 09:28, Alexander Duyck wrote:
>> This series is meant to add support for SR-IOV on devices when the VFs are
>> not managed by the kernel. Examples of recent patches attempting to do this
>> include:
>> virto - https://patchwork.ke
Hi Ladislav,
On Mon, 16 Apr 2018 08:52:59 +0200
Ladislav Michl wrote:
> dma_map_single doesn't get the proper DMA address for vmalloced area,
That's not true, it returns the right DMA (physical) address, it's just
that:
1/ the memory location is not necessarily physically contiguous
2/ in case
Hi Jerome,
I love your patch! Yet something to improve:
[auto build test ERROR on clk/clk-next]
[also build test ERROR on v4.17-rc1 next-20180420]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Something put your commit message texts completely into the subject
lines of the patch emails.
Please fix this and resubmit as v4.
Thank you.
On 2018-04-18 21:46, Paul Moore wrote:
> On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote:
> > Audit events could happen in a network namespace outside of a task
> > context due to packets received from the net that trigger an auditing
> > rule prior to being associated with a running tas
Attention: Beneficiary,
Re:CONTACT MONEY GRAM OFFICE FOR YOUR PAYMENT OF $5,000.00
This is the second time we are notifying you about the statue of your
compensation fund of ( $1,500,000.00).Be inform that We have been authorized by
the United Nations Compensation Commission (UNCC) to release y
On 04/20/2018 06:16 PM, Jann Horn wrote:
> Remove dead code that bails on `attr->value_size > KMALLOC_MAX_SIZE` - the
> previous check already bails on `attr->value_size != 4`.
>
> Signed-off-by: Jann Horn
Applied to bpf tree, thanks Jann!
On Fri, Apr 20, 2018 at 4:02 PM, Richard Guy Briggs wrote:
> On 2018-04-18 21:46, Paul Moore wrote:
>> On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote:
>> > Audit events could happen in a network namespace outside of a task
>> > context due to packets received from the net that trigger
701 - 800 of 936 matches
Mail list logo
