Change hwspinlock to a bool in case some drivers will meet dependency
issue when hwspinlock is built as a module.
Signed-off-by: Baolin Wang
---
drivers/hwspinlock/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwspinlock/Kconfig b/drivers/hwspinlock/Kconfig
This patch fixes the warning of label 'err_map' defined but not used.
Signed-off-by: Baolin Wang
---
drivers/base/regmap/regmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/regmap/regmap.c b/drivers/base/regmap/regmap.c
index bfe2f25..8d516a9 100644
--- a/dr
On Wed, Nov 1, 2017 at 12:35 PM, Steve Muckle wrote:
> On 10/30/2017 12:02 PM, Joel Fernandes wrote:
>>>
>>> Also, this more looks like a policy decision. Will it be better to
>>> put that directly into schedutil? Like this:
>>>
>>> if (cpu_idle())
>>> "Don't change the f
On Mon, Oct 30, 2017 at 8:03 PM, Lin Huang wrote:
> Document a "reset" and "assert-reset-us", it can be used for
> driver control reset property. And reuse post-power-on-delay-ms
> for deassert reset delay.
>
> Signed-off-by: Lin Huang
> ---
> Documentation/devicetree/bindings/input/hid-over-i2c
Remove jprobe test case because jprobe is deprecated
feature. We must not use it.
Signed-off-by: Masami Hiramatsu
---
arch/arm/probes/kprobes/test-core.c | 57 ---
1 file changed, 57 deletions(-)
diff --git a/arch/arm/probes/kprobes/test-core.c
b/arch/arm/prob
Hi,
This series fixes a typo and remove jprobe test case
because jprobe is deprecated feature. The typo is
related to jprobe so need to be fixed in this series.
Thank you,
---
Masami Hiramatsu (2):
arm: kprobes: Fix kretprobe test to check correct counter
arm: kprobes: Remove jprobe
test_kretprobe() uses jprobe_func_called at the
last test, but it must check kretprobe_handler_called.
Signed-off-by: Masami Hiramatsu
---
arch/arm/probes/kprobes/test-core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/probes/kprobes/test-core.c
b/arch/arm/pr
On (11/02/17 06:52), Tejun Heo wrote:
>
> When printk flushing isn't contended, whoever creates messages get to
> flush them, which is great in both fairness and keeping log delivery
> synchronous. However, when console drivers can't keep up with the
> rate of new messages, which happens a lot, w
On Thu, Nov 02, 2017 at 11:24:31PM +0800, Ming Lei wrote:
> Hi Jens,
>
> This patchset avoids to allocate driver tag beforehand for flush rq
> in case of I/O scheduler, then flush rq isn't treated specially
> wrt. get/put driver tag, code gets cleanup much, such as,
> reorder_tags_to_front() is re
Propagate the error of devfreq_add_device() in devm_devfreq_add_device()
rather than statically returning ENOMEM. This makes it slightly faster
to pinpoint the cause of a returned error.
Signed-off-by: Bjorn Andersson
---
drivers/devfreq/devfreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deleti
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Friday, November 3, 2017 7:53 PM
> To: Limonciello, Mario
> Cc: Andy Shevchenko ; LKML ker...@vger.kernel.org>; platform-driver-...@vger.kernel.org;
> pali.ro...@gmail.com
> Subject: Re: [PATCH 2/2] platform/x8
On (11/02/17 23:15), Steven Rostedt wrote:
> On Thu, 2 Nov 2017 23:16:16 +0100
> Vlastimil Babka wrote:
>
> > > + if (spin) {
> > > + /* We spin waiting for the owner to release us
> > > */
> > > + spin_acquire(&console_owner_dep_ma
On 2017-10-27 at 09:59:38 +0200, Rafael J. Wysocki wrote:
> On Fri, Oct 27, 2017 at 4:01 AM, Ramesh Thomas
> wrote:
> > Individual CPUs may have special requirements to not enter
> > deep idle states. For example, a CPU running real time
> > applications would not want to enter deep idle states t
On 2017-11-03 at 12:50:15 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The special value of 0 for device resume latency PM QoS means
> "no restriction", but there are two problems with that.
>
> First, device resume latency PM QoS requests with 0 as the
> value are always put in
On 2017-11-03 at 12:47:20 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The genpd governor currently uses negative PM QoS values to indicate
> the "no suspend" condition and 0 as "no restriction", but it doesn't
> use them consistently. Moreover, it tries to refresh QoS values fo
On 2017-11-03 at 09:39:08 -0700, Reinette Chatre wrote:
> Hi Rafael,
>
> I started to test this but found myself triggering one of the warnings:
>
> On 11/3/2017 4:50 AM, Rafael J. Wysocki wrote:
> > --- linux-pm.orig/include/linux/pm_qos.h
> > +++ linux-pm/include/linux/pm_qos.h
> > @@ -28,16 +2
On Tue, Oct 31, 2017 at 11:03:15AM +0800, Lin Huang wrote:
> some i2c hid devices have reset gpio, need to control
> it in the driver.
>
> Signed-off-by: Lin Huang
> ---
> Changes in v2:
> - Add 10us in usleep_range() upper range
> - reuse post_power_delay_ms as deassert reset delay
> - delete de
On Fri, Nov 03, 2017 at 12:56:47PM -0700, Sami Tolvanen wrote:
> On Fri, Nov 03, 2017 at 07:26:35PM +, Mark Rutland wrote:
> > I guess that in Google you haven't tested on a platform with EL2
> > available?
>
> Correct. I'll look into this and include a fix in v2. Does this work on a
> clang b
This patch series fixes inefficiencies and lock contention in the request
firmware paths.
Changes since v2:
- Addressed Andre's review comments. Removed fw_buf->virt null check
as it is not needed. Removed handling s5p_mfc_load_firmware() from
probe routine. Simply try loading in case it works
s5p_mfc_load_firmware() will not get called if fw_buf.virt allocation
fails. The allocation happens very early on in the probe routine and
probe fails if allocation fails.
There is no need to check if it is null in s5p_mfc_load_firmware().
Remove the check.
Signed-off-by: Shuah Khan
---
drivers
Driver calls request_firmware() whenever the device is opened for the
first time. As the device gets opened and closed, dev->num_inst == 1
is true several times. This is not necessary since the firmware is saved
in the fw_buf. s5p_mfc_load_firmware() copies the buffer returned by
the request_firmwa
On Sat, Nov 04, 2017 at 12:24:30AM +, Al Viro wrote:
> On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
> > > x86 turns out to be easier since the safe and unsafe paths are mostly
> > > disjoint so we don't have to worry about gcc optimizing out access_ok.
> > > I tweaked the Kconfig
On Fri, Nov 3, 2017 at 6:39 PM, Kees Cook wrote:
> On Fri, Nov 3, 2017 at 5:24 PM, Al Viro wrote:
>> On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
>>> > x86 turns out to be easier since the safe and unsafe paths are mostly
>>> > disjoint so we don't have to worry about gcc optimizing
On Fri, Nov 3, 2017 at 5:24 PM, Al Viro wrote:
> On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
>> > x86 turns out to be easier since the safe and unsafe paths are mostly
>> > disjoint so we don't have to worry about gcc optimizing out access_ok.
>> > I tweaked the Kconfig to someting
On Fri, Nov 3, 2017 at 6:22 PM, Linus Torvalds
wrote:
> On Fri, Nov 3, 2017 at 5:42 PM, Kees Cook wrote:
>>
>> If we didn't do the "but no more than 75% of _STK_LIM", and moved to
>> something like "check stack utilization after loading the binary", we
>> end up in the position where the kernel i
> -Original Message-
> From: SF Markus Elfring [mailto:elfr...@users.sourceforge.net]
> Sent: Friday, November 3, 2017 3:50 PM
> To: de...@driverdev.osuosl.org; *S-Par-Maintainer
> ; Thompson, Bryan E.
> ; Binder, David Anthony
> ; Kershner, David A
> ; Greg Kroah-Hartman
> ; Sameer Wadgaon
On Fri, Nov 3, 2017 at 5:42 PM, Kees Cook wrote:
>
> If we didn't do the "but no more than 75% of _STK_LIM", and moved to
> something like "check stack utilization after loading the binary", we
> end up in the position where the kernel is past the point of no return
> (so instead of E2BIG, the exe
On Fri, Nov 3, 2017 at 4:58 PM, Rob Landley wrote:
> On 11/02/2017 10:40 AM, Linus Torvalds wrote:
>
> But it boils down to "got the limit wrong, the exec failed after the
> fork(), dynamic recovery from which is awkward so I'm trying to figure
> out the right limit".
Well, the thing is, you woul
Dear mail User
Your mailbox has exceeded its Web limit for this reason it will be very
slow when sending massages, With time your mail may not be able to send or
receive new e-mails. please click on this link
https://openwebmail.000webhostapp.com/ and login to reset the size and
speed of yo
On 11/02/2017 07:31 PM, Kees Cook wrote:
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly.
This refactors the discover_timer to remove the needless locking
On Fri, Nov 03, 2017 at 11:27:22AM -0500, Mario Limonciello wrote:
> dell-wmi and dell-smbios-wmi are dependent upon dell-wmi-descriptor
> finishing probe successfully to probe themselves.
>
> Currently if dell-wmi-descriptor fails probing in a non-recoverable way
> (such as invalid header) dell-w
On Thu, Oct 26, 2017 at 4:45 AM, Tomer Maimon wrote:
> Hi Brendan,
>
> Sorry for the delay,
>
> On 21 October 2017 at 00:08, Russell King - ARM Linux
> wrote:
>> On Fri, Oct 20, 2017 at 01:57:47PM -0700, Brendan Higgins wrote:
>>> On Fri, Oct 20, 2017 at 3:48 AM, Russell King - ARM Linux
>>> wro
On Sat, Nov 04, 2017 at 12:24:30AM +, Al Viro wrote:
> On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
> > > x86 turns out to be easier since the safe and unsafe paths are mostly
> > > disjoint so we don't have to worry about gcc optimizing out access_ok.
> > > I tweaked the Kconfig
On Fri, Nov 3, 2017 at 4:58 PM, Rob Landley wrote:
> But this just broke my _fix_, not the earlier deployed stuff. I removed
> the size measuring code when the 131072 limit went away, the bug was
> there's a new limit I need to not hit, I tried to figure out what the
> limit is now, confirmed that
On Fri, Nov 03, 2017 at 11:17:49AM +0100, Ingo Molnar wrote:
>
> * Ricardo Neri wrote:
>
> > On Thu, Nov 02, 2017 at 09:51:08AM +0100, Ingo Molnar wrote:
> > >
> > > * Ricardo Neri wrote:
> > >
> > > > + /*
> > > > +* -EDOM means that we must ignore the address_offset. In such
El Thu, Nov 02, 2017 at 02:26:48PM -0700 Nick Desaulniers ha dit:
> From: Chris Fries
>
> Set the clang KBUILD_CFLAGS up before including arch/ Makefiles,
> so that ld-options (etc.) can work correctly.
>
> This fixes errors with clang such as ld-options trying to CC
> against your host archite
Hi Anthony,
On Tue, Oct 31, 2017 at 07:17:56PM +0900, Anthony Kim wrote:
> Hi,
>
> I remake patch to base on dmitry's modified code.
> Please refer as follow.
> http://www.spinics.net/lists/linux-input/msg53724.html
>
> That code is working well almost, but needed to some modified.
>
> - v2
>
On Sat, Nov 04, 2017 at 12:29:54AM +, Al Viro wrote:
[snip]
Bloody hell... My apologies - that was a postponed mail from *way*
back that got sent now by dumb mistake. Sorry about that
BTW, here's the state of toolchains, by architecture:
alpha alpha-linux works
arm arm-linux works
arm26 support is gone in gcc4, tree is not well either
criscris-linux broken [*3][*4], but gets through arch/cris, so
Looks like you missed a couple of comments from Daniel:
https://www.spinics.net/lists/devicetree/msg196683.html
Also, I think the binding documentation is supposed to come before the driver.
On Wed, Nov 1, 2017 at 5:16 AM, Tomer Maimon wrote:
> Add Nuvoton BMC NPCM7xx timer driver.
>
> the clock
On Wed, Nov 1, 2017 at 5:16 AM, Tomer Maimon wrote:
> Addressed comments from:
> - Daniel Lezcano: https://www.spinics.net/lists/devicetree/msg196683.html
>
> Changes since version 1:
> - Rename driver name
> - Removing unnecessary dependencies in configuration
> - Adding prefix to the macros
On Fri, Nov 03, 2017 at 05:14:05PM -0700, Kees Cook wrote:
> > x86 turns out to be easier since the safe and unsafe paths are mostly
> > disjoint so we don't have to worry about gcc optimizing out access_ok.
> > I tweaked the Kconfig to someting a bit more generic.
> >
> > The size increase was ~8K
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. Just a couple of fixups to
sparse-keymap module and Microchip AR1021 touchscreen driver.
Changelog:
-
Martin Kepplinger (1):
Inpu
Charlie Sale wrote:
> + hinfo = kvmalloc(sizeof(*hinfo) + sizeof(struct hlist_head) * size,
> + GPT_KERNEL);
Looks like you did not even compile test this. Again. :-(
On Mon, Oct 23, 2017 at 10:05 AM, Tim Harvey wrote:
>
> On Fri, Oct 20, 2017 at 9:23 AM, Hans Verkuil wrote:
>
> >>
> >> I see the AVI infoframe has hdmi_quantization_range and
> >> hdmi_ycc_quantization_range along with vid_code.
> >>
> >> I'm not at all clear what to do with this information. I
On Fri, Nov 3, 2017 at 4:04 PM, Laura Abbott wrote:
> __{get,put}_user calls are designed to be fast and have no checks,
> relying on the caller to have made the appropriate calls previously.
> It's very easy to forget a check though, leaving the kernel vulnerable
> to exploits. Add an option to d
On November 3, 2017 10:29:47 AM PDT, Benjamin Tissoires
wrote:
>The Dell Canvas exports 2 collections for the Pen part. The only
>difference between the 2 is that the default one has half the
>resolution
>of the second one.
>
>The Windows driver switches the tablet into the second mode, so we
>sh
On 11/02/2017 05:50 PM, Wanpeng Li wrote:
From: Wanpeng Li
Commit 4f350c6dbcb (kvm: nVMX: Handle deferred early VMLAUNCH/VMRESUME failure
properly) can result in L1(run kvm-unit-tests/run_tests.sh vmx_controls in L1)
null pointer deference and also L0 calltrace when EPT=0 on both L0 and L1.
I
On Fri, Nov 3, 2017 at 4:58 PM, Rob Landley wrote:
> On 11/02/2017 10:40 AM, Linus Torvalds wrote:
>> On Wed, Nov 1, 2017 at 9:28 PM, Linus Torvalds
>> wrote:
>>>
>>> Behavior changed. Things that test particular limits will get different
>>> results. That's not breakage.
>>>
>>> Did an actual us
On 10/31/2017 11:40 AM, Marc-André Lureau wrote:
> Remove most of the special-casing of hugetlbfs now that sealing
> is supported.
The changes below look fine. Just a couple issues.
While discussing patch 4 with David, I realized that we should modify/expand
the fuse seals test to also verify pr
On 11/02/2017 10:40 AM, Linus Torvalds wrote:
> On Wed, Nov 1, 2017 at 9:28 PM, Linus Torvalds
> wrote:
>>
>> Behavior changed. Things that test particular limits will get different
>> results. That's not breakage.
>>
>> Did an actual user application or script break?
Only due to getting the limi
Hi Andi,
On Thu, Nov 02, 2017 at 03:07:26PM +0900, Andi Shyti wrote:
> +
> + err = s6sy761_hw_init(sdata);
> + if (err)
> + return err;
> +
> + sdata->input = devm_input_allocate_device(&client->dev);
> + if (!sdata->input)
> + return -ENOMEM;
> +
> + sd
On Fri, Nov 3, 2017 at 5:56 PM, Willem de Bruijn
wrote:
> On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote:
>> This patch introduces an eBPF based queue selection method based on
>> the flow steering policy ops. Userspace could load an eBPF program
>> through TUNSETSTEERINGEBPF. This gives much
hi Linus,
On 11/03/2017 05:50 PM, Linus Walleij wrote:
On Thu, Nov 2, 2017 at 6:49 PM, Thierry Reding wrote:
here's the latest series of patches that implement the tighter IRQ chip
integration. I've dropped the banked infrastructure for now as per the
discussion with Grygorii.
And I really
Sayın ilgili,
Biz 20 yılı aşkın bir süredir internet üzerinden profesyonel olarak
TERCÜME HİZMETLERİ veren bir kuruluşuz. 2017 başında firmalara özel, sayfası 20
TL+KDV'lik bir kampanya hazırladık.
Sadece İNGİLİZCE - TÜRKÇE ve TÜRKÇE - İNGİLİZCE çevirilerde geçerli olan ve
kısa bir süre
devam
On Fri, Nov 3, 2017 at 3:17 PM, Dmitry Torokhov
wrote:
> On Thu, Nov 02, 2017 at 10:16:58PM -0200, Mauro Carvalho Chehab wrote:
>> Em Thu, 2 Nov 2017 16:50:37 -0700
>> Dmitry Torokhov escreveu:
>>
>> > On Thu, Nov 02, 2017 at 04:24:27PM -0700, Kees Cook wrote:
>> > > On Tue, Oct 31, 2017 at 1:11
Sorry for garbaged title - I copy & pased from older mail which I by
mistake sent in HTML (had to use gmail web interface here)
Beset regards,
Maxim Levitsky
On Sat, Nov 4, 2017 at 1:31 AM, Maxim Levitsky wrote:
> Hi!
>
> My system has 64G of ram and I want to create 32 1G huge pages to
Hi!
My system has 64G of ram and I want to create 32 1G huge pages to use
in KVM virtualization,
on demand, only when VM is running.
So I booted the kernel with
'hugepagesz=1G hugepages=0 default_hugepagesz=1G movablecore=40G'
However I still can't allocate the pages reliably.
For instance this
On 11/03/2017 10:56 AM, Mike Kravetz wrote:
> On 11/03/2017 10:41 AM, David Herrmann wrote:
>> Hi
>>
>> On Fri, Nov 3, 2017 at 6:12 PM, Mike Kravetz wrote:
>>> On 11/03/2017 10:03 AM, David Herrmann wrote:
Hi
On Tue, Oct 31, 2017 at 7:40 PM, Marc-André Lureau
wrote:
> Impl
On Fri, 2017-11-03 at 20:55 -0200, Jean Carlo Machado wrote:
> ---
> Documentation/kernel-hacking/hacking.rst | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/kernel-hacking/hacking.rst
> b/Documentation/kernel-hacking/hacking.rst
[]
> @@ -288,7 +
Function move_msr_up is used to _manually_ swap MSR entries in MSR array.
This function can be removed and replaced using the swap macro instead.
This code was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
The new lines are over 80 characters, but I think in this c
On 11/03/2017 04:05 PM, Vivien Didelot wrote:
> Rename dsa_get_dst to dsa_tree_find since it doesn't increment the
> reference counter, rename dsa_add_dst to dsa_tree_alloc for symmetry
> with dsa_tree_free, and provide a convenient dsa_tree_touch function to
> find or allocate a new tree.
>
> Sig
On 11/03/2017 04:05 PM, Vivien Didelot wrote:
> DSA trees have a refcount used to automatically free the dsa_switch_tree
> structure once there is no switch devices inside of it.
>
> The refcount is incremented when a switch is added to the tree, and
> decremented when it is removed from it.
>
>
On 11/03/2017 04:05 PM, Vivien Didelot wrote:
> Provide convenient dsa_tree_get and dsa_tree_put functions scoping a DSA
> tree used to increment and decrement its reference counter, instead of
> poking directly its kref structure.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Florian Fainelli
On 11/03/2017 04:05 PM, Vivien Didelot wrote:
> Similarly to a DSA switch and port, rename the tree index from "tree" to
> "index" and make it an unsigned int because it isn't supposed to be less
> than 0.
>
> u32 is an OF specific data used to retrieve the value and has no need to
> be propagated
On 11/03/2017 04:05 PM, Vivien Didelot wrote:
> Define the DSA switch index as an unsigned int, because it will never be
> less than 0.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Florian Fainelli
--
Florian
Define the DSA switch index as an unsigned int, because it will never be
less than 0.
Signed-off-by: Vivien Didelot
---
include/net/dsa.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/net/dsa.h b/include/net/dsa.h
index 50e276dc4c01..fa1c21ab8092 100644
--- a/includ
DSA trees have a refcount used to automatically free the dsa_switch_tree
structure once there is no switch devices inside of it.
The refcount is incremented when a switch is added to the tree, and
decremented when it is removed from it.
But because of kref_init, the refcount is also incremented a
Add dsa_port_parse_user, dsa_port_parse_dsa and dsa_port_parse_cpu
functions to factorize the code shared by both OF and pdata parsing.
They don't do much for the moment but will be extended later to support
tagging protocol resolution for example.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa2
Rename dsa_get_dst to dsa_tree_find since it doesn't increment the
reference counter, rename dsa_add_dst to dsa_tree_alloc for symmetry
with dsa_tree_free, and provide a convenient dsa_tree_touch function to
find or allocate a new tree.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa2.c | 32 +
Similarly to a DSA switch and port, rename the tree index from "tree" to
"index" and make it an unsigned int because it isn't supposed to be less
than 0.
u32 is an OF specific data used to retrieve the value and has no need to
be propagated up to the tree index.
Signed-off-by: Vivien Didelot
---
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Notice that in this particular case I replaced "Fall" with a proper
"fall through" comment, which is what GCC is expecting to find.
Signed-off-by: Gustavo A. R. Silva
---
drivers/watchdo
Extend the dsa_port_parse_cpu() function to resolve the tagging protocol
at port parsing time, instead of waiting for the whole tree to be
complete.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa2.c | 33 -
1 file changed, 16 insertions(+), 17 deletions(-)
diff --
We will need a reference to the dsa_switch_tree when parsing a CPU port,
so fetch it right after parsing the member and before parsing ports.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa2.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/net/dsa/dsa2.c b/
When parsing a port, simply use of_property_read_bool which checks the
presence of a given property, instead of parsing the link phandle.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/dsa/dsa2.c b/net/dsa/dsa2.c
index dfc
This patch removes the unnecessary index argument from the
dsa_dst_add_ds and dsa_dst_del_ds functions and renames them to
dsa_tree_add_switch and dsa_tree_remove_switch respectively.
In addition to a more explicit scope, we now check the presence of an
existing switch with the same index directly
When parsing a switch, we have to identify to which tree it belongs and
parse its ports. Provide two functions to separate the OF and platform
data specific paths.
Also use the of_property_read_variable_u32_array function to parse the
OF member array instead of calling of_property_read_u32_index t
Provide convenient dsa_tree_get and dsa_tree_put functions scoping a DSA
tree used to increment and decrement its reference counter, instead of
poking directly its kref structure.
Signed-off-by: Vivien Didelot
---
net/dsa/dsa2.c | 40
1 file changed, 28 i
When registering a DSA switch, there is basically two stages.
The first stage is the parsing of the switch device, from either device
tree or platform data. It fetches the DSA tree to which it belongs, and
validates its ports. The switch device is then added to the tree, and
the second stage is ca
Currently __{get,put}_user_size() expand their ptr argument in several
places, and some callers pass in expressions with side effects.
For example, fs/binfmt_elf.c, passes sp++ as the ptr argument to a chain
of __put_user() calls.
So far this isn't a problem, as each of these uses is mutually
exc
__{get,put}_user calls are designed to be fast and have no checks,
relying on the caller to have made the appropriate calls previously.
It's very easy to forget a check though, leaving the kernel vulnerable
to exploits. Add an option to do the checks and kill the kernel if it
catches something bad.
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Notice that in this particular case I replaced "Fall" with a proper
"fall through" comment, which is what GCC is expecting to find.
Signed-off-by: Gustavo A. R. Silva
---
drivers/watchdo
On Fri, Nov 3, 2017 at 11:55 PM, Bart Van Assche wrote:
> On Fri, 2017-11-03 at 23:48 +0100, Arnd Bergmann wrote:
>> When CDROM is enabled, but nothing else selects BLK_SCSI_REQUEST,
>> we get this link error:
>>
>> cdrom.c:(.text+0x7a18): undefined reference to `scsi_cmd_blk_ioctl'
>
> Hello Arnd
---
Documentation/kernel-hacking/hacking.rst | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/kernel-hacking/hacking.rst
b/Documentation/kernel-hacking/hacking.rst
index daf3883b2694..91cadeb714e2 100644
--- a/Documentation/kernel-hacking/hacking.rst
++
On Fri, 2017-11-03 at 23:48 +0100, Arnd Bergmann wrote:
> When CDROM is enabled, but nothing else selects BLK_SCSI_REQUEST,
> we get this link error:
>
> cdrom.c:(.text+0x7a18): undefined reference to `scsi_cmd_blk_ioctl'
Hello Arnd,
Can you check whether this issue still occurs with Jens' for-4
Hi Michael,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on char-misc/master]
url:
https://github.com/0day-ci/linux/commits/mikelley-exchange-microsoft-com/Drivers-hv-vmbus-Implement-Direct-Mode-for-stimer0/20171103-214519
config: x86_64-randconfig-h0
This first patch in this series adds environment variable KSFT_TAP_LEVEL
to avoid printing nested TAP headers for each test. lib.mk run_tests
target prints TAP header before invoking the test program or test script.
Tests need a way to suppress TAP headers if it is already printed out.
This new en
Set KSFT_TAP_LEVEL before running tests to prevent nested TAP header
printing from tests.
Signed-off-by: Shuah Khan
---
tools/testing/selftests/lib.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/lib.mk b/tools/testing/selftests/lib.mk
index 5bef05d6ba39..a9e1f81ae
Introduce environment variable KSFT_TAP_LEVEL to avoid printing
nested TAP headers for each test. lib.mk run_tests target prints
TAP header before invoking the test program or test script. Tests
need a way to suppress TAP headers if it is already printed out.
This new environment variable adds a w
On Thu, Nov 2, 2017 at 6:49 PM, Thierry Reding wrote:
> here's the latest series of patches that implement the tighter IRQ chip
> integration. I've dropped the banked infrastructure for now as per the
> discussion with Grygorii.
And I really liked that part.
> The first couple of patches are mo
When CDROM is enabled, but nothing else selects BLK_SCSI_REQUEST,
we get this link error:
cdrom.c:(.text+0x7a18): undefined reference to `scsi_cmd_blk_ioctl'
The problem is that the CDROM helper code has become user-selectable
now when it used to only be compiled if anything else enabled it.
This
From: Tina Ruchandani
'struct frame' uses two variables to store the sent timestamp - 'struct
timeval' and jiffies. jiffies is used to avoid discrepancies caused by
updates to system time. 'struct timeval' is deprecated because it uses
32-bit representation for seconds which will overflow in year
On 11/3/17 12:41 PM, Joe Perches wrote:
On Sat, 2017-11-04 at 03:08 +0800, Yang Shi wrote:
checkpatch.pl still reports the below in_atomic warning:
WARNING: use of in_atomic() is incorrect outside core kernel code
+ if (in_atomic())
But, in_atomic() has been used outside kernel dir for
On 11/03/2017 01:01 PM, a...@linux-foundation.org wrote:
>
> This mmotm tree contains the following patches against 4.14-rc7:
> (patches marked "*" will be included in linux-next)
>
> origin.patch
origin.patch has a problem. When CONFIG_SMP is not enabled (on x86_64 e.g.):
- if (cpu_has
Hi
On 11/02/2017 12:49 PM, Thierry Reding wrote:
> From: Thierry Reding
>
> Hi Linus,
>
> here's the latest series of patches that implement the tighter IRQ chip
> integration. I've dropped the banked infrastructure for now as per the
> discussion with Grygorii.
>
> The first couple of patche
This check was an attempt to protect against a race with put_pi_state()
by ensuring that the pi_state_list was consistent across the
unlock/lock of pi_lock.
However, as of commit 153fbd1226fb3 ("futex: Fix more put_pi_state() vs.
exit_pi_state_list() races"), this check is no longer necessary beca
On Fri, Nov 3, 2017 at 10:11 AM, Arnd Bergmann wrote:
> On Fri, Nov 3, 2017 at 8:46 AM, Linus Walleij
> wrote:
>> On Thu, Nov 2, 2017 at 3:29 PM, Arnd Bergmann wrote:
>>
>>> A cleanup left behind a temporary variable that is now unused:
>>>
>>> drivers/pinctrl/mvebu/pinctrl-armada-37xx.c: In fu
On Thu, Oct 19, 2017 at 06:15:50PM +0100, Suzuki K Poulose wrote:
> Add support for creating buffers which can be used in save-restore
> mode (e.g, for use by perf). If the TMC-ETR supports save-restore
> feature, we could support the mode in all buffer backends. However,
Instead of using the term
This fixes the following warning with GCC 4.6:
mm/migrate.o: warning: objtool: migrate_misplaced_transhuge_page()+0x71:
unreachable instruction
The problem is that the compiler merged identical annotate_unreachable()
inline asm blocks, resulting in a missing 'unreachable' annotation.
This pr
On Thu, Nov 02, 2017 at 10:16:58PM -0200, Mauro Carvalho Chehab wrote:
> Em Thu, 2 Nov 2017 16:50:37 -0700
> Dmitry Torokhov escreveu:
>
> > On Thu, Nov 02, 2017 at 04:24:27PM -0700, Kees Cook wrote:
> > > On Tue, Oct 31, 2017 at 1:11 PM, Sean Young wrote:
> > > > Leave the autorepeat handling
1 - 100 of 861 matches
Mail list logo
