> Are you aware of other cases where we're likely to run into problems
> besides ext4_new_inode()?
Nope. If we can get ext4_new_inode() case covered we should be fine.
I will abandon this patch and will work on a patch that adds extra
credits in __ext4_new_inode().
thanks
On 03/07/17 23:08, Stefano Stabellini wrote:
> Introduce the C header file which defines the PV Calls interface. It is
> imported from xen/include/public/io/pvcalls.h.
>
> Signed-off-by: Stefano Stabellini
> Reviewed-by: Boris Ostrovsky
On Tue, 4 Jul 2017 17:58:18 +1000
Stephen Rothwell wrote:
> Hi Linus,
>
> On Mon, 3 Jul 2017 15:46:00 -0700 Linus Torvalds
> wrote:
> >
> > On Mon, Jul 3, 2017 at 2:01 AM, Martin Schwidefsky
> > wrote:
> > >
> >
On Tue, Jul 04, 2017 at 09:15:55AM +0200, Geert Uytterhoeven wrote:
> Hi Greg, Heikki,
>
> On Mon, Jul 3, 2017 at 4:58 PM, Greg KH wrote:
> > The following changes since commit 41f1830f5a7af77cf5c86359aba3cbd706687e52:
> >
> > Linux 4.12-rc6 (2017-06-19 22:19:37
Hi Frank,
Am Dienstag, 4. Juli 2017, 16:12:42 CEST schrieb Frank Wang:
> This patch adds vcc_io, vdd_arm and vdd_log regulator nodes
> for rk3229-evb board.
>
> Signed-off-by: Frank Wang
> ---
> arch/arm/boot/dts/rk3229-evb.dts | 54
>
On Tue, Jul 04, 2017 at 09:27:07AM +0200, Peter Zijlstra wrote:
> On Sat, Jul 01, 2017 at 07:06:13AM +0200, Vincent Guittot wrote:
> > The running state is a subset of runnable state which means that running
> > can't be set if runnable (weight) is cleared. There are corner cases
> > where the
on big endian
>> systems, this depends on "[PATCH v3 0/3] Define CPU_BIG_ENDIAN or warn for
>> inconsistencies".
>> https://lkml.org/lkml/2017/6/12/1068
>
> Is this a problem?
I have no idea what happens if you enable the driver on big endian.
> I thought that series was s
On 06/29/2017 12:46 PM, Abhishek Sahu wrote:
1. Add the function for command descriptor preparation which
will be used only by BAM DMA and it will form the DMA descriptors
containing command elements.
2. Add the data descriptor preparation function which will be used
only by BAM
On Tue, Jul 04, 2017 at 11:12:34AM +0200, Vincent Guittot wrote:
> On 4 July 2017 at 10:34, Peter Zijlstra wrote:
> > On Tue, Jul 04, 2017 at 09:27:07AM +0200, Peter Zijlstra wrote:
> >> On Sat, Jul 01, 2017 at 07:06:13AM +0200, Vincent Guittot wrote:
> >> > The running
On Tue, 4 Jul 2017, Andy Shevchenko wrote:
> On Tue, Jul 4, 2017 at 12:11 PM, Julia Lawall wrote:
> > Here is a revised version (not a patch because it doesn't support all of
> > the various modes) and the results. It doesn't return anything beyond
> > what was mentioned
* Peter Zijlstra wrote:
> > An intermediate approach to improve that skew would be something like
> > below.
> > It doesn't track the remainder like your patch does, but doesn't lose
> > precision either, just rounds down 'now' to the nearest 1024 boundary.
>
> > diff
On 04/07/17 10:56, Suzuki K Poulose wrote:
> This series contains some fixes for GIC/GIC-v3 to behave as expected
> by the generic management layer.
>
> Suzuki K Poulose (3):
> irqchip: gic-v3: Report failures in gic_irq_domain_alloc
> irqchip: gic-v2: Report failures in gic_irq_domain_alloc
2017-06-28 0:51 GMT+02:00 Kees Cook :
> On Mon, Jun 12, 2017 at 9:56 AM, Salvatore Mesoraca
> wrote:
>> Adding documentation for S.A.R.A. LSM.
>>
>> Signed-off-by: Salvatore Mesoraca
>> ---
>>
On 03-07-17, 16:07, Mark Brown wrote:
> On Mon, Jul 03, 2017 at 11:45:52AM +0530, Viresh Kumar wrote:
> > The above regulator-min/max-microvolt values I mentioned were for the
> > regulator
> > device and not what the consumers would request. Yes, DMA will request
> > something
>
> If you're
On 2017/6/29 16:22, Xishi Qiu wrote:
> centos 7.2,I got some oops form my production line,
> Anybody has seen these errors before?
>
Here is another one
[ 703.025737] BUG: unable to handle kernel NULL pointer dereference at
0d68
[ 703.026008] IP: [] mlx4_en_QUERY_PORT+0xa2/0x190
Hi Boris,
在 2017/7/4 2:36, Boris Brezillon 写道:
Hm, maybe it's time to drop these custom hooks and implement
pwm_apply_v1 and pwm_apply_v2 instead.
Okay, drop the enable and config hooks, only use the apply hook to
instead them.
Hi Greg, Heikki,
On Mon, Jul 3, 2017 at 4:58 PM, Greg KH wrote:
> The following changes since commit 41f1830f5a7af77cf5c86359aba3cbd706687e52:
>
> Linux 4.12-rc6 (2017-06-19 22:19:37 +0800)
>
> are available in the git repository at:
>
>
Hi Thomas,
At 07/04/2017 03:19 PM, Thomas Gleixner wrote:
On Tue, 4 Jul 2017, Dou Liyang wrote:
At 07/03/2017 10:22 PM, Colin King wrote:
-int normal_busy(struct bau_control *bcp)
+static int normal_busy(struct bau_control *bcp)
In my opinion, there is no need to mark *normal_busy* static,
On 03/07/17 23:08, Stefano Stabellini wrote:
> When the other end notifies us that there is data to be written
> (pvcalls_back_conn_event), increment the io and write counters, and
> schedule the ioworker.
>
> Implement the write function called by ioworker by reading the data from
> the data
On 03/07/17 23:08, Stefano Stabellini wrote:
> Also add pvcalls-back to the Makefile.
>
> Signed-off-by: Stefano Stabellini
Reviewed-by: Juergen Gross
Thanks,
Juergen
Now function process_e820_entry is only used to process e820 memory
entries. Adapt it for any type of memory entry, not just for e820.
Later we will use it to process efi mirror regions.
So rename the old process_e820_entry to process_mem_region, and
extract and wrap the e820 specific processing
Kernel text may be located in non-mirror regions (movable zone) when both
address range mirroring feature and KASLR are enabled.
The address range mirroring feature arranges such mirror region into
normal zone and other region into movable zone in order to locate
kernel code and data in mirror
On 03/07/17 23:08, Stefano Stabellini wrote:
> Keep a list of connected frontends. Use a semaphore to protect list
> accesses.
>
> Signed-off-by: Stefano Stabellini
> Reviewed-by: Boris Ostrovsky
Reviewed-by: Juergen Gross
On Tue, 4 Jul 2017 10:05:30 +0200
Martin Schwidefsky wrote:
> On Tue, 4 Jul 2017 17:58:18 +1000
> Stephen Rothwell wrote:
>
> > Hi Linus,
> >
> > On Mon, 3 Jul 2017 15:46:00 -0700 Linus Torvalds
> > wrote:
> > >
On Mon, 3 Jul 2017, Chen Yu wrote:
> On Sun, Jun 04, 2017 at 10:04:53PM +0200, Thomas Gleixner wrote:
> > After looking at the callsites, it's safe to change
> > irq_set_affinity_locked() so that it uses the direct affinity setter
> > function when force == true.
> >
> Sorry it took me sometime
On Tue 04-07-17 10:45:43, Vlastimil Babka wrote:
> Hi,
>
> I realize this is against the standard stable policy, but I see no other
> way, because the mainline accidental fix is part of 34+ patch reclaim
> rework, that would be absurd to try to backport into stable. The fix is
> a one-liner
On Tue, Jul 04, 2017 at 10:22:44AM +0200, Peter Rosin wrote:
> The MULTIPLEXER question in the Kconfig might be confusing and is
> of dubious value. Remove it. This makes consumers responsible for
> selecting MULTIPLEXER, which they already do.
>
> Signed-off-by: Peter Rosin
>
On Thu, Jun 29, 2017 at 10:12:33AM +0200, Ingo Molnar wrote:
>
> * Mark Rutland wrote:
>
> > It still seems wrong to make up data, though.
>
> So what we have here is a hardware quirk: we asked for user-space samples,
> but
> didn't get them and we cannot expose the
On 4 July 2017 at 09:19, Jisheng Zhang wrote:
> On Tue, 4 Jul 2017 09:02:06 +0100 Ard Biesheuvel wrote:
>
>> On 4 July 2017 at 07:58, Jisheng Zhang wrote:
>> > On Mon, 3 Jul 2017 08:27:04 -0500 wrote:
>> >
>> >> [+cc Jingoo, Joao]
>> >>
>> >> On Mon, Jul
* Peter Zijlstra wrote:
> Argh, no... That code was perfectly fine. The new code otoh is
> convoluted crap.
>
> It had the form:
>
> if (exception1)
> deal with exception1
>
> if (execption2)
> deal with exception2
>
> do normal stuff
On Tue 04-07-17 09:21:00, zhouxianrong wrote:
> the test was done as follows:
>
> 1. the environment is android 7.0 and kernel is 4.1 and managed memory is
> 3.5GB
There have been many changes in the compaction proper since than. Do you
see the same problem with the current upstream kernel?
>
On 03/07/17 23:08, Stefano Stabellini wrote:
> Introduce a per-frontend data structure named pvcalls_fedata. It
> contains pointers to the command ring, its event channel, a list of
> active sockets and a tree of passive sockets (passing sockets need to be
> looked up from the id on listen, accept
> Il giorno 04 lug 2017, alle ore 00:49, Jens Axboe ha
> scritto:
>
> On 07/03/2017 02:00 AM, Paolo Valente wrote:
>> Hi Jens,
>> I'm writing this short cover letter to hopefully help you decide what
>> to do with this patch, in this late phase of the development
>> cycle.
On Tue, 4 Jul 2017 14:58:40 +0800 Jisheng Zhang wrote:
> On Mon, 3 Jul 2017 08:27:04 -0500 wrote:
>
> > [+cc Jingoo, Joao]
> >
> > On Mon, Jul 03, 2017 at 10:35:50AM +0100, Ard Biesheuvel wrote:
> > > On 3 July 2017 at 00:18, Bjorn Helgaas wrote:
> > > > On Tue, Jun
On 03/07/17 23:08, Stefano Stabellini wrote:
> Release both active and passive sockets. For active sockets, make sure
> to avoid possible conflicts with the ioworker reading/writing to those
> sockets concurrently. Set map->release to let the ioworker know
> atomically that the socket will be
On 03/07/17 23:08, Stefano Stabellini wrote:
> Implement backend_disconnect. Call pvcalls_back_release_active on active
> sockets and pvcalls_back_release_passive on passive sockets.
>
> Implement module_exit by calling backend_disconnect on frontend
> connections.
>
> Signed-off-by: Stefano
On Mon, Jul 03, 2017 at 12:25:48PM -0700, kernelci.org bot wrote:
> stable-rc/linux-4.9.y boot: 130 boots: 5 failed, 112 passed with 13 offline
> (v4.9.35-173-g45949a8fd1df)
>
> Full Boot Summary:
> https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.35-173-g45949a8fd1df/
On 4 July 2017 at 07:58, Jisheng Zhang wrote:
> On Mon, 3 Jul 2017 08:27:04 -0500 wrote:
>
>> [+cc Jingoo, Joao]
>>
>> On Mon, Jul 03, 2017 at 10:35:50AM +0100, Ard Biesheuvel wrote:
>> > On 3 July 2017 at 00:18, Bjorn Helgaas wrote:
>> > > On Tue, Jun
On Mon, Jul 03, 2017 at 01:25:47PM -0700, kernelci.org bot wrote:
> stable-rc/linux-4.4.y boot: 149 boots: 6 failed, 94 passed with 49 offline
> (v4.4.75-102-g77af3cab5b0c)
>
> Full Boot Summary:
> https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.75-102-g77af3cab5b0c/
On Tue, 4 Jul 2017 09:02:06 +0100 Ard Biesheuvel wrote:
> On 4 July 2017 at 07:58, Jisheng Zhang wrote:
> > On Mon, 3 Jul 2017 08:27:04 -0500 wrote:
> >
> >> [+cc Jingoo, Joao]
> >>
> >> On Mon, Jul 03, 2017 at 10:35:50AM +0100, Ard Biesheuvel wrote:
> >> > On 3 July
Am Dienstag, 4. Juli 2017, 16:12:45 CEST schrieb Frank Wang:
> This patch enables eMMC support for rk3229-evb board.
>
> Signed-off-by: Frank Wang
> ---
> arch/arm/boot/dts/rk3229-evb.dts | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git
On Tue, 4 Jul 2017 11:12:17 +0200
Greg Kroah-Hartman gre...@linuxfoundation.org wrote:
...
>> Is this series queued for merging in 4.13-rc1 ?
>
>Nope, it missed my merge window for that, sorry. I'll queue them up to
>my tree after 4.13-rc1 is out. If there are any specific bugfixes in
>here
On 07/04/2017 07:23 AM, Joonsoo Kim wrote:
> On Mon, Jul 03, 2017 at 04:18:01PM +0200, Vlastimil Babka wrote:
>> allocated" looks much more sane there. But there's a warning nevertheless.
>
> Warning would comes from the fact that drain_all_pages() is called
> before mm_percpu_wq is initialised.
On 07/04/17 11:28, Jose Abreu wrote:
> Hi Hans,
>
>
> On 03-07-2017 11:33, Hans Verkuil wrote:
>> On 07/03/2017 11:53 AM, Jose Abreu wrote:
>>> Hi Hans,
>>>
>>>
>>> On 03-07-2017 10:27, Hans Verkuil wrote:
On 06/29/2017 12:46 PM, Jose Abreu wrote:
> This is an initial submission for the
On 06/29/2017 12:46 PM, Abhishek Sahu wrote:
1. The BAM mode requires few registers configuration before each
NAND page read and codeword read which is different from ADM
so add the helper functions which will be called in BAM mode
only.
2. The NAND page read handling of BAM is
* Peter Zijlstra wrote:
> On Thu, Jun 29, 2017 at 10:12:33AM +0200, Ingo Molnar wrote:
> >
> > * Mark Rutland wrote:
> >
> > > It still seems wrong to make up data, though.
> >
> > So what we have here is a hardware quirk: we asked for user-space
Hi Sean,
> This patchset introduces Consumer IR (CIR) support for MT7622 SoC
> implements raw mode for more compatibility with different protocols
> as previously SoC did. Before adding support to MT7622 SoC, extra
> code refactor is done since there're major differences in register and
> field
Hi gengdongjiu,
Can you give us a specific example of an error you are trying to handle?
How would a non-KVM user space process handle the error?
KVM-users should be regular user space processes, we should not have a KVM-way
and everyone-else-way of handling errors.
On 04/07/17 05:46,
From: Yunsheng Lin
If driver support checksum offload, should check netdev feature
before fill TX description and get CSUM err bit from RX
description. HNS driver do the check in RX derction but it doesn't
do the check in TX direction.
Signed-off-by: lipeng
On Tue, Jul 04, 2017 at 10:33:45AM +0100, Mark Rutland wrote:
> On Tue, Jul 04, 2017 at 11:03:13AM +0200, Peter Zijlstra wrote:
> > Faking data gets a wee bit tricky in how much data we need to clear
> > through, its not only IP, pretty much everything we get from the
> > interrupt context, like
This makes the redundant fb helpers .load_lut, .gamma_set and .gamma_get
completely obsolete.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/drm_fb_helper.c | 165 +++-
1 file changed, 94 insertions(+), 71 deletions(-)
diff --git
2017-07-04 19:06 GMT+09:00 Andy Shevchenko :
> On Tue, 2017-07-04 at 12:53 +0900, Masahiro Yamada wrote:
>> Some of include directives in include/linux/gpio/driver.h are
>> unneeded because the header does not need to know the content of
>> struct device,
Hi Nicholas,
On Sun, May 14, 2017 at 10:43 AM, Nicholas Mc Guire wrote:
> If the timeout-case prints a warning message then probably the interrupted
> case should also. Further, wait_for_completion_interruptible_timeout()
> returns long not int.
>
> Fixes: commit 03b262f2bbf4
Hi!
While trying to get CLUT support for the atmel_hlcdc driver, and
specifically for the emulated fbdev interface, I received some
push-back that my feeble in-driver attempts should be solved
by the core. This is my attempt to do it right.
I have obviously not tested all of this with more than
On 4 July 2017 at 02:00, Cyrille Pitchen wrote:
> Hi Matthew,
>
>
> Le 26/06/2017 à 18:13, matthew.gerl...@linux.intel.com a écrit :
>> From: Matthew Gerlach
>> +static int altera_quadspi_setup_banks(struct device *dev,
>> +
drm_fb_helper_save_lut_atomic is redundant since the .gamma_store is
now always kept up to date by drm_fb_helper_setcmap.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/drm_fb_helper.c | 17 -
1 file changed, 17 deletions(-)
diff --git
Commit-ID: e5682b4eecb2b73282853d0ef314d3164b986997
Gitweb: http://git.kernel.org/tip/e5682b4eecb2b73282853d0ef314d3164b986997
Author: Sebastian Ott
AuthorDate: Tue, 4 Jul 2017 11:25:15 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 4
Commit-ID: 2343877fbda701599653e63f8dcc318aa1bf15ee
Gitweb: http://git.kernel.org/tip/2343877fbda701599653e63f8dcc318aa1bf15ee
Author: Thomas Gleixner
AuthorDate: Thu, 29 Jun 2017 23:33:39 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 4 Jul
On Tue, Jul 4, 2017 at 12:15 PM, Chunyan Zhang
wrote:
> This patch added FM radio driver for Spreadtrum's SC2342, which's
> a WCN SoC, also added a new directory for Spreadtrum's WCN SoCs.
>
> Signed-off-by: Songhe Wei
> Signed-off-by:
Commit-ID: 9114014cf4e6df0b22d764380ae1fc54f1a7a8b2
Gitweb: http://git.kernel.org/tip/9114014cf4e6df0b22d764380ae1fc54f1a7a8b2
Author: Thomas Gleixner
AuthorDate: Thu, 29 Jun 2017 23:33:37 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 4 Jul
Commit-ID: 46e48e257360f0845fe17089713cbad4db611e70
Gitweb: http://git.kernel.org/tip/46e48e257360f0845fe17089713cbad4db611e70
Author: Thomas Gleixner
AuthorDate: Thu, 29 Jun 2017 23:33:38 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 4 Jul
Commit-ID: 3a90795e1e885167209056a1a90be965add30e25
Gitweb: http://git.kernel.org/tip/3a90795e1e885167209056a1a90be965add30e25
Author: Thomas Gleixner
AuthorDate: Thu, 29 Jun 2017 23:33:36 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 4 Jul
On 2017/7/1 11:06, "Eduardo Valentin" wrote:>
> On Thu, Jun 22, 2017 at 11:42:03AM +0800, Tao Wang wrote:
> > Bind thermal sensor driver for Hi3660.
> >
> > Signed-off-by: Tao Wang
> > Signed-off-by: Leo Yan
> > ---
> >
On Mon, 2017-07-03 at 13:01 +0530, Arvind Yadav wrote:
> attribute_groups are not supposed to change at runtime. All functions
> working with attribute_groups provided by work with const
> attribute_group. So mark the non-const structs as const.
>
> File size before:
> text data
On Tue, 2017-07-04 at 12:42 +0200, Michal Hocko wrote:
> On Tue 04-07-17 11:47:28, Willy Tarreau wrote:
> > On Tue, Jul 04, 2017 at 11:35:38AM +0200, Michal Hocko wrote:
[...]
> > But wouldn't this completely disable the check in case such a guard page
> > is installed, and possibly continue to
On Tue, Jul 04, 2017 at 01:24:14PM +0200, Michal Hocko wrote:
> On Tue 04-07-17 16:04:52, zhouxianrong wrote:
> > every 2s i sample /proc/buddyinfo in the whole test process.
> >
> > the last about 90 samples were sampled after the test was done.
>
> I've tried to explain to you that numbers
On Tue, Jul 4, 2017 at 8:14 AM, Jan Kiszka wrote:
> On 2017-06-09 20:36, Jan Kiszka wrote:
>> Call directly into acpica to load a table to obtain its index on return.
>> We choose the direct call of acpica internal functions to avoid having
>> to modify its API which is
On 07/04/2017 11:32 AM, Thomas Gleixner wrote:
> The rework of the cpu hotplug locking unearthed potential deadlocks with
> the memory hotplug locking code.
>
> The solution for these is to rework the memory hotplug locking code as well
> and take the cpu hotplug lock before the memory hotplug
Hi Eric,
On 15/06/17 13:52, Eric Auger wrote:
> Currently, the line level of unmapped level sensitive SPIs is
> toggled down by the maintenance IRQ handler/resamplefd mechanism.
>
> As mapped SPI completion is not trapped, we cannot rely on this
> mechanism and the line level needs to be
On 04/07/17 00:55, Ben Hutchings wrote:
> Unfortunately these regressions have not been completely fixed by
> switching to Hugh's fix.
>
> Firstly, some Rust programs are crashing on ppc64el with 64 KiB pages.
> Apparently Rust maps its own guard page at the lower limit of the stack
>
On 04-07-2017 10:39, Hans Verkuil wrote:
>
>> +static const struct v4l2_subdev_video_ops
>> dw_hdmi_sd_video_ops = {
>> +.s_routing = dw_hdmi_s_routing,
>> +.g_input_status = dw_hdmi_g_input_status,
>> +.g_parm = dw_hdmi_g_parm,
>> +.g_dv_timings =
As there is no way to actually query the hardware for the current clock
rate, now racalc_rate() just returns the last rate that was previously
set. But if the rate was not set yet, we return the bogus rate of 1KHz.
Knowing what the rate of XO is and that some clocks are just branches of
it, we
On Tue 04-07-17 13:21:02, Ben Hutchings wrote:
> On Tue, 2017-07-04 at 14:00 +0200, Michal Hocko wrote:
> > On Tue 04-07-17 12:36:11, Ben Hutchings wrote:
> > > On Tue, 2017-07-04 at 12:42 +0200, Michal Hocko wrote:
> > > > On Tue 04-07-17 11:47:28, Willy Tarreau wrote:
> > > > > On Tue, Jul 04,
On Tue, Jul 04, 2017 at 02:21:50PM +0200, Peter Zijlstra wrote:
> On Tue, Jul 04, 2017 at 12:13:09PM +0200, Ingo Molnar wrote:
> >
> > This code on the other hand:
> >
> > sa->last_update_time += delta << 10;
> >
> > ... in essence creates a whole new absolute clock value that slowly but
>
Hi,
On 04/07/2017 14:37, Quentin Schulz wrote:
When phy-sun4i-usb's probing fails, it does not print the reason in
kernel log, forcing the developer to edit this driver to add info logs.
This commit makes the kernel print the reason of phy-sun4i-usb's probing
failure or a success message.
On Tue 04-07-17 14:48:56, Thomas Gleixner wrote:
> On Tue, 4 Jul 2017, Michal Hocko wrote:
> > On Tue 04-07-17 11:32:33, Thomas Gleixner wrote:
> > > The rework of the cpu hotplug locking unearthed potential deadlocks with
> > > the memory hotplug locking code.
> > >
> > > The solution for these
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
According to GregKH's suggestion [1], we tried to simply sort out the
FM driver source code which has been using in the internal projects.
Hopes it can help for fixing the problem raised in [1].
[1] https://lkml.org/lkml/2017/6/28/222
Chunyan Zhang (2):
arm64: dts: add Spreadtrum's fm support
Added FM support for Spreadtrum's SP9860 board.
Signed-off-by: Songhe Wei
Signed-off-by: Chunyan Zhang
---
arch/arm64/boot/dts/sprd/sp9860g-1h10.dts | 4
1 file changed, 4 insertions(+)
diff --git
+Tony, Arnd,
Hi,
On Friday 19 May 2017 02:16 PM, Kishon Vijay Abraham I wrote:
> The error handling code in omap_ocp2scp_probe fails to invoke
> pm_runtime_disable and fails to initialize return value in
> certain cases. Fix it here.
Can this patch be picked into arm-soc tree?
Thanks
Kishon
>
On Tue, Jul 4, 2017 at 8:26 AM, Yang Jiaxun wrote:
> From 8db74a4eef334f614bf727232e5b88f67f824862 Mon Sep 17 00:00:00 2001
> From: Yang Jiaxun
> Date: Tue, 4 Jul 2017 11:28:41 +0800
> Subject: [PATCH] ideapad-laptop: Add several models to no_hw_rfkill
>
>
From: Colin Ian King
Array type_array can be made static const rather than being
populated on the stack. Makes the object code smaller:
Before:
textdata bss dec hex filename
80871496 09583256f drivers/usb/renesas_usbhs/pipe.o
On 2017-07-04 12:36, Peter Rosin wrote:
> The pseudo-palette has nothing to do with the crtc, so move it
> out of the crtc loop and update the palette once, then break out
> early.
>
> Signed-off-by: Peter Rosin
Should of course be p...@axentia.se
I wonder when I managed to
On Tue 04-07-17 11:32:34, Thomas Gleixner wrote:
> Andrey reported a potential deadlock with the memory hotplug lock and the
> cpu hotplug lock.
>
> The reason is that memory hotplug takes the memory hotplug lock and then
> calls stop_machine() which calls get_online_cpus(). That's the reverse
Hi Mark,
On 3 July 2017 at 17:36, Mark Brown wrote:
> On Mon, Jul 03, 2017 at 05:33:03PM +0200, Waldemar Rymarkiewicz wrote:
>
>> I've asked also on TI forum if this is typical to the regulator not to
>> determine the startup voltage but still waiting for feedback. Anyway,
>>
On Tue 04-07-17 11:32:33, Thomas Gleixner wrote:
> The rework of the cpu hotplug locking unearthed potential deadlocks with
> the memory hotplug locking code.
>
> The solution for these is to rework the memory hotplug locking code as well
> and take the cpu hotplug lock before the memory hotplug
On 07/03/2017 02:51 PM, Michal Hocko wrote:
> On Mon 03-07-17 13:58:59, Anshuman Khandual wrote:
>> On 06/30/2017 07:52 PM, Michal Hocko wrote:
>>> On Fri 30-06-17 11:59:37, Anshuman Khandual wrote:
Hello,
execve() system call should support argument length of
MAX_ARG_STRLEN
On Tue, Jul 04, 2017 at 11:57:12AM +0200, Vincent Guittot wrote:
> On 4 July 2017 at 11:44, Peter Zijlstra wrote:
> > But but but, how can that happen? Should it not all be under the same
> > rq->lock and thus have only a single update_rq_clock() and thus be at
> > the same
On 2017/7/1 11:06, "Eduardo Valentin" wrote:>
> Hey Tao,
>
> On Thu, Jun 22, 2017 at 11:42:02AM +0800, Tao Wang wrote:
> > This patch adds the support for thermal sensor of Hi3660 SoC.
> > this will register sensors for thermal framework and use device
> > tree to bind
On Tue 04-07-17 16:04:52, zhouxianrong wrote:
> every 2s i sample /proc/buddyinfo in the whole test process.
>
> the last about 90 samples were sampled after the test was done.
I've tried to explain to you that numbers without a proper testing
metodology and highlevel metrics you are interested
Several distributions mount the "proper root" as ro during initrd and
then remount it as rw before pivot_root(2). Thus, if a rescan had been
aborted by a previous shutdown, the rescan would never be resumed.
This issue would manifest itself as several btrfs ioctl(2)s causing the
entire machine to
101 - 200 of 1354 matches
Mail list logo