On Mon, Mar 27, 2017 at 06:06:05PM +0100, Joao Pinto wrote:
> Às 6:00 PM de 3/27/2017, Corentin Labbe escreveu:
> > On Mon, Mar 27, 2017 at 04:26:48PM +0100, Joao Pinto wrote:
> >> Hi David,
> >>
> >> Às 7:26 AM de 3/25/2017, Corentin Labbe escreveu:
> >>> On Fri, Mar 24, 2017 at 05:16:45PM +,
From: Mahesh Bandewar
bond_miimon_commit() marks the link UP after attempting to get the speed
and duplex settings for the link. There is a possibility that
bond_update_speed_duplex() could fail. This is another place where it
could result into an inconsistent bonding link
From: Mahesh Bandewar
Signed-off-by: Mahesh Bandewar
---
drivers/net/bonding/bond_3ad.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/bonding/bond_3ad.c b/drivers/net/bonding/bond_3ad.c
index
From: Mahesh Bandewar
The primary issue is that mii-inspect phase updates link-state and
expects changes to be committed during the mii-commit phase. After
the inspect phase if it fails to acquire rtnl-mutex, the commit
phase (bond_mii_commit) doesn't get to run. This
From: Mahesh Bandewar
Split the function into two (a) propose (b) commit phase without
changing the semantics for the original API.
Signed-off-by: Mahesh Bandewar
---
include/net/bonding.h | 22 +-
1 file changed, 17 insertions(+), 5
From: Mahesh Bandewar
The mii monitoring is divided into two phases - inspect and commit. The
inspect phase technically should not make any changes to the state and
defer it to the commit phase. However detected link state inconsistencies
on several machines and discovered
From: Mahesh Bandewar
bond_update_speed_duplex() retrieves speed and duplex settings. There
is a possibility of failure in retrieving these values but caller has
to assume it's always successful. This leads to having inconsistent
slave link settings. If these (speed, duplex)
On Mon, Mar 27, 2017 at 09:25:03AM -0700, Denny Page wrote:
> I agree that the values in the igb driver are incorrect. They were
> middle of the range values from the old tables. At least for 100Mb,
> Intel seems to know that the original table was incorrect. I’ve done
> extensive measurements of
[RFC until kernel code is accepted/rejected]
This patch adds support to the iproute2 tc filter command for matching MPLS
labels in the flower classifier. The ability to match the Time To Live,
Bottom Of Stack, Traffic Control and Label fields are added as options to
the flower filter.
Add support to tc flower to match based on fields in MPLS labels (TTL,
Bottom of Stack, TC field, Label).
Signed-off-by: Benjamin LaHaise
Signed-off-by: Benjamin LaHaise
Reviewed-by: Simon Horman
Reviewed-by: Jakub
On Sat, Mar 25, 2017 at 02:50:47PM -0700, Jakub Kicinski wrote:
> On Wed, 8 Mar 2017 16:03:51 +0200, Gal Pressman wrote:
> > This ethtool patch adds support to set and get the current RSS hash
> > function for the device through the new hfunc mask field in the
> > ethtool_rxfh struct. Kernel
Add support for parsing MPLS flows to the flow dissector in preparation for
adding MPLS match support to cls_flower.
Signed-off-by: Benjamin LaHaise
Signed-off-by: Benjamin LaHaise
Reviewed-by: Simon Horman
On 03/27/2017 02:58 AM, Russell King wrote:
> We currently allow userspace to set any EEE advertisments it desires,
> whether or not the PHY supports them. For example:
>
> # ethtool --set-eee eth1 advertise 0x
> # ethtool --show-eee eth1
> EEE Settings for eth1:
> EEE status:
On 03/27/2017 10:00 AM, Russell King - ARM Linux wrote:
> On Mon, Mar 27, 2017 at 09:47:31AM -0700, Florian Fainelli wrote:
>> On 03/27/2017 02:59 AM, Russell King wrote:
>>> As EEE is able to work in SGMII mode as well, add it to the list of
>>> permissable EEE modes that phy_init_eee() will
On 03/27/2017 02:58 AM, Russell King wrote:
> When the EEE advertisment is changed, we should restart autonegotiation
> to update the link partner with the new EEE settings. Add this trigger
> but only if the advertisment has changed.
>
> Signed-off-by: Russell King
Andrew has been contributing a lot to PHYLIB over the past months and
his feedback on patches is more than welcome.
Signed-off-by: Florian Fainelli
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
Às 6:28 PM de 3/27/2017, David Miller escreveu:
> From: Corentin Labbe
> Date: Mon, 27 Mar 2017 19:00:58 +0200
>
>> On Mon, Mar 27, 2017 at 04:26:48PM +0100, Joao Pinto wrote:
>>> Hi David,
>>>
>>> Às 7:26 AM de 3/25/2017, Corentin Labbe escreveu:
On Fri, Mar 24,
On Mon, Mar 27, 2017 at 09:44:37AM -0700, Florian Fainelli wrote:
> Hello,
>
> On 03/27/2017 03:12 AM, Thomas Scariah wrote:
> > From: "Scariah, Thomas"
> >
> > Added functions to support ethtool to print the phy statistics and error
> > information along with other
On 03/27/2017 10:11 AM, Christoph Hellwig wrote:
On Mon, Mar 27, 2017 at 09:59:35AM -0700, David Daney wrote:
On 03/27/2017 01:29 AM, Christoph Hellwig wrote:
Unused now that all callers switched to pci_alloc_irq_vectors.
And you are aware that the ThunderX GPIO driver that I am attempting
From: Corentin Labbe
Date: Mon, 27 Mar 2017 19:00:58 +0200
> On Mon, Mar 27, 2017 at 04:26:48PM +0100, Joao Pinto wrote:
>> Hi David,
>>
>> Às 7:26 AM de 3/25/2017, Corentin Labbe escreveu:
>> > On Fri, Mar 24, 2017 at 05:16:45PM +, Joao Pinto wrote:
>> >> For
> > static int cpsw_get_sset_count(struct net_device *ndev, int sset)
> > {
> > + struct cpsw_priv *priv = netdev_priv(ndev);
> > + int slave_no = cpsw_slave_index(priv);
> > + int count;
> > +
> > switch (sset) {
> > case ETH_SS_STATS:
> > - return CPSW_STATS_LEN;
> > +
On Mon, Mar 27, 2017 at 09:33:32PM +0530, Sunil Kovvuri wrote:
> How urgent is this ?
I would like to get this into 4.12 to stop people from adding new users of
pci_enable_msix.
> Can we comeup with a proper patch to fix this in couple of weeks, instead of
> going with these untested patches ?
On Mon, Mar 27, 2017 at 03:03:30PM +, David Laight wrote:
> Indeed, but pci_enable_msix_range() only appeared in 3.14.
> We have to support a wide range of kernels.
> I think we've finally managed to get most of our customers off 2.6.18.
That's your problem, not that of upstream kernel
On Mon, Mar 27, 2017 at 09:59:35AM -0700, David Daney wrote:
> On 03/27/2017 01:29 AM, Christoph Hellwig wrote:
>> Unused now that all callers switched to pci_alloc_irq_vectors.
>>
>
> And you are aware that the ThunderX GPIO driver that I am attempting to
> merge uses this interface.
>
> If this
Às 6:00 PM de 3/27/2017, Corentin Labbe escreveu:
> On Mon, Mar 27, 2017 at 04:26:48PM +0100, Joao Pinto wrote:
>> Hi David,
>>
>> Às 7:26 AM de 3/25/2017, Corentin Labbe escreveu:
>>> On Fri, Mar 24, 2017 at 05:16:45PM +, Joao Pinto wrote:
For cores that have more than 1 TX queue
On Mon, Mar 27, 2017 at 04:26:48PM +0100, Joao Pinto wrote:
> Hi David,
>
> Às 7:26 AM de 3/25/2017, Corentin Labbe escreveu:
> > On Fri, Mar 24, 2017 at 05:16:45PM +, Joao Pinto wrote:
> >> For cores that have more than 1 TX queue configured, the kernel would
> >> crash,
> >> since only one
Our chosen ic_dev may be anywhere in our list of ic_devs, and we may
free it before attempting to close others. When we compare d->dev and
ic_dev->dev, we're potentially dereferencing memory returned to the
allocator. This causes KASAN to scream for each subsequent ic_dev we
check.
As there's a
On Mon, Mar 27, 2017 at 09:47:31AM -0700, Florian Fainelli wrote:
> On 03/27/2017 02:59 AM, Russell King wrote:
> > As EEE is able to work in SGMII mode as well, add it to the list of
> > permissable EEE modes that phy_init_eee() will accept. This is
> > necessary so that EEE can work with an
On 03/27/2017 01:29 AM, Christoph Hellwig wrote:
Unused now that all callers switched to pci_alloc_irq_vectors.
And you are aware that the ThunderX GPIO driver that I am attempting to
merge uses this interface.
If this patch gets merged, should I ask to revert it when the GPIO
driver goes
On Mon, Mar 27, 2017 at 05:15:00PM +0200, Jesper Dangaard Brouer wrote:
> And I also verified it worked:
>
> 0.63 │ mov__preempt_count,%eax
>│ free_hot_cold_page():
> 1.25 │ test $0x1f,%eax
>│ ↓ jne1e4
>
> And this simplification also made
On 03/27/2017 02:59 AM, Russell King wrote:
> As EEE is able to work in SGMII mode as well, add it to the list of
> permissable EEE modes that phy_init_eee() will accept. This is
> necessary so that EEE can work with an 88E1512 connected in SGMII mode.
As you mention in your cover letter, we
Hello,
On 03/27/2017 03:12 AM, Thomas Scariah wrote:
> From: "Scariah, Thomas"
>
> Added functions to support ethtool to print the phy statistics and error
> information along with other ethtool statistics. This will help ethtool
> information to know the error is
> On Mar 27, 2017, at 07:29, Richard Cochran wrote:
>
> At the end of the day, the correction in the igb driver is useless and
> even harmful. Why? Because if the app cares about this level of
> accuracy, it is going to have to implement special logic anyhow, and
>
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Saturday, March 25, 2017 8:01 PM
> To: Kirsher, Jeffrey T
> Cc: Wyborny, Carolyn ;
> netdev@vger.kernel.org; nhor...@redhat.com; sassm...@redhat.com;
>
On Mon, Mar 27, 2017 at 1:59 PM, Christoph Hellwig wrote:
> Remove the deprecated pci_enable_msix API in favour of it's successor.
>
> Signed-off-by: Christoph Hellwig
> ---
> drivers/net/ethernet/cavium/thunder/nic_main.c | 75
> ++
> 1 file
On Monday, March 13, 2017 10:05:09 PM CEST Alban wrote:
> The current binding only cover PCI devices so extend it for SoC devices.
>
> Most SoC platforms use an MTD partition for the calibration data
> instead of an EEPROM. The qca,no-eeprom property was added to allow
> loading the EEPROM
On Mon, Mar 27, 2017 at 10:16 PM, Marcelo Ricardo Leitner
wrote:
> On Mon, Mar 27, 2017 at 12:48:31PM +0800, Xin Long wrote:
>> On Sat, Mar 25, 2017 at 7:52 AM, Marcelo Ricardo Leitner
>> wrote:
>> > On Tue, Mar 21, 2017 at 01:44:32PM +0800,
On Mon, 2017-03-27 at 15:37 +0200, Stefan Wahren wrote:
> In order to share common functions between QCA7000 SPI and UART
> protocol
> driver the qca_common needs to be a separate kernel module.
Maybe "qca_eth_common"? There are many things Qualcomm, slightly fewer
things Qualcomm Atheros, and
On Thu, Mar 23, 2017 at 6:01 PM, Florian Fainelli wrote:
> Introduce a new configuration symbol: MDIO_DEVICE which allows building
> the MDIO devices and bus code, without pulling in the entire Ethernet
> PHY library and devices code.
>
> PHYLIB nows select MDIO_DEVICE and
Hi David,
Às 7:26 AM de 3/25/2017, Corentin Labbe escreveu:
> On Fri, Mar 24, 2017 at 05:16:45PM +, Joao Pinto wrote:
>> For cores that have more than 1 TX queue configured, the kernel would crash,
>> since only one TX queue is permitted by default.
>>
>> Signed-off-by: Joao Pinto
On Mon, 27 Mar 2017 07:15:18 -0700
Matthew Wilcox wrote:
> On Mon, Mar 27, 2017 at 02:39:47PM +0200, Jesper Dangaard Brouer wrote:
> >
> > +static __always_inline int in_irq_or_nmi(void)
> > +{
> > + return in_irq() || in_nmi();
> > +// XXX: hoping compiler will optimize
From: Pablo Neira Ayuso
> Sent: 27 March 2017 13:08
> On Sat, Mar 25, 2017 at 06:19:47PM +0530, Arushi Singhal wrote:
> > This patch removes multiple assignments.
> > Done using coccinelle.
> > @@
> > identifier i1,i2;
> > constant c;
> > @@
> > - i1=i2=c;
> > + i1=c;
> > + i2=c;
>
> You have to
From: 'Christoph Hellwig'
> Sent: 27 March 2017 15:52
> On Mon, Mar 27, 2017 at 02:06:45PM +, David Laight wrote:
> > Apart from all the 'out of tree' drivers that will need
> > fixing and a conditional compile added.
>
> That has never been a reason for stopping linux kernel changes.
I'm
On Mon, Mar 27, 2017 at 02:06:45PM +, David Laight wrote:
> Apart from all the 'out of tree' drivers that will need
> fixing and a conditional compile added.
That has never been a reason for stopping linux kernel changes.
Never mind that your out of tree drivers should probably never have
On 3/26/17 9:11 PM, Eric W. Biederman wrote:
> I don't like this. Byte writes don't exist on all architectures.
>
> So while I think always writing to rtn_nhn_alive under the
> rtn_lock ensures that we don't have wrong values written
> it is quite subtle. And I don't know how this will interact
On Mon, Mar 27, 2017 at 12:13:24PM +0200, Miroslav Lichvar wrote:
> On Fri, Mar 24, 2017 at 10:17:51AM -0700, Denny Page wrote:
> > I should have remembered this yesterday... I went and looked at my favorite
> > driver, Intel's igb. Not only is the igb driver already caching link speed,
> > it
Hi Colin,
> Variable err is being initialized to zero and then later being
> set to the error return from the call to hci_req_run_skb; hence
> we can remove the redundant initialization to zero.
>
> Also on two occassions err is not being set from the error return
> from the call to
On 3/27/17 4:39 AM, Robert Shearman wrote:
> On 25/03/17 19:15, Eric W. Biederman wrote:
>> David Ahern writes:
>>
>>> Bump the maximum number of labels for MPLS routes from 2 to 12. To keep
>>> memory consumption in check the labels array is moved to the end of
>>>
On Mon, Mar 27, 2017 at 12:48:31PM +0800, Xin Long wrote:
> On Sat, Mar 25, 2017 at 7:52 AM, Marcelo Ricardo Leitner
> wrote:
> > On Tue, Mar 21, 2017 at 01:44:32PM +0800, Xin Long wrote:
> >> On Tue, Mar 21, 2017 at 2:04 AM, Marcelo Ricardo Leitner
> >>
On Mon, Mar 27, 2017 at 02:39:47PM +0200, Jesper Dangaard Brouer wrote:
>
> +static __always_inline int in_irq_or_nmi(void)
> +{
> + return in_irq() || in_nmi();
> +// XXX: hoping compiler will optimize this (todo verify) into:
> +// #define in_irq_or_nmi() (preempt_count() & (HARDIRQ_MASK
Hi Luiz,
> These patches fixes lladdr length to be 6 bytes long and not 8 which cause
> neighbor advertisement to be sent with wrong lladdr including FF:FE filler
> bytes for eui64.
>
> Note: This does not fix some of the existing crashes which I hope to address
> in a different set.
>
> v2:
Hi Elena,
> 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
From: Christoph Hellwig
> Sent: 27 March 2017 09:30
>
> Unused now that all callers switched to pci_alloc_irq_vectors.
Apart from all the 'out of tree' drivers that will need
fixing and a conditional compile added.
At least give us a couple of kernel versions to get it sorted.
David
On 3/27/17 6:42 AM, Dmitry Vyukov wrote:
> A friendly ping. This still happens all the time for us.
Haven't looked at this in a couple of weeks. I have syzkaller installed
on a machine locally and never was able to reproduce this ipv6 problem.
I am using a jessie rootfs; from the syzkaller files
Instead of returning the requested baudrate, we better return the
actual one because it isn't always the same.
Signed-off-by: Stefan Wahren
---
drivers/tty/serdev/serdev-ttyport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
There is no need to export qcaspi_netdev_open and qcaspi_netdev_close
because they are also accessible via the net_device_ops.
Signed-off-by: Stefan Wahren
---
drivers/net/ethernet/qualcomm/qca_debug.c | 5 +++--
drivers/net/ethernet/qualcomm/qca_spi.h | 3 ---
2 files
This patch adds the Ethernet over UART driver for the
Qualcomm QCA7000 HomePlug GreenPHY.
Signed-off-by: Stefan Wahren
---
drivers/net/ethernet/qualcomm/Kconfig | 10 +
drivers/net/ethernet/qualcomm/Makefile | 2 +
drivers/net/ethernet/qualcomm/qca_common.h |
The Qualcomm QCA7000 HomePlug GreenPHY supports two interfaces:
UART and SPI. This patch series adds the missing support for UART.
This driver based on the Qualcomm code [1], but contains some changes:
* use random MAC address per default
* use net_device_stats from device
* share frame decoding
Unfortunately the frame format is not exactly identical between SPI
and UART. In case of SPI there is an additional HW length at the
beginning. So store the initial state to make the decoding state machine
more flexible and easy to extend for UART support.
Signed-off-by: Stefan Wahren
This is the serdev binding for the QCA7000 UART driver (Ethernet over UART).
Signed-off-by: Stefan Wahren
---
According to this binding are still some questions:
Where should be the optional hardware flow control defined (at master or slave
side)?
Is it okay to have
As preparation for the upcoming UART driver we need a module
which contains common functions for both interfaces. The module
qca_framing is a good candidate but renaming to qca_common would
make it clear.
Signed-off-by: Stefan Wahren
---
The function qcaspi_tx_cmd() is only called from qca_spi.c. So we better
move it there.
Signed-off-by: Stefan Wahren
---
drivers/net/ethernet/qualcomm/qca_7k.c | 24
drivers/net/ethernet/qualcomm/qca_7k.h | 1 -
On Mon, Mar 27, 2017 at 02:39:47PM +0200, Jesper Dangaard Brouer wrote:
> On Mon, 27 Mar 2017 10:55:14 +0200
> Jesper Dangaard Brouer wrote:
>
> > A possible solution, would be use the local_bh_{disable,enable} instead
> > of the {preempt_disable,enable} calls. But it is
Currently serdev core doesn't provide functions to retrieve common
UART settings like data bits, stop bits or parity. This patch adds
the interface to the core and the necessary implementation for
serdev-ttyport.
Signed-off-by: Stefan Wahren
---
drivers/tty/serdev/core.c
In order to share common functions between QCA7000 SPI and UART protocol
driver the qca_common needs to be a separate kernel module.
Signed-off-by: Stefan Wahren
---
drivers/net/ethernet/qualcomm/Kconfig | 8 +++-
drivers/net/ethernet/qualcomm/Makefile | 5
Most of the includes in qca_7k.c are unnecessary so we better remove them.
Signed-off-by: Stefan Wahren
---
drivers/net/ethernet/qualcomm/qca_7k.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/net/ethernet/qualcomm/qca_7k.c
gt; u32 work_done = 0;
>>>>>>> u32 queue = 0;
>>>>>>> --
>>>>>>> 2.9.3
>>>>>>>
>>>>>>
>>>>>> This patch fix the performance issue on dwmac-sun8i only.
>>
gt;>>>
>>>>> This patch fix the performance issue on dwmac-sun8i only.
>>>>
>>>> Ok, great!
>>>>
>>>
>>> Sorry, in the we, I see that my gigabit dwmac-sun8i didnt work... (but
>>> didnt have time to find why).
>>&g
gt; --
>>>>> 2.9.3
>>>>>
>>>>
>>>> This patch fix the performance issue on dwmac-sun8i only.
>>>
>>> Ok, great!
>>>
>>
>> Sorry, in the we, I see that my gigabit dwmac-sun8i didnt work... (but didnt
>> have t
On Mon, Mar 27, 2017 at 1:37 PM, Steffen Klassert
wrote:
> On Sat, Mar 25, 2017 at 07:41:17PM +0300, Alexey Dobriyan wrote:
>> After (no branches):
>>
>> movr8d,0x20
>> movrdx,0x
>> movesi,DWORD PTR [rsi+0x2c]
>>
On Wed, Mar 8, 2017 at 12:55 PM, Dmitry Vyukov wrote:
> On Tue, Mar 7, 2017 at 9:00 PM, Dmitry Vyukov wrote:
>> On Tue, Mar 7, 2017 at 8:30 PM, Dmitry Vyukov wrote:
> On 3/7/17 11:13 AM, Dmitry Vyukov wrote:
>>> on this
On Mon, 27 Mar 2017 10:55:14 +0200
Jesper Dangaard Brouer wrote:
> A possible solution, would be use the local_bh_{disable,enable} instead
> of the {preempt_disable,enable} calls. But it is slower, using numbers
> from [1] (19 vs 11 cycles), thus the expected cycles saving is
On Tue, Mar 21, 2017 at 05:49:52PM +0530, simran singhal wrote:
> This patch series remove unnecessary cast on void pointer.
>
> simran singhal (2):
> netfilter: ipset: Remove unnecessary cast on void pointer
> netfilter: Remove unnecessary cast on void pointer
Please, merge this two patches
moxart_mac_start_xmit() doesn't care where tx_tail is, tx_head can
catch and pass tx_tail, which is bad because moxart_tx_finished()
isn't guaranteed to catch up on freeing resources from tx_tail.
Add a check in moxart_mac_start_xmit() stopping the queue at
the end of the circular buffer. Wake it
On Mon, Mar 27, 2017 at 10:55:14AM +0200, Jesper Dangaard Brouer wrote:
> On Mon, 27 Mar 2017 03:32:47 -0400 (EDT)
> Pankaj Gupta wrote:
>
> > Hello,
> >
> > It looks like a race with softirq and normal process context.
> >
> > Just thinking if we really want allocations
On Mon, Mar 27, 2017 at 05:48:41PM +0530, Arushi Singhal wrote:
> On Mon, Mar 27, 2017 at 5:38 PM, Pablo Neira Ayuso
> wrote:
>
> > On Sat, Mar 25, 2017 at 06:19:47PM +0530, Arushi Singhal wrote:
> > > This patch removes multiple assignments.
> > > Done using coccinelle.
> >
On Sat, Mar 25, 2017 at 06:19:47PM +0530, Arushi Singhal wrote:
> This patch removes multiple assignments.
> Done using coccinelle.
> @@
> identifier i1,i2;
> constant c;
> @@
> - i1=i2=c;
> + i1=c;
> + i2=c;
You have to explain why this is bad.
Hi Arushi,
On Sat, Mar 25, 2017 at 07:23:13PM +0530, Arushi Singhal wrote:
> diff --git a/net/netfilter/nf_conntrack_netlink.c
> b/net/netfilter/nf_conntrack_netlink.c
> index 6806b5e73567..aa344c5868c5 100644
> --- a/net/netfilter/nf_conntrack_netlink.c
> +++
The Ethernet link on an interrupt driven PHY was not coming up if the
Ethernet cable was plugged before the Ethernet interface was brought up.
The PHY state machine seems to be stuck from RUNNING to AN state
with no new interrupts from the PHY. So it doesn't know when the
PHY Auto-negotiation has
On 23/03/17 11:52, Sergei Shtylyov wrote:
> Hello!
>
> On 3/22/2017 2:02 PM, Roger Quadros wrote:
>
>> he ethernet link on an interrupt driven PHY was not coming up if the
>
>s/he/The/?
>
>> ethernet cable was plugged before the ethernet interface was brought up.
>
>Also, my spell
> > > - const skb_frag_t *frag = >frags[-1];
> > > + const skb_frag_t *frag = >frags[0];
[...]
> > > + frag--;
> >
> > Isn't it just a question of time until the compiler will see
> > through this trick and warn about it?
>
> Frag is incremented again before being accessed, so there is nothing
On 2017-03-27 12:47, Johannes Berg wrote:
> On Fri, 2017-03-24 at 18:06 -0700, Matthias Kaehlcke wrote:
>> __ieee80211_amsdu_copy_frag intentionally initializes a pointer to
>> array[-1] to increment it later to valid values. clang rightfully
>> generates an array-bounds warning on the
I found a bug by:
0. boot and start dhcp client
1. echo mem > /sys/power/state
2. resume back immediately
3. don't touch dhcp client to renew the lease
4. ping the gateway. No acks
Usually, after step2, the DHCP lease isn't expired, so in theory we
should resume all back. But in fact, it
On Fri, 2017-03-24 at 18:06 -0700, Matthias Kaehlcke wrote:
> __ieee80211_amsdu_copy_frag intentionally initializes a pointer to
> array[-1] to increment it later to valid values. clang rightfully
> generates an array-bounds warning on the initialization statement.
> Work around this by
On Sat, Mar 25, 2017 at 07:41:17PM +0300, Alexey Dobriyan wrote:
> Current addr4_match() code has special test for /0 prefixes because of
> standard required undefined behaviour. However, it is possible to omit
> it on 64-bit because shifting can be done within a 64-bit register and
> then
On Fri, Mar 24, 2017 at 02:07:50AM +0300, Alexey Dobriyan wrote:
> x86_64 is zero-extending arch so "unsigned int" is preferred over "int"
> for address calculations and extending to size_t.
>
> Space savings:
>
> add/remove: 0/0 grow/shrink: 0/2 up/down: 0/-24 (-24)
> function
On 25/03/17 19:15, Eric W. Biederman wrote:
David Ahern writes:
Bump the maximum number of labels for MPLS routes from 2 to 12. To keep
memory consumption in check the labels array is moved to the end of mpls_nh
and mpls_iptunnel_encap structs as a 0-sized array.
On Fri, Mar 24, 2017 at 01:29:40AM +0300, Alexey Dobriyan wrote:
> Signed-off-by: Alexey Dobriyan
> ---
>
> include/net/xfrm.h |1 -
> net/key/af_key.c |1 -
> net/xfrm/xfrm_user.c |1 -
> 3 files changed, 3 deletions(-)
Applied to ipsec-next, thanks!
On Fri, Mar 24, 2017 at 01:53:09AM +0300, Alexey Dobriyan wrote:
> x86_64 is zero-extending arch so "unsigned int" is preferred over "int"
> for address calculations.
>
> Space savings:
>
> add/remove: 0/0 grow/shrink: 0/3 up/down: 0/-58 (-58)
> function
On 24/03/17 22:21, David Ahern wrote:
When a device associated with a nexthop is deleted, the nexthop in
the route is effectively removed, so remove it from the route dump.
Further, when all nexhops have been deleted the route is effectively
done, so remove the route.
David Ahern (2):
mpls:
On 27-3-2017 11:24, Arend Van Spriel wrote:
> + Johannes
>
> On 6-3-2017 11:48, Arend Van Spriel wrote:
>> + linux-wireless
>>
>> On 6-3-2017 8:04, Daniel J Blueman wrote:
>>> When resuming from suspend with a BCM43602 on Ubuntu 16.04 with
>>> 4.9.13, we see use after free [1].
>>>
>>> We see the
From: "Scariah, Thomas"
Added functions to support ethtool to print the phy statistics and error
information along with other ethtool statistics. This will help ethtool
information to know the error is from physical layer or MAC layer.
This is an enahancement for
On Fri, Mar 24, 2017 at 10:17:51AM -0700, Denny Page wrote:
> > On Mar 24, 2017, at 02:45, Miroslav Lichvar wrote:
> > How common is to have link speed changing in normal operation on LAN?
>
> In my case, it’s currently every few minutes because I’m doing hw timestamp
>
phylib has some undesirable behaviour when forcing a link mode through
ethtool. phylib uses this code:
idx = phy_find_valid(phy_find_setting(phydev->speed, phydev->duplex),
features);
to find an index in the settings table. phy_find_setting() starts at
index 0,
We currently allow userspace to set any EEE advertisments it desires,
whether or not the PHY supports them. For example:
# ethtool --set-eee eth1 advertise 0x
# ethtool --show-eee eth1
EEE Settings for eth1:
EEE status: disabled
Tx LPI: disabled
Supported EEE
Florian,
This series of patches depends on the previous set of changes, and is
therefore net-next material.
While testing the EEE code, I discovered a number of issues:
1. It is possible to enable advertisment of EEE modes which are not
supported by the hardware. We omit to check the
When the EEE advertisment is changed, we should restart autonegotiation
to update the link partner with the new EEE settings. Add this trigger
but only if the advertisment has changed.
Signed-off-by: Russell King
---
drivers/net/phy/phy.c | 21 +++--
As EEE is able to work in SGMII mode as well, add it to the list of
permissable EEE modes that phy_init_eee() will accept. This is
necessary so that EEE can work with an 88E1512 connected in SGMII mode.
Signed-off-by: Russell King
---
drivers/net/phy/phy.c | 1 +
1
Hi Joao
On 03/24/2017 06:09 PM, Joao Pinto wrote:
Hello David,
Às 5:05 PM de 3/24/2017, David Miller escreveu:
From: Andrew Lunn
Date: Fri, 24 Mar 2017 12:17:36 +0100
Yes it would be fantastic to have a set of boards, but I rarely see this in any
maintainer :).
Being a
When CONFIG_IPV6_SEG6_LWTUNNEL is selected, automatically select DST_CACHE.
This allows to remove multiple ifdefs.
Signed-off-by: David Lebrun
---
net/ipv6/Kconfig | 1 +
net/ipv6/seg6_iptunnel.c | 18 --
2 files changed, 1 insertion(+), 18
101 - 200 of 228 matches
Mail list logo