3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sagi Grimberg
commit 8d5944d80359e645feb2ebd069a6f4caf7825e40 upstream.
If iser_initialize_task_headers() routine failed before
dma mapping, we should not attempt to unmap in
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Linus=20L=C3=BCssing?=
commit 65d7d46050704bcdb8121ddbf4110bfbf2b38baa upstream.
Bitwise OR/AND assignments in C aren't guaranteed to be atomic. One
OGM handler might undo
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit 6bb0fef489f667cf701853054f44579754f00a06 upstream.
When netlink mmap on receive side is the consumer of nf queue data,
it can happen that in some edge cases,
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jialing Fu
commit 71f8a4b81d040b3d094424197ca2f1bf811b1245 upstream.
The following panic is captured in ker3.14, but the issue still exists
in latest kernel.
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christoph Hellwig
commit 294ab783ad98066b87296db1311c7ba2a60206a5 upstream.
It looks like the Kconfig check that was meant to fix this (commit
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit 592867bfabe2fcb449393ba7eb0de4f972a08c63 upstream.
We may already have gotten a proper fd struct through fdget(), so
whenever we return at the end of an map
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Hin-Tak Leung
commit b4cc0efea4f0bfa2477c56af406cfcf3d3e58680 upstream.
Fix B-tree corruption when a new record is inserted at position 0 in the
node in hfs_brec_insert().
This is
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Krzysztof Kozlowski
commit 5f09a5cbd14ae16e93866040fa44d930ff885650 upstream.
During probe the regulator (if present) was enabled but not disabled in
case of failure. So an
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet
commit c82199061009d1561e31e17fca5e47a87cb7ff4c upstream.
In commit f341861fb0b ("task_work: add a scheduling point in
task_work_run()") I fixed a latency problem adding
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Florian Fainelli
commit 03679a14739a0d4c14b52ba65a69ff553bfba73b upstream.
The macro to write 64-bits quantities to the 32-bits register swapped
the value and offsets arguments, we
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Haggai Eran
commit 11d748045c6dadb279d1acdb6d2ea8f3f2ede85b upstream.
The mlx5_ib_reg_user_mr() function will attempt to call clean_mr() in
its error flow even though there is never
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lukas Wunner
commit 69f92f67b68ab7028ffe15f0eea76b59f8859383 upstream.
Commit 92122789b2d6 ("drm/i915: preserve SSC if previously set v3")
added code to intel_modeset_gem_init to
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Chuck Lever
commit 9d11b51ce7c150a69e761e30518f294fc73d55ff upstream.
The Linux NFS server returns garbage in the data payload of inline
NFS/RDMA READ replies. These are READs of
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dan Carpenter
commit 3294bee87091be5f179474f6c39d1d87769635e2 upstream.
The ">" should be ">=" or we end up reading beyond the end of the array.
Fixes: 6e973d2c4385 ('clk: vexpress:
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit e41b0bedba0293b9e1e8d1e8ed553104b9693656 upstream.
We previously register IPPROTO_ROUTING offload under inet6_add_offload(),
but in error path, we try to
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit b382c08656000c12a146723a153b85b13a855b49 upstream.
diag socket's sock_diag_put_filterinfo() dumps classic BPF programs
upon request to user space (ss -0 -b).
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Viresh Kumar
commit a2022001cebd0825b96aa0f3345ea3ad44ae79d4 upstream.
Tolerance applies on both sides of the target voltage, i.e. both min and
max sides. But while checking if a
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit bb148bdeb0ab16fc0ae8009799471e4d7180073b upstream.
According to the bug report, FSC Amilo laptops with ALC880 can detect
the headphone jack but currently the
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Ward
commit 44840dec6127e4d7c5074f75d2dd96bc4ab85fe3 upstream.
This is an HP-branded Sierra Wireless EM7355:
https://bugzilla.redhat.com/show_bug.cgi?id=1223646#c2
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Masahiro Yamada
commit 64526370d11ce8868ca495723d595b61e8697fbf upstream.
Currently, devres_get() passes devres_free() the pointer to devres,
but devres_free() should be given with
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mike Marciniszyn
commit d6f1c17e162b2a11e708f28fa93f2f79c164b442 upstream.
The lkey table is allocated with with a get_user_pages() with an
order based on a number of index bits from
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Kees Cook
commit a068acf2ee77693e0bf39d6e07139ba704f461c3 upstream.
Many file systems that implement the show_options hook fail to correctly
escape their output which could lead to
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johan Hovold
commit cbb4be652d374f64661137756b8f357a1827d6a4 upstream.
Fix potential null-pointer dereference at probe by making sure that the
required endpoints are present.
The
This is the start of the review cycle for the Linux 3.19.8-ckt8 stable kernel.
This version contains 156 new patches, summarized below. The new patches are
posted as replies to this message and also available in this git branch:
3.19.8-ckt8 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mark Rustad
commit 7aa6ca4d39edf01f997b9e02cf6d2fdeb224f351 upstream.
Set the PCI_DEV_FLAGS_VPD_REF_F0 flag on all Intel Ethernet device
functions other than function 0, so that on
3.13.11-ckt28 -stable review patch. If anyone has any objections, please let
me know.
--
From: Bjorn Helgaas
commit d1541dc977d376406f4584d8eb055488655c98ec upstream.
In fixup_ti816x_class(), we assigned "class = PCI_CLASS_MULTIMEDIA_VIDEO".
But PCI_CLASS_MULTIMEDIA_VIDEO is
On 20/10/15 14:28, Andrew F. Davis wrote:
> Add support for the TI DP83848 Ethernet PHY device.
>
> The DP83848 is a highly reliable, feature rich, IEEE 802.3 compliant
> single port 10/100 Mb/s Ethernet Physical Layer Transceiver supporting
> the MII and RMII interfaces.
>
> Signed-off-by:
3.13.11-ckt28 -stable review patch. If anyone has any objections, please let
me know.
--
From: Hin-Tak Leung
commit 7cb74be6fd827e314f81df3c5889b87e4c87c569 upstream.
Pages looked up by __hfs_bnode_create() (called by hfs_bnode_create() and
hfs_bnode_find() for finding or
3.13.11-ckt28 -stable review patch. If anyone has any objections, please let
me know.
--
From: Jaewon Kim
commit c54839a722a02818677bcabe57e957f0ce4f841d upstream.
reclaim_clean_pages_from_list() assumes that shrink_page_list() returns
number of pages removed from the
On Tue, 20 Oct 2015 16:21:09 +0900 Minchan Kim wrote:
>
> I reviewed THP refcount redesign patch and It seems below patch fixes
> MADV_FREE problem. It works well for hours.
>
> >From 104a0940b4c0f97e61de9fee0fd602926ff28312 Mon Sep 17 00:00:00 2001
> From: Minchan Kim
> Date: Tue, 20 Oct
3.13.11-ckt28 -stable review patch. If anyone has any objections, please let
me know.
--
From: Hin-Tak Leung
commit b4cc0efea4f0bfa2477c56af406cfcf3d3e58680 upstream.
Fix B-tree corruption when a new record is inserted at position 0 in the
node in hfs_brec_insert().
This is
3.13.11-ckt28 -stable review patch. If anyone has any objections, please let
me know.
--
From: Nikhil Badola
commit 523f1dec58408b36e7683a3d61a0286eed1fc1c8 upstream.
USB controller version-2.5 requires to enable internal UTMI
phy and program PTS field in PORTSC register
3.13.11-ckt28 -stable review patch. If anyone has any objections, please let
me know.
--
From: Lars-Peter Clausen
commit 7abad1063deb0f77d275c61f58863ec319c58c5c upstream.
The different devices support by the adis16480 driver have slightly
different scales for the gyroscope
3.13.11-ckt28 -stable review patch. If anyone has any objections, please let
me know.
--
From: =?UTF-8?q?David=20H=C3=A4rdeman?=
commit a66b0c41ad277ae62a3ae6ac430a71882f899557 upstream.
The input_dev is already gone when the rc device is being unregistered
so checking for
This is the start of the review cycle for the Linux 3.13.11-ckt28 stable kernel.
This version contains 85 new patches, summarized below. The new patches are
posted as replies to this message and also available in this git branch:
On Tue, 20 Oct 2015 13:25:28 -0700
"Paul E. McKenney" wrote:
> On Tue, Oct 20, 2015 at 12:10:31PM -0400, Steven Rostedt wrote:
> >
> > Paul,
> >
> > I've spent a couple of days debugging this, and finally found that my
> > stack tracer was calling the stack trace code, which calls
> >
Add support for the TI DP83848 Ethernet PHY device.
The DP83848 is a highly reliable, feature rich, IEEE 802.3 compliant
single port 10/100 Mb/s Ethernet Physical Layer Transceiver supporting
the MII and RMII interfaces.
Signed-off-by: Andrew F. Davis
Signed-off-by: Dan Murphy
---
On Tue, Oct 20, 2015 at 11:21:47AM +0200, Peter Zijlstra wrote:
> On Tue, Oct 20, 2015 at 03:15:32PM +0800, Boqun Feng wrote:
> > On Wed, Oct 14, 2015 at 01:19:17PM -0700, Paul E. McKenney wrote:
> > >
> > > Am I missing something here? If not, it seems to me that you need
> > > the leading
Hi Hanjun,
Thanks for review.
-Brijesh
On 10/19/2015 09:21 PM, Hanjun Guo wrote:
> Hi Brijesh,
>
> On 2015/10/20 3:23, Brijesh Singh wrote:
>> Add support for the AMD Seattle SoC EDAC driver.
>>
>> Signed-off-by: Brijesh Singh
>> ---
>> .../devicetree/bindings/edac/amd-seattle-edac.txt |
On Tue, Oct 20, 2015 at 2:20 PM, Chris Metcalf wrote:
> On 10/20/2015 04:56 PM, Andy Lutomirski wrote:
>>
>> On Tue, Oct 20, 2015 at 1:36 PM, Chris Metcalf
>> wrote:
>>>
>>> +/*
>>> + * In task isolation mode we try to return to userspace only after
>>> + * attempting to make sure we won't be
On 10/20/2015 04:56 PM, Andy Lutomirski wrote:
On Tue, Oct 20, 2015 at 1:36 PM, Chris Metcalf wrote:
+/*
+ * In task isolation mode we try to return to userspace only after
+ * attempting to make sure we won't be interrupted again. To handle
+ * the periodic scheduler tick, we test to make
On 10/20/2015 05:03 PM, Frederic Weisbecker wrote:
On Tue, Oct 20, 2015 at 04:36:06PM -0400, Chris Metcalf wrote:
While the current fallback to 1-second tick is still required for
a number of kernel accounting tasks (e.g. vruntime, load balancing
data, and load accounting), it's useful to be
Hi Greg,
> On Oct 21, 2015, at 00:08 , Greg Kroah-Hartman
> wrote:
>
> On Tue, Oct 20, 2015 at 10:13:16PM +0300, Pantelis Antoniou wrote:
>> * A per overlay can_remove sysfs attribute that reports whether
>> the overlay can be removed or not due to another overlapping overlay.
>>
>> * A
Hi Rob,
> On Oct 21, 2015, at 00:04 , Rob Herring wrote:
>
> On Tue, Oct 20, 2015 at 2:13 PM, Pantelis Antoniou
> wrote:
>> * A per overlay can_remove sysfs attribute that reports whether
>> the overlay can be removed or not due to another overlapping overlay.
>>
>> * A target sysfs attribute
Hi Rob,
> On Oct 21, 2015, at 00:06 , Rob Herring wrote:
>
> On Tue, Oct 20, 2015 at 2:13 PM, Pantelis Antoniou
> wrote:
>> The first patch puts the overlays as objects in the sysfs in
>> /sys/firmware/devicetree/overlays.
>>
>> The next adds a master overlay enable switch (that once is set
On Tue, Oct 20, 2015 at 10:13:16PM +0300, Pantelis Antoniou wrote:
> * A per overlay can_remove sysfs attribute that reports whether
> the overlay can be removed or not due to another overlapping overlay.
>
> * A target sysfs attribute listing the target of each fragment,
> in a group named after
On Tue, Oct 20, 2015 at 2:13 PM, Pantelis Antoniou
wrote:
> The first patch puts the overlays as objects in the sysfs in
> /sys/firmware/devicetree/overlays.
>
> The next adds a master overlay enable switch (that once is set to
> disabled can't be re-enabled), while the one after that
>
On Tue, Oct 20, 2015 at 10:13:15PM +0300, Pantelis Antoniou wrote:
> A throw once master enable switch to protect against any
> further overlay applications if the administrator desires so.
>
> Signed-off-by: Pantelis Antoniou
> ---
> drivers/of/overlay.c | 43
On Tue, Oct 20, 2015 at 2:13 PM, Pantelis Antoniou
wrote:
> * A per overlay can_remove sysfs attribute that reports whether
> the overlay can be removed or not due to another overlapping overlay.
>
> * A target sysfs attribute listing the target of each fragment,
> in a group named after the name
On Tue, Oct 20, 2015 at 04:36:06PM -0400, Chris Metcalf wrote:
> While the current fallback to 1-second tick is still required for
> a number of kernel accounting tasks (e.g. vruntime, load balancing
> data, and load accounting), it's useful to be able to disable it
> for testing purposes. Paul
On Tue, Oct 20, 2015 at 10:13:14PM +0300, Pantelis Antoniou wrote:
> We are going to need the overlays to appear on sysfs with runtime
> global properties (like master enable) so turn them into kobjects.
Why kobjects and not 'struct device'?
Why even have them in sysfs at all? You need more
Hi Rob,
> On Oct 20, 2015, at 23:56 , Rob Herring wrote:
>
> On Tue, Oct 20, 2015 at 2:13 PM, Pantelis Antoniou
> wrote:
>> Documentation ABI entry for overlays sysfs entries.
>>
>> Signed-off-by: Pantelis Antoniou
>> ---
>> .../ABI/testing/sysfs-firmware-devicetree-overlays | 40
>>
On Fri, 2015-10-09 at 15:08 +, Scot Doyle wrote:
> Since commit 27a4c827c34ac4256a190cc9d24607f953c1c459
> fbcon: use the cursor blink interval provided by vt
>
> a PPC64LE kernel fails to boot when fbcon_add_cursor_timer uses an
> uninitialized ops->cur_blink_jiffies. Prevent by
Hi Mike, All,
[not for merge]
As we discussed I've prepared patch which introduces config option
COMMON_CLK_USE_RAW_LOCKS which, once enabled, switches CCF to use raw locks
for locking. This way it will be possible to call clk_enable()/clk_disable()
from atomic context on -RT [1].
Unfortunately
On Tue, Oct 20, 2015 at 2:13 PM, Pantelis Antoniou
wrote:
> Documentation ABI entry for overlays sysfs entries.
>
> Signed-off-by: Pantelis Antoniou
> ---
> .../ABI/testing/sysfs-firmware-devicetree-overlays | 40
> ++
> 1 file changed, 40 insertions(+)
> create mode
On Tue, Oct 20, 2015 at 1:36 PM, Chris Metcalf wrote:
> +/*
> + * In task isolation mode we try to return to userspace only after
> + * attempting to make sure we won't be interrupted again. To handle
> + * the periodic scheduler tick, we test to make sure that the tick is
> + * stopped, and if
Hello!
Have you received my patch? When will it be included in the kernel?
Thanks!
19.10.2015, 00:02, "Anton V. Shokurov" :
> V4L2_CID_EXPOSURE_ABSOLUTE property does not return an updated value when
> autoexposure (V4L2_CID_EXPOSURE_AUTO) is turned on. This patch fixes this
> issue by adding
On 10/20/2015 02:34 PM, Yinghai Lu wrote:
On Tue, Oct 20, 2015 at 1:07 PM, Khalid Aziz wrote:
I don't want to argue about pci_resource_to_user() right now, so I
guess you can just panic if the mem64 offset is different from the
mem32 offset. But you should at least add a comment about why
On Tue, 20 Oct 2015, Chris Metcalf wrote:
> This function checks to see if a vmstat worker is not running,
> and the vmstat diffs don't require an update. The function is
> called from the task-isolation code to see if we need to
> actually do some work to quiet vmstat.
Acked-by: Christoph
Hi Michael,
On Tue, 20 Oct 2015 21:06:51 +1100 Michael Ellerman wrote:
>
> On Tue, 2015-10-20 at 16:21 +1100, Stephen Rothwell wrote:
>
> > After merging the powerpc tree, today's linux-next build (powerpc
> > allyesconfig) produced this warning:
> >
> > WARNING: vmlinux.o(.text+0x9367c):
Hi Yoshinori,
On Tue, 20 Oct 2015 13:28:32 +0900 Yoshinori Sato
wrote:
>
> OK.
> Fixed.
Thanks.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
uct device from device node".
Bisect log is below. Reverting this patch results in build failures, so
I could not test if a revert would fix the problem.
Guenter
---
$ git bisect log
# bad: [1c7a47a97a31902a96fd4ec9e930af23cca3d67d] Add linux-next specific files
for 20151020
# good: [7379047d
The existing nohz_full mode is designed as a "soft" isolation mode
that makes tradeoffs to minimize userspace interruptions while
still attempting to avoid overheads in the kernel entry/exit path,
to provide 100% kernel semantics, etc.
However, some applications require a "hard" commitment from
While the current fallback to 1-second tick is still required for
a number of kernel accounting tasks (e.g. vruntime, load balancing
data, and load accounting), it's useful to be able to disable it
for testing purposes. Paul McKenney observed that if we provide
a mode where the 1Hz fallback timer
We add the necessary call to task_isolation_enter() in the
prepare_exit_to_usermode() routine. We already unconditionally
call into this routine if TIF_NOHZ is set, since that's where
we do the user_enter() call.
We add calls to task_isolation_check_exception() in places
where exceptions may not
This function checks to see if a vmstat worker is not running,
and the vmstat diffs don't require an update. The function is
called from the task-isolation code to see if we need to
actually do some work to quiet vmstat.
Signed-off-by: Chris Metcalf
---
include/linux/vmstat.h | 2 ++
With task_isolation mode, the task is in principle guaranteed not to
be interrupted by the kernel, but only if it behaves. In particular,
if it enters the kernel via system call, page fault, or any of a
number of other synchronous traps, it may be unexpectedly exposed
to long latencies. Add a
When the schedule tick is disabled in tick_nohz_stop_sched_tick(),
we call hrtimer_cancel(), which eventually calls down into
__remove_hrtimer() and thus into hrtimer_force_reprogram(). That
function's call to tick_program_event() detects that we are trying to
set the expiration to KTIME_MAX and
The new "task_isolation_debug" flag simplifies debugging
of TASK_ISOLATION kernels when processes are running in
PR_TASK_ISOLATION_ENABLE mode. Such processes should get no
interrupts from the kernel, and if they do, when this boot flag is
specified a kernel stack dump on the console is
This change is a prerequisite change for TASK_ISOLATION but also
stands on its own for readability and maintainability. The existing
arm64 do_notify_resume() is called in a loop from assembly on
the slow path; this change moves the loop into C code as well.
For the x86 version see commit
This change is a prerequisite change for TASK_ISOLATION but also
stands on its own for readability and maintainability. The existing
tile do_work_pending() was called in a loop from assembly on
the slow path; this change moves the loop into C code as well.
For the x86 version see commit
Allow userspace to override the default SIGKILL delivered
when a task_isolation process in STRICT mode does a syscall
or otherwise synchronously enters the kernel.
Signed-off-by: Chris Metcalf
---
include/uapi/linux/prctl.h | 2 ++
kernel/isolation.c | 9 -
2 files changed, 10
In prepare_exit_to_usermode(), call task_isolation_ready()
when we are checking the thread-info flags, and after we've handled
the other work, call task_isolation_enter() unconditionally.
In syscall_trace_enter_phase1(), we add the necessary support for
strict-mode detection of syscalls.
We add
On Tue, Oct 20, 2015 at 01:26:01PM -0700, Kees Cook wrote:
> On Tue, Oct 20, 2015 at 1:20 PM, Oleg Nesterov wrote:
> >
> > Oh wait, I didn't notice this when I looked at v7.
> >
> > No, you can't do copy_to_user() from atomic context. You need to pin this
> > filter, drop the lock/irq, then
We need to call task_isolation_enter() from prepare_exit_to_usermode(),
so that we can both ensure we do it last before returning to
userspace, and we also are able to re-run signal handling, etc.,
if something occurs while task_isolation_enter() has interrupts
enabled. To do this we add
This per-cpu check was being done in the loop in lru_add_drain_all(),
but having it be callable for a particular cpu is helpful for the
task-isolation patches.
Signed-off-by: Chris Metcalf
---
include/linux/swap.h | 1 +
mm/swap.c| 13 +
2 files changed, 10
This email discusses in detail the changes for v8; please see
older versions of the cover letter for details about older versions.
v8:
The biggest difference in this version is, at Thomas Gleixner's
suggestion, I removed the code that busy-waits until there are no
scheduler-tick timer
From: Christoph Lameter
quiet_vmstat() can be called in anticipation of a OS "quiet" period
where no tick processing should be triggered. quiet_vmstat() will fold
all pending differentials into the global counters and disable the
vmstat_worker processing.
Note that the shepherd thread will
On Tue, Oct 20, 2015 at 01:46:03AM +0200, Frederic Weisbecker wrote:
> On Mon, Oct 19, 2015 at 03:59:07PM -0700, Paul E. McKenney wrote:
> > On Mon, Oct 19, 2015 at 02:45:02PM -0700, Yang Shi wrote:
> > > It is not invoked by anyone now, just remove it.
> > >
> > > Signed-off-by: Yang Shi
> >
>
With 4.1 RT-kernel on TI ARM dra7-evm the below error report is
displayed each time system is woken up from sleep state:
BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:917
in_atomic(): 1, irqs_disabled(): 128, pid: 142, name: sh
INFO: lockdep is turned off.
irq
On Tue, Oct 20, 2015 at 1:07 PM, Khalid Aziz wrote:
>> I don't want to argue about pci_resource_to_user() right now, so I
>> guess you can just panic if the mem64 offset is different from the
>> mem32 offset. But you should at least add a comment about why you're
>> doing that. Otherwise it
Em Tue, Oct 20, 2015 at 04:12:14PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Oct 14, 2015 at 12:41:15PM +, Wang Nan escreveu:
> > This patch introduces bpf__{un,}probe() functions to enable callers to
> > create kprobe points based on section names a BPF program. It parses
> > the
Maurizio Lombardi reported a problem [1] with the %pb extension: It
doesn't work for sufficiently large bitmaps, since the size is stashed
in the field_width field of the struct printf_spec, which is currently
an s16. Concretely, this manifested itself in
/sys/bus/pseudo/drivers/scsi_debug/map
If the string corresponding to a %s specifier can change under us, we
might end up copying a \0 byte to the output buffer. There might be
callers who expect the output buffer to contain a genuine C string
whose length is exactly the snprintf return value (assuming truncation
hasn't happened or has
These should also count as performed tests.
Cc: Kees Cook
Signed-off-by: Rasmus Villemoes
---
lib/test_printf.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/test_printf.c b/lib/test_printf.c
index 80ddafb2675d..8fca007d9bcd 100644
--- a/lib/test_printf.c
+++ b/lib/test_printf.c
@@
The field width is overloaded to pass some extra information for
some %p extensions (e.g. #bits for %pb). But we might silently
truncate the passed value when we stash it in struct printf_spec (see
e.g. "lib/vsprintf.c: expand field_width to 24 bits"). Hopefully 23
value bits should now be enough
One consequence of the reorganization of struct printf_spec to make
field_width 24 bits was that number() gained about 180 bytes. Since
spec is never passed to other functions, we can help gcc make number()
lose most of that extra weight by using local variables for the field
width and precision.
This is pure code movement, making sure the widen_string() helper is
defined before the string() function.
Cc: Ingo Molnar
Signed-off-by: Rasmus Villemoes
---
lib/vsprintf.c | 62 +-
1 file changed, 31 insertions(+), 31 deletions(-)
diff
Following "lib/vsprintf.c: expand field_width to 24 bits", let's add a
test to see that we now actually support bitmaps with 65536 bits.
Cc: Maurizio Lombardi
Cc: Kees Cook
Cc: Tejun Heo
Signed-off-by: Rasmus Villemoes
---
lib/test_printf.c | 17 +
1 file changed, 17
kasprintf relies on being able to replay the formatting and getting
the same result (in particular, the same length). This will almost
always work, but it is possible that the object pointed to by a %s or
%p argument changed under us (so we might get truncated output). Add a
somewhat paranoid
Cc: Al Viro
Signed-off-by: Rasmus Villemoes
---
Al, I'd appreciate it if you'd take a look and see that the printed
strings are actually as expected.
lib/test_printf.c | 27 +++
1 file changed, 27 insertions(+)
diff --git a/lib/test_printf.c b/lib/test_printf.c
index
Add a few padding bytes on either side of the test buffer, and check
that these (and the part of the buffer not used) are untouched by
vsnprintf.
Cc: Kees Cook
Signed-off-by: Rasmus Villemoes
---
lib/test_printf.c | 24 +++-
1 file changed, 19 insertions(+), 5 deletions(-)
Cc: Kees Cook
Signed-off-by: Rasmus Villemoes
---
lib/test_printf.c | 4
1 file changed, 4 insertions(+)
diff --git a/lib/test_printf.c b/lib/test_printf.c
index 1ce1a1dd8faf..80ddafb2675d 100644
--- a/lib/test_printf.c
+++ b/lib/test_printf.c
@@ -166,6 +166,10 @@ test_string(void)
BUG is a completely unnecessarily big hammer, and we're more likely to
get the internal bug reported if we just pr_err() and ensure the test
suite fails.
Cc: Kees Cook
Signed-off-by: Rasmus Villemoes
---
lib/test_printf.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
Pull out the logic in dentry_name() which handles field width space
padding, in preparation for reusing it from string(). Rename the
widen() helper to move_right(), since it is used for handling the
!(flags & LEFT) case.
Cc: Al Viro
Cc: Ingo Molnar
Signed-off-by: Rasmus Villemoes
---
On Tue, Oct 20, 2015 at 1:20 PM, Oleg Nesterov wrote:
> On 10/20, Tycho Andersen wrote:
>>
>> +long seccomp_get_filter(struct task_struct *task, unsigned long filter_off,
>> + void __user *data)
>> +{
>> + struct seccomp_filter *filter;
>> + struct sock_fprog_kern
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 43e41adc9e8c36545888d78fed2ef8d102a938dc:
perf record: Add ability to sample call branches (2015-10-20 10:30:55 +0200)
are available in the git repository at:
From: Andi Kleen
Add a missing field to the perf_event_attr debug output.
Signed-off-by: Andi Kleen
Cc: Jiri Olsa
Cc: Peter Zijlstra
Link:
http://lkml.kernel.org/r/1445366797-30894-4-git-send-email-a...@firstfloor.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/evsel.c | 1
From: Paolo Bonzini
The format of the role word has changed through the years and the plugin
was never updated; some VMX exit reasons were missing too.
Signed-off-by: Paolo Bonzini
Acked-by: Steven Rostedt
Cc: David Ahern
Cc: Namhyung Kim
Cc: k...@vger.kernel.org
Link:
On Tue, Oct 20, 2015 at 12:10:31PM -0400, Steven Rostedt wrote:
>
> Paul,
>
> I've spent a couple of days debugging this, and finally found that my
> stack tracer was calling the stack trace code, which calls
> __module_address() which asserts the below.
>
> Is just calling rcu_irq_enter() and
401 - 500 of 2446 matches
Mail list logo
