mmu_notifier_ops structures are never modified, so declare them all as
const.
---
drivers/infiniband/core/umem_odp.c |2 +-
drivers/iommu/amd_iommu_v2.c |2 +-
drivers/xen/gntdev.c |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
To unsubscribe from
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit b6878d9e03043695dbf3fa1caa6dfc09db225b16 upstream.
In drivers/md/md.c get_bitmap_file() uses kmalloc() for creating a
mdu_bitmap_file_t called "file".
5769 file =
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 602b8593d2b4138c10e922eeaafe306f6b51817b upstream.
The current semaphore code allows a potential use after free: in
exit_sem we may free the task's sem_undo_list while there is still
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
Without this length argument, we can read past the end of the iovec in
memcpy_toiovec because we have no way of knowing the total length of the
iovec's buffers.
This is needed for stable kernels
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 89c22d8c3b278212eef6a8cc66b570bc840a6f5a ]
When we calculate the checksum on the recv path, we store the
result in the skb as an optimisation in case we need the checksum
again
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit e8577d1f0329d4842e8302e289fb2c22156abef4 upstream.
ipc_addid() makes a new ipc identifier visible to everyone. New objects
start as locked, so that the caller can complete the
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit a0a2a6602496a45ae838a96db8b8173794b5d398 upstream.
The commit 738ac1ebb96d02e0d23bc320302a6ea94c612dec ("net: Clone
skb before setting peeked flag") introduced a use-after-free bug
in
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit fe2b592173ff0274e70dc44d1d28c19bb995aa7c upstream.
wf_unregister_client() increments the client count when a client
unregisters. That is obviously incorrect. Decrement that client count
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit eddd3826a1a0190e5235703d1e666affa4d13b96 upstream.
Dmitry Vyukov reported the following using trinity and the memory
error detector AddressSanitizer
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 77751427a1ff25b27d47a4c36b12c3c8667855ac upstream.
Currently we don't check if the new MTU is valid or not and this allows
one to configure a smaller than minimum allowed by RFCs or even
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 738ac1ebb96d02e0d23bc320302a6ea94c612dec upstream.
Shared skbs must not be modified and this is crucial for broadcast
and/or multicast paths where we use it as an optimisation to avoid
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 8ce675ff39b9958d1c10f86cf58e357efaafc856 ]
Either of pskb_pull() or pskb_trim() may fail under low memory conditions.
If rds_tcp_data_recv() ignores such failures, the
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 468b732b6f76b138c0926eadf38ac88467dcd271 upstream.
"len" is a signed integer. We check that len is not negative, so it
goes from zero to INT_MAX. PAGE_SIZE is unsigned long so the
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 48900cb6af4282fa0fb6ff4d72a81aa3dadb5c39 upstream.
virtio declares support for NETIF_F_FRAGLIST, but assumes
that there are at most MAX_SKB_FRAGS + 2 fragments which isn't
always true with
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 077cb37fcf6f00a45f375161200b5ee0cd4e937b ]
It seems that kernel memory can leak into userspace by a
kmalloc, ethtool_get_strings, then copy_to_user sequence.
Avoid this by
2015-11-29 18:33 GMT-03:00 Paul Mackerras :
> On Sun, Nov 29, 2015 at 05:14:03PM -0300, Geyslan Gregório Bem wrote:
>> Hello,
>>
>> I have found a possible out of bounds reading in
>> arch/powerpc/kvm/book3s_64_mmu.c (kvmppc_mmu_book3s_64_xlate
>> function). pteg[] array could be accessed twice
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 0c78789e3a030615c6650fde89546cadf40ec2cc upstream.
In case the reconnection attempt fails.
Signed-off-by: Trond Myklebust
[bwh: Backported to 3.2: add local variable xprt]
Signed-off-by:
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit e81107d4c6bd098878af9796b24edc8d4a9524fd upstream.
My colleague ran into a program stall on a x86_64 server, where
n_tty_read() was waiting for data even if there was data in the buffer
in
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit ffeecc5213024ae663377b442eedcfbacf6d0c5d upstream.
struct xfs_attr_leafblock contains 'entries' array which is declared
with size 1 altough it can in fact contain much more entries. Since
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 1c90308e7a77af6742a97d1021cca923b23b7f0d upstream.
This patch makes pagemap readable for normal users and hides physical
addresses from them. For some use-cases PFN isn't required at all.
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 2f84a8990ebbe235c59716896e017c6b2ca1200f upstream.
SunDong reported the following on
https://bugzilla.kernel.org/show_bug.cgi?id=103841
I think I find a linux bug, I have the
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 64526370d11ce8868ca495723d595b61e8697fbf upstream.
Currently, devres_get() passes devres_free() the pointer to devres,
but devres_free() should be given with the pointer to resource data.
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit fc57a7c68020dcf954428869eafd934c0ab1536f upstream.
PARAVIRT_ADJUST_EXCEPTION_FRAME generates this code (using nmi as an
example, trimmed for readability):
ff 15 00 00 00 00
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 74e98eb085889b0d2d4908f59f6e00026063014f upstream.
There was no verification that an underlying transport exists when creating
a connection, this would cause dereferencing a NULL ptr.
It
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
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 an identical change to the
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 1f35d04a02a652f14566f875aef3a6f2af4cb77b upstream.
The iomap[] array has PCIM_IOMAP_MAX (6) elements and not
DEVICE_COUNT_RESOURCE (16). This bug was found using a static checker.
It may
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 0ff28d9f4674d781e492bcff6f32f0fe48cf0fed upstream.
Using sendfile with below small program to get MD5 sums of some files,
it appear that big files (over 64kbytes with 4k pages system) get
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 44f49dd8b5a606870a1f21101522a0f9c4414784 ]
Fixes the following kernel BUG :
BUG: using __this_cpu_add() in preemptible [] code: bash/2758
caller is
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 8fa677d2706d325d71dab91bf6e6512c05214e37 ]
Under low memory conditions, tcp_sk_init() and icmp_sk_init()
can both iterate on all possible cpus and call inet_ctl_sock_destroy(),
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 79b568b9d0c7c5d81932f4486d50b38efdd6da6d upstream.
hid_connect adds various strings to the buffer but they're all
conditional. You can find circumstances where nothing would be written
to
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 7cb74be6fd827e314f81df3c5889b87e4c87c569 upstream.
Pages looked up by __hfs_bnode_create() (called by hfs_bnode_create() and
hfs_bnode_find() for finding or creating pages corresponding to
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit eb38f3a4f6e86f8bb10a3217ebd85ecc5d763aae upstream.
We've got bug reports showing the old systemd-logind (at least
system-210) aborting unexpectedly, and this turned out to be because
of an
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit 275d7d44d802ef271a42dc87ac091a495ba72fc5 upstream.
Poma (on the way to another bug) reported an assertion triggering:
[] module_assert_mutex_or_preempt+0x49/0x90
[]
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit cde93be45a8a90d8c264c776fab63487b5038a65 upstream.
A rename can result in a dentry that by walking up d_parent
will never reach it's mnt_root. For lack of a better term
I call this an
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit b582ef5c53040c5feef4c96a8f9585b6831e2441 upstream.
Do not clobber the buffer space passed from `search_binary_handler' and
originally preloaded by `prepare_binprm' with the executable's
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit b9a532277938798b53178d5a66af6e2915cb27cf upstream.
As reported by Dmitry Vyukov, we really shouldn't do ipc_addid() before
having initialized the IPC object state. Yes, we initialize the
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
commit cbb4be652d374f64661137756b8f357a1827d6a4 upstream.
Fix potential null-pointer dereference at probe by making sure that the
required endpoints are present.
The whiteheat driver assumes
This is the start of the longterm review cycle for the 2.6.32.69 release.
All patches will be posted as a response to this one. If anyone has any
issue with these being applied, please let me know. If anyone is a
maintainer of the proper subsystem, and wants to add a Signed-off-by: line
to the
Hello.
On 11/28/2015 5:51 PM, Pavel Machek wrote:
atl1c driver is doing order-4 allocation with GFP_ATOMIC
priority. That often breaks networking after resume. Switch to
GFP_KERNEL. Still not ideal, but should be significantly better.
Signed-off-by: Pavel Machek
diff --git
On Tue, Nov 17, 2015 at 11:33 PM, Hongzhou Yang
wrote:
> configs will kmemdup to dup_configs in pictrl util function.
> So configs need to be freed.
>
> Signed-off-by: Hongzhou Yang
> Reviewed-by: Daniel Kurtz
> Reviewed-by: Matthias Brugger
> ---
> Fix a memleak issue.
> According to
On Sun, Nov 29, 2015 at 05:14:03PM -0300, Geyslan Gregório Bem wrote:
> Hello,
>
> I have found a possible out of bounds reading in
> arch/powerpc/kvm/book3s_64_mmu.c (kvmppc_mmu_book3s_64_xlate
> function). pteg[] array could be accessed twice using the i variable
> after the for iteration. What
On Saturday 28 November 2015 21:45:55 Theodore Ts'o wrote:
> On Tue, Nov 24, 2015 at 09:10:53PM +0100, Arnd Bergmann wrote:
> > On Tuesday 24 November 2015 14:36:46 Theodore Ts'o wrote:
> > > This is the patch I would prefer to use (and in fact which I have
> > > added to the ext4 tree):
> > >
>
On Mon, Nov 16, 2015 at 10:26 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Mon, 16 Nov 2015 22:00:28 +0100
>
> The variable "res" will eventually be set to a resource pointer from
> a call of the d40_hw_detect_init(() function.
> Thus let us omit the explicit initialisation at
On Mon, Nov 16, 2015 at 10:24 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Mon, 16 Nov 2015 21:56:07 +0100
>
> A single jump label was used by the d40_probe() function in several cases
> for error handling which was a bit inefficient here.
>
> * This implementation detail could
On Mon, Nov 16, 2015 at 10:23 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Mon, 16 Nov 2015 20:26:27 +0100
>
> The kmem_cache_destroy() function tests whether its argument is NULL
> and then returns immediately. Thus the test around the call is not needed.
>
> This issue was
On Tue, Nov 17, 2015 at 4:18 AM, Magnus Damm wrote:
> From: Koji Matsuoka
>
> r8a7794 PFC DU support from the R-Car Gen2 v1.9.4 BSP
>
> Signed-off-by: Koji Matsuoka
> Signed-off-by: Magnus Damm
Acked-by for all from my side, Geert, I expect that you
queue these with the rest of the SH PFC
Hi Remi,
Am 29.11.2015 um 01:31 schrieb Remi Pommarel:
Hi Stefan,
On Sat, Nov 28, 2015 at 09:52:07PM +0100, Stefan Wahren wrote:
i applied the series including the devicetree modification, but it
doesn't work for me.
First of all i get an ugly division by zero warning from the pwm
driver.
This will probably earn me a reputation as the most single-minded
monomaniac on this planet (insofar there's still anything to earn in
this respect) but this issue has been irking me "ever since".
NB: This is somewhat loser formatted than a proper patch submission in
order to explain the
copy_to_user() and copy_from_user() functions expect the user space
pointers to be marked with __user. Sparse throws following warnings.
For copy_to_user():
warning: incorrect type in argument 1 (different address spaces)
expected void [noderef] *to
got void *buf
For copy_from_user():
warning:
On zo, 2015-11-29 at 19:47 +0100, Tilman Schmidt wrote:
> Btw I don't see a timer_list object in struct platform_device either.
> Nor in the embedded struct device.
I found two instances of struct timer_list, rather deep down struct
ser_cardstate:
struct ser_cardstate {
struct
On 11/25/2015 8:55 AM, Ulf Hansson wrote:
> On 21 November 2015 at 01:17, Joshua Henderson
> wrote:
> > From: Andrei Pistirica
> >
> > This driver supports the SDHCI host controller found on the PIC32 in
> > DMA or PIO mode.
> >
> > Signed-off-by: Andrei Pistirica
> > Signed-off-by: Joshua
Hello,
I have found a possible out of bounds reading in
arch/powerpc/kvm/book3s_64_mmu.c (kvmppc_mmu_book3s_64_xlate
function). pteg[] array could be accessed twice using the i variable
after the for iteration. What happens is that in the last iteration
the i index is incremented to 16, checked
On Fri, Nov 27, 2015 at 01:17:40PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Nov 27, 2015 at 01:03:11PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Fri, Nov 27, 2015 at 09:21:21AM +0100, Jiri Olsa escreveu:
> > > On Thu, Nov 26, 2015 at 05:45:59PM -0300, Arnaldo Carvalho de Melo wrote:
Hi,
I have version 0.0-2 of this installed on my CentOS machines.
When I try to copy an entire hard drive that is formatted with the
hfs+ file system to another, it makes my system completely freeze
after a period of time.
I have tried this on two different CentOS machines of mine and the
same
each vm has 4 nics connected to 4 different bridges which is
connected to 4 different physical interface in access mode VLAN.No
bonding between interfaces.I have IP assigned on "ovirtmgmt" bridge
which is used for storage,migration,console and VM internet access.All
interfaces are 10G with MTU
Hi Linus,
just some nouveau and radeon/amdgpu fixes, the nouveau fixes
look large as the firmware context files are regenerated, but
the actual change is quite small.
Dave.
The following changes since commit 78c4a49a69e910a162b05e4e8727b9bdbf948f13:
Merge branch 'for-linus' of
2015-11-29 8:59 GMT+01:00 Dan Kenigsberg :
> On Sat, Nov 28, 2015 at 08:10:06PM +0530, mad Engineer wrote:
>> hello all i am having strange network issue with vms that are running on
>> centos 6.7 ovirt nodes.
>>
>> I recently added one more ovirt node which is running centos6.7 and
>> upgraded
On Thursday 26 November 2015 15:55:56 Michał Kępień wrote:
> > > /* Shortcut and audio panel keys */
> > >
> > > - { KE_IGNORE, 0xe025, { KEY_RESERVED } },
> > > + { KE_KEY, 0xe025, { KEY_PROG4 } },
> > >
> > > { KE_IGNORE, 0xe026, { KEY_RESERVED } },
> >
> > I'm trying to figure out if
On 28.11.2015 21:58, Pavel Machek wrote:
Ring test failure is often caused by too high agpmode. Tell the user
what to try.
Signed-off-by: Pavel Machek
NAK, the ring test can fail for any number of reasons and the agpmode is
actually rather unlikely to be the cause.
Regards,
Christian.
Running centos 6.7 and trying to PXE boot centos 6.5 vms but some of
them are stuck with this in boot message:
[drm] fb: depth 24,pitch 4096
screenshot of vm console:
http://snag.gy/7Bhyc.jpg
tried restarting vms but its still stuck there
rpm -qa |grep kvm
For some watchdogs, the hardware timeout is fixed, and the
watchdog driver depends on the watchdog core to handle the
actual timeout. In this situation, the watchdog driver might
only set the 'timeout' variable but do nothing else.
This can as well be handled by the infrastructure, so make
the
Some watchdogs require a minimum time between heartbeats.
Examples are the watchdogs in DA9062 and AT91SAM9x.
Signed-off-by: Guenter Roeck
---
v6: Rebased to v4.4-rc2
v5: Rebased to v4.4-rc1
Fixed typo in documentation.
v4: Added patch
---
Documentation/watchdog/watchdog-kernel-api.txt |
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
The infrastructure now also supports generating additional heartbeats
if the maximum hardware timeout is smaller than or close to the
configured timeout. Convert the
The watchdog infrastructure is currently purely passive, meaning
it only passes information from user space to drivers and vice versa.
Since watchdog hardware tends to have its own quirks, this can result
in quite complex watchdog drivers. A number of scanarios are especially common.
- A
Introduce an optional hardware maximum timeout in the watchdog core.
The hardware maximum timeout can be lower than the maximum timeout.
Drivers can set the maximum hardware timeout value in the watchdog data
structure. If the configured timeout exceeds the maximum hardware timeout,
the watchdog
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
Convert the driver to use this infrastructure.
Signed-off-by: Guenter Roeck
---
v6: Rename WDOG_RUNNING to WDOG_HW_RUNNING
Rebased to v4.4-rc2
v5: Rebased to
Drop 'cancel' parameter; simply cancel worker unconditionally
if not needed.
Signed-off-by: Guenter Roeck
---
v6: Rebased to v4.4-rc2
v5: Introduced patch
---
drivers/watchdog/watchdog_dev.c | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
Convert the driver to use this infrastructure.
Signed-off-by: Guenter Roeck
---
v6: Rename WDOG_RUNNING to WDOG_HW_RUNNING
Rebased to v4.4-rc2
v5: Rebased to
Convert driver to use watchdog infrastructure. This includes
infrastructure support to handle watchdog keepalive if the watchdog
is running while the watchdog device is closed.
Signed-off-by: Guenter Roeck
---
v6: Added patch
---
drivers/watchdog/Kconfig | 1 +
drivers/watchdog/dw_wdt.c |
The WDOG_HW_RUNNING flag is expected to be set by watchdog drivers if
the hardware watchdog is running. If the flag is set, the watchdog
subsystem will ping the watchdog even if the watchdog device is closed.
The watchdog driver stop function is now optional and may be omitted
if the watchdog can
On 29.11.2015 17:12, Julia Lawall wrote:
The radeon_asic_ring structures are never modified, so declare them as
const.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
Nice clean, patch is Reviewed-by: Christian König
---
drivers/gpu/drm/radeon/radeon.h |2 -
Hello,
We have the below lists in stock and looking for offers.
CPUs and QTYs in stock.
75 X X5650
55 X E5410
65 X X5660
45 X E5530
75 X E5645
70 X X5680
65 X X5690
IP phones and QTYs in stock.
15 x CP-7937G
57 x CP-7942G
45 x CP-7945G
55 x CP-7962G
Here is the qty in
Am 29.11.2015 um 19:22 schrieb Peter Hurley:
>>> [ 413.536749] WARNING: CPU: 6 PID: 25400 at lib/debugobjects.c:263
>>> debug_print_object+0x1c4/0x1e0()
>>> [ 413.538111] ODEBUG: free active (active state 0) object type: timer_list
>>> hint: delayed_work_timer_fn+0x0/0x90
>>
>> This message
Am 29.11.2015 um 19:22 schrieb Peter Hurley:
> On 11/29/2015 10:30 AM, Tilman Schmidt wrote:
>>
>> Judging from the backtrace below this must be the call
>>
>> kfree(cs->hw.ser);
>>
>> in drivers/isdn/gigaset/ser-gigaset.c line 375.
>> cs->hw.ser is of type struct ser_cardstate *.
>>
On Fri, 20 Nov 2015 21:22:54 -0500
Tom Hebb wrote:
> If we can't find updated links, though,
> perhaps we should remove them altogether. I can send another patch to do
> that, provided no one has new links to the missing documents.
An add-on patch to fix things up would be welcome if you get a
Hi Tilman,
On 11/29/2015 10:30 AM, Tilman Schmidt wrote:
> Hi Sasha,
>
> thanks for the report. As the original author of the code in question, I
> am somewhat at a loss what to make of it.
>
> Am 27.11.2015 um 16:19 schrieb Sasha Levin:
>> Fuzzing with syzkaller on the latest -next kernel
On Sun, Nov 29, 2015 at 02:18:29PM +0100, Dmitry Vyukov wrote:
> ca.key_size = 1;
> ca.value_size = 0xfff9;
> ca.max_entries = 10;
> int fd = syscall(SYS_bpf, BPF_MAP_CREATE, , sizeof(ca));
...
> [ cut here ]
> WARNING: CPU: 2 PID: 11122
On Sunday 29 November 2015 19:09:39 Russell King - ARM Linux wrote:
> On Sat, Nov 28, 2015 at 12:34:23PM -0500, Nicolas Pitre wrote:
> > Good. And Arnd likes the idea too. So we might be converging at
> > last which is a good thing.
>
> I disagree with the idea that there is convergence. There
Hi Linus,
Here are two fixes for the ds1307 driver. I don't expect much more for
this cycle.
The following changes since commit 1ec218373b8ebda821aec00bb156a9c94fad9cd4:
Linux 4.4-rc2 (2015-11-22 16:45:59 -0800)
are available in the git repository at:
On Sun, Nov 29, 2015 at 12:51:30PM +, jp...@tutanota.de wrote:
> The patch for cleaning up the Skein hash implementation is included below.
>
> The test & pass vectors for the hash function have been included, but not
> checked as the competition is still ongoing,as the final specification
Hello Maxime,
Sorry for delayed response.
On Mon, Oct 26, 2015 at 4:20 AM, Maxime Ripard
wrote:
> Hi,
>
> On Fri, Oct 23, 2015 at 07:46:16AM +0800, Vishnu Patekar wrote:
>> + memory {
>> + reg = <0x4000 0x8000>;
>> + };
>> +
>> + timer {
>> +
On Sat, Nov 28, 2015 at 12:34:23PM -0500, Nicolas Pitre wrote:
> Good. And Arnd likes the idea too. So we might be converging at last
> which is a good thing.
I disagree with the idea that there is convergence. There might be
convergence towards an idea, but... Here's a mail extract, from July
On 29 November 2015 at 16:39, Ingo Molnar wrote:
>
> * PaX Team wrote:
>
>> On 29 Nov 2015 at 9:08, Ingo Molnar wrote:
>>
>> >
>> > * PaX Team wrote:
>> >
>> > > i don't see the compile time vs. runtime detection as 'competing'
>> > > approaches,
>> > > both have their own role. [...]
>> >
>>
On 11/29/2015 08:31 AM, Jonathan Cameron wrote:
On 25/11/15 11:28, Marc Titinger wrote:
in SOFTWARE buffer mode, a kthread will capture the active scan_elements
into a kfifo, then compute the remaining time until the next capture tick
and do an active wait (udelay).
This will produce a stream
The snd_i2c_ops structures are never modified, so declare them as const.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
include/sound/i2c.h |2 +-
sound/i2c/i2c.c |2 +-
sound/pci/ice1712/delta.c |2 +-
3 files changed, 3 insertions(+), 3
Hi Jens,
this is just to ask you whether you made any decision about these patches,
including just not to apply them.
Thanks,
Paolo
Il giorno 03/nov/2015, alle ore 10:01, Paolo Valente
ha scritto:
>
> Il giorno 02/nov/2015, alle ore 17:14, Jens Axboe ha scritto:
>
>> On 11/02/2015 07:31
On 18/11/15 07:33, Jonathan Cameron wrote:
>
>
> On 17 November 2015 23:47:16 GMT+00:00, Andrew Morton
> wrote:
>> On Sun, 15 Nov 2015 10:39:08 + Jonathan Cameron
>> wrote:
>>
>>> On 11/11/15 06:43, Jonathan Cameron wrote:
On 10 November 2015 21:12:37 GMT+00:00, Andrew
On 2015.11.29 at 11:49 -0500, Mike Snitzer wrote:
> On Sun, Nov 29 2015 at 11:15am -0500,
> Markus Trippelsdorf wrote:
>
> > On 2015.11.29 at 16:43 +0100, Hannes Reinecke wrote:
> > > On 11/29/2015 12:49 PM, Markus Trippelsdorf wrote:
> > > >
> > > > I'm still seeing the issue (BUG at
On Tue, Nov 24, 2015 at 03:36:57PM +0100, LABBE Corentin wrote:
> of_match_device could return NULL, and so cause a NULL pointer
> dereference later.
> Even if the probability of this case is very low, fixing it made
> static analyzers happy.
> Solving this with of_device_get_match_data made also
On Sun, Nov 29 2015 at 11:15am -0500,
Markus Trippelsdorf wrote:
> On 2015.11.29 at 16:43 +0100, Hannes Reinecke wrote:
> > On 11/29/2015 12:49 PM, Markus Trippelsdorf wrote:
> > >
> > > I'm still seeing the issue (BUG at drivers/scsi/scsi_lib.c:1096!) even
> > > with this patch applied.
> > >
On 25/11/15 11:28, Marc Titinger wrote:
> This can lead to repeated or skipped samples depending on the clock beat
> between the capture thread and the chip sampling clock, but will also spare
> reading/waiting for the Capture Ready Flag and improve the available i2c
> bandwidth for reading
The ACCES 104-IDI-48 family of PC/104 utility boards feature 48
individually optically isolated digital inputs. Enabled inputs feature
change-of-state detection capability; if change-of-state detection is
enabled, an interrupt is fired off if a change of input level
(low-to-high or high-to-low) is
On 25/11/15 11:28, Marc Titinger wrote:
> in SOFTWARE buffer mode, a kthread will capture the active scan_elements
> into a kfifo, then compute the remaining time until the next capture tick
> and do an active wait (udelay).
>
> This will produce a stream of up to fours channels plus a 64bits
>
The device table is required to load modules based on modaliases.
Signed-off-by: Enric Balletbo i Serra
---
Changes since last version:
- Use of_match_ptr (Lee Jones)
drivers/video/backlight/tps65217_bl.c | 9 +
1 file changed, 9 insertions(+)
diff --git
The radeon_asic_ring structures are never modified, so declare them as
const.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
drivers/gpu/drm/radeon/radeon.h |2 -
drivers/gpu/drm/radeon/radeon_asic.c | 38 +--
2 files changed, 20
Hi Arnaldo,
On Fri, Nov 27, 2015 at 10:10:54PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Nov 27, 2015 at 08:47:38AM +, Wang Nan escreveu:
> > bpf__config_obj() is introduced as a core API to config BPF object
> > after loading. One configuration option of maps is introduced. After
> >
On 2015.11.29 at 16:43 +0100, Hannes Reinecke wrote:
> On 11/29/2015 12:49 PM, Markus Trippelsdorf wrote:
> > On 2015.11.26 at 08:11 -0500, Mike Snitzer wrote:
> >> On Thu, Nov 26 2015 at 2:46am -0500,
> >> Hannes Reinecke wrote:
> >>
> >>> When a cloned request is retried on other queues it
Hi Wang,
On Fri, Nov 27, 2015 at 08:47:36AM +, Wang Nan wrote:
> This patch collects name of maps in BPF object files and saves them into
> 'maps' field in 'struct bpf_object'. 'bpf_object__get_map_by_name' is
> introduced to retrive fd and definitions of a map through its name.
>
>
On 24/11/15 10:59, Adriana Reus wrote:
> Keep track of the als and px enabled/disabled status in
> order to enable them selectively.
>
> Signed-off-by: Adriana Reus
Couple more nitpicks, but again fixed up during apply.
> ---
> drivers/iio/light/us5182d.c | 64
>
The action_ops structures are never modified, so declare them as const.
Done with the help of Coccinelle.
Signed-off-by: Julia Lawall
---
sound/core/pcm_native.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/sound/core/pcm_native.c
201 - 300 of 754 matches
Mail list logo