3.18.98-stable review
Greg Kroah-Hartman
maintainerPATCH 1/24 ipv6: Skip XFRM lookup if dst_entry in socket cache is valid
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jakub Sitnicki <[email protected]>
commit 00bc0ef5880dc7b82f9c320dead4afaad48e47be upstream.
At present we perform an xfrm_lookup() for each UDPv6 message we send. The lookup involves querying the flow cache (flow_cache_lookup) and, in case of a cache miss, creating an XFRM bundle.
If we miss the flow cache, we can end up creating a new bundle and deriving the path MTU (xfrm_init_pmtu) from on an already transformed dst_entry, which we pass from the socket cache (sk->sk_dst_cache) down to xfrm_lookup(). This can happen only if we're caching the dst_entry in the socket, that is when we're using a connected UDP socket.
To put it another way, the path MTU shrinks each time we miss the flow cache, which later on leads to incorrectly fragmented payload. It can be observed with ESPv6 in transport mode:
1) Set up a transformation and lower the MTU to trigger fragmentation
# ip xfrm policy add dir out src ::1 dst ::1 \
tmpl src ::1 dst ::1 proto esp spi 1
# ip xfrm state add src ::1 dst ::1 \
proto esp spi 1 enc 'aes' 0x0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b0b
# ip link set dev lo mtu 15002) Monitor the packet flow and set up an UDP sink
# tcpdump -ni lo -ttt &
# socat udp6-listen:12345,fork /dev/null &3) Send a datagram that needs fragmentation with a connected socket
# perl -e 'print "@" x 1470 | socat - udp6:[::1]:12345
2016/06/07 18:52:52 socat[724] E read(3, 0x555bb3d5ba00, 8192): Protocol error
00:00:00.000000 IP6 ::1 > ::1: frag (0|1448) ESP(spi=0x00000001,seq=0x2), length 1448
00:00:00.000014 IP6 ::1 > ::1: frag (1448|32)
00:00:00.000050 IP6 ::1 > ::1: ESP(spi=0x00000001,seq=0x3), length 1272
(^ ICMPv6 Parameter Problem)
00:00:00.000022 IP6 ::1 > ::1: ESP(spi=0x00000001,seq=0x5), length 1364) Compare it to a non-connected socket
# perl -e 'print "@" x 1500' | socat - udp6-sendto:[::1]:12345
00:00:40.535488 IP6 ::1 > ::1: frag (0|1448) ESP(spi=0x00000001,seq=0x6), length 1448
00:00:00.000010 IP6 ::1 > ::1: frag (1448|64)What happens in step (3) is:
1) when connecting the socket in __ip6_datagram_connect(), we perform an XFRM lookup, miss the flow cache, create an XFRM bundle, and cache the destination,
2) afterwards, when sending the datagram, we perform an XFRM lookup, again, miss the flow cache (due to mismatch of flowi6_iif and flowi6_oif, which is an issue of its own), and recreate an XFRM bundle based on the cached (and already transformed) destination.
To prevent the recreation of an XFRM bundle, avoid an XFRM lookup altogether whenever we already have a destination entry cached in the socket. This prevents the path MTU shrinkage and brings us on par with UDPv4.
The fix also benefits connected PINGv6 sockets, another user of ip6_sk_dst_lookup_flow(), who also suffer messages being transformed twice.
Joint work with Hannes Frederic Sowa.
--- net/ipv6/ip6_output.c | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-)
net/ipv6/ip6_output.c +3 -8
@@ -1038,17 +1038,12 @@ struct dst_entry *ip6_sk_dst_lookup_flow const struct in6_addr *final_dst) {struct dst_entry *dst =sk_dst_check (sk,inet6_sk (sk)->dst_cookie); -int err; dst =ip6_sk_dst_check (sk, dst, fl6); +if (!dst) + dst =ip6_dst_lookup_flow (sk, fl6, final_dst); - err =ip6_dst_lookup_tail (sk, &dst, fl6); -if (err) -return ERR_PTR (err); -if (final_dst) - fl6->daddr = *final_dst; - -return xfrm_lookup_route (sock_net (sk), dst,flowi6_to_flowi (fl6), sk,0 ); +return dst; }EXPORT_SYMBOL_GPL (ip6_sk_dst_lookup_flow);
Greg Kroah-Hartman
maintainerPATCH 8/24 scsi: storvsc: Fix scsi_cmd error assignments in storvsc_handle_error
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Cathy Avery <[email protected]>
[ Upstream commit d1b8b2391c24751e44f618fcf86fb55d9a9247fd ]
When an I/O is returned with an srb_status of SRB_STATUS_INVALID_LUN which has zero good_bytes it must be assigned an error. Otherwise the I/O will be continuously requeued and will cause a deadlock in the case where disks are being hot added and removed. sd_probe_async will wait forever for its I/O to complete while holding scsi_sd_probe_domain.
Also returning the default error of DID_TARGET_FAILURE causes multipath to not retry the I/O resulting in applications receiving I/O errors before a failover can occur.
--- drivers/scsi/storvsc_drv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/scsi/storvsc_drv.c +2 -1
@@ -1029,10 +1029,11 @@ static void storvsc_handle_error(structcase TEST_UNIT_READY :break ;default : -set_host_byte (scmnd,DID_TARGET_FAILURE ); +set_host_byte (scmnd,DID_ERROR ); }break ;case SRB_STATUS_INVALID_LUN : +set_host_byte (scmnd,DID_NO_CONNECT ); do_work = true; process_err_fn = storvsc_remove_lun;break ;
Greg Kroah-Hartman
maintainerPATCH 9/24 tg3: Add workaround to restrict 5762 MRRS to 2048
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Siva Reddy Kallam <[email protected]>
[ Upstream commit 4419bb1cedcda0272e1dc410345c5a1d1da0e367 ]
One of AMD based server with 5762 hangs with jumbo frame traffic. This AMD platform has southbridge limitation which is restricting MRRS to 4000. As a work around, driver to restricts the MRRS to 2048 for this particular 5762 NX1 card.
--- drivers/net/ethernet/broadcom/tg3.c | 10 ++++++++++ drivers/net/ethernet/broadcom/tg3.h | 4 ++++ 2 files changed, 14 insertions(+)
drivers/net/ethernet/broadcom/tg3.c +10 -0
@@ -10028,6 +10028,16 @@ static int tg3_reset_hw(struct tg3 *tp,tw32 (GRC_MODE , tp->grc_mode | val); +/* On one of the AMD platform, MRRS is restricted to 4000 because of +* south bridge limitation. As a workaround, Driver is setting MRRS +* to 2048 instead of default 4096. +*/ +if (tp->pdev->subsystem_vendor ==PCI_VENDOR_ID_DELL && + tp->pdev->subsystem_device ==TG3PCI_SUBDEVICE_ID_DELL_5762 ) { + val =tr32 (TG3PCI_DEV_STATUS_CTRL ) & ~MAX_READ_REQ_MASK ; +tw32 (TG3PCI_DEV_STATUS_CTRL , val |MAX_READ_REQ_SIZE_2048 ); + } +/* Setup the timer prescalar register. Clock is always 66Mhz. */ val =tr32 (GRC_MISC_CFG ); val &= ~0xff ;
drivers/net/ethernet/broadcom/tg3.h +4 -0
@@ -95,6 +95,7 @@#define TG3PCI_SUBDEVICE_ID_DELL_JAGUAR 0x0106#define TG3PCI_SUBDEVICE_ID_DELL_MERLOT 0x0109#define TG3PCI_SUBDEVICE_ID_DELL_SLIM_MERLOT 0x010a +#define TG3PCI_SUBDEVICE_ID_DELL_5762 0x07f0#define TG3PCI_SUBVENDOR_ID_COMPAQ PCI_VENDOR_ID_COMPAQ#define TG3PCI_SUBDEVICE_ID_COMPAQ_BANSHEE 0x007c#define TG3PCI_SUBDEVICE_ID_COMPAQ_BANSHEE_2 0x009a
@@ -280,6 +281,9 @@#define TG3PCI_STD_RING_PROD_IDX 0x00000098/* 64-bit */ #define TG3PCI_RCV_RET_RING_CON_IDX 0x000000a0/* 64-bit */ /* 0xa8 --> 0xb8 unused */ +#define TG3PCI_DEV_STATUS_CTRL 0x000000b4 +#define MAX_READ_REQ_SIZE_2048 0x00004000 +#define MAX_READ_REQ_MASK 0x00007000#define TG3PCI_DUAL_MAC_CTRL 0x000000b8#define DUAL_MAC_CTRL_CH_MASK 0x00000003#define DUAL_MAC_CTRL_ID 0x00000004
Greg Kroah-Hartman
maintainerPATCH 17/24 drm/ttm: check the return value of kzalloc
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Xiongwei Song <[email protected]>
[ Upstream commit 19d859a7205bc59ffc38303eb25ae394f61d21dc ]
In the function ttm_page_alloc_init, kzalloc call is made for variable _manager, we need to check its return value, it may return NULL.
--- drivers/gpu/drm/ttm/ttm_page_alloc.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/gpu/drm/ttm/ttm_page_alloc.c +2 -0
@@ -818,6 +818,8 @@ int ttm_page_alloc_init(struct ttm_mem_gpr_info ("Initializing pool allocator\n" ); _manager =kzalloc (sizeof (*_manager),GFP_KERNEL ); +if (!_manager) +return -ENOMEM ;ttm_page_pool_init_locked (&_manager->wc_pool,GFP_HIGHUSER ,"wc" );
Greg Kroah-Hartman
maintainerPATCH 18/24 xen-netfront: enable device after manual module load
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eduardo Otubo <[email protected]>
[ Upstream commit b707fda2df4070785d0fa8a278aa13944c5f51f8 ]
When loading the module after unloading it, the network interface would not be enabled and thus wouldn't have a backend counterpart and unable to be used by the guest.
The guest would face errors like:
[root@guest ~]# ethtool -i eth0
Cannot get driver information: No such device
[root@guest ~]# ifconfig eth0
eth0: error fetching interface information: Device not found
This patch initializes the state of the netfront device whenever it is loaded manually, this state would communicate the netback to create its device and establish the connection between them.
--- drivers/net/xen-netfront.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/xen-netfront.c +1 -0
@@ -1358,6 +1358,7 @@ static struct net_device *xennet_create_netif_carrier_off (netdev); +xenbus_switch_state (dev, XenbusStateInitialising);return netdev; exit:
Greg Kroah-Hartman
maintainerPATCH 22/24 xen/gntdev: Fix partial gntdev_mmap() cleanup
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ross Lagerwall <[email protected]>
[ Upstream commit cf2acf66ad43abb39735568f55e1f85f9844e990 ]
When cleaning up after a partially successful gntdev_mmap(), unmap the successfully mapped grant pages otherwise Xen will kill the domain if in debug mode (Attempt to implicitly unmap a granted PTE) or Linux will kill the process and emit "BUG: Bad page map in process" if Xen is in release mode.
This is only needed when use_ptemod is true because gntdev_put_map() will unmap grant pages itself when use_ptemod is false.
--- drivers/xen/gntdev.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/xen/gntdev.c +3 -1
@@ -817,8 +817,10 @@ unlock_out: out_unlock_put:mutex_unlock (&priv->lock); out_put_map: -if (use_ptemod) +if (use_ptemod) { map->vma =NULL ; +unmap_grant_pages (map,0 , map->count); + }gntdev_put_map (priv, map);return err; }
Greg Kroah-Hartman
maintainercover 3.18.98-stable review
This is the start of the stable review cycle for the 3.18.98 release. There are 24 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sun Mar 4 08:42:22 UTC 2018. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.98-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-3.18.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 3.18.98-rc1
Yangbo Lu <[email protected]>
net: gianfar_ptp: move set_fipers() to spinlock protecting area
Marcelo Ricardo Leitner <[email protected]>
sctp: make use of pre-calculated len
Ross Lagerwall <[email protected]>
xen/gntdev: Fix partial gntdev_mmap() cleanup
Ross Lagerwall <[email protected]>
xen/gntdev: Fix off-by-one error when unmapping with holes
Sergei Shtylyov <[email protected]>
SolutionEngine771x: fix Ether platform data
Christophe JAILLET <[email protected]>
mdio-sun4i: Fix a memory leak
Eduardo Otubo <[email protected]>
xen-netfront: enable device after manual module load
Xiongwei Song <[email protected]>
drm/ttm: check the return value of kzalloc
Tushar Dave <[email protected]>
e1000: fix disabling already-disabled warning
Aliaksei Karaliou <[email protected]>
xfs: quota: check result of register_shrinker()
Aliaksei Karaliou <[email protected]>
xfs: quota: fix missed destroy of qi_tree_lock
Stefan Haberland <[email protected]>
s390/dasd: fix wrongly assigned configuration data
Matthieu CASTET <[email protected]>
led: core: Fix brightness setting when setting delay_off=0
Guilherme G. Piccoli <[email protected]>
bnx2x: Improve reliability in case of nested PCI errors
Siva Reddy Kallam <[email protected]>
tg3: Enable PHY reset in MTU change path for 5720
Siva Reddy Kallam <[email protected]>
tg3: Add workaround to restrict 5762 MRRS to 2048
Cathy Avery <[email protected]>
scsi: storvsc: Fix scsi_cmd error assignments in storvsc_handle_error
Alexander Kochetkov <[email protected]>
net: arc_emac: fix arc_emac_rx() error paths
Radu Pirea <[email protected]>
spi: atmel: fixed spin_lock usage inside atmel_spi_remove
Al Viro <[email protected]>
sget(): handle failures of register_shrinker()
Brendan McGrath <[email protected]>
ipv6: icmp6: Allow icmp messages to be looped back
Sascha Hauer <[email protected]>
mtd: nand: gpmi: Fix failure when a erased page has a bitflip at BBM
Anna-Maria Gleixner <[email protected]>
hrtimer: Ensure POSIX compliance (relative CLOCK_REALTIME hrtimers)
Jakub Sitnicki <[email protected]>
ipv6: Skip XFRM lookup if dst_entry in socket cache is valid
-------------
Diffstat:
Makefile | 4 +- arch/sh/boards/mach-se/770x/setup.c | 10 ++++- drivers/gpu/drm/ttm/ttm_page_alloc.c | 2 + drivers/leds/led-core.c | 2 +- drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 6 +-- drivers/net/ethernet/arc/emac_main.c | 53 ++++++++++++++---------- drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 4 +- drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c | 14 ++++++- drivers/net/ethernet/broadcom/tg3.c | 13 +++++- drivers/net/ethernet/broadcom/tg3.h | 4 ++ drivers/net/ethernet/freescale/gianfar_ptp.c | 3 +- drivers/net/ethernet/intel/e1000/e1000.h | 3 +- drivers/net/ethernet/intel/e1000/e1000_main.c | 27 +++++++++--- drivers/net/phy/mdio-sun4i.c | 6 ++- drivers/net/xen-netfront.c | 1 + drivers/s390/block/dasd_3990_erp.c | 10 +++++ drivers/scsi/storvsc_drv.c | 3 +- drivers/spi/spi-atmel.c | 2 +- drivers/xen/gntdev.c | 8 ++-- fs/super.c | 6 ++- fs/xfs/xfs_qm.c | 46 +++++++++++++------- kernel/time/hrtimer.c | 7 +++- net/ipv6/ip6_output.c | 11 ++--- net/ipv6/route.c | 1 + net/sctp/socket.c | 16 ++++--- 25 files changed, 180 insertions(+), 82 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 10/24 tg3: Enable PHY reset in MTU change path for 5720
3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Siva Reddy Kallam <[email protected]>
[ Upstream commit e60ee41aaf898584205a6af5c996860d0fe6a836 ]
A customer noticed RX path hang when MTU is changed on the fly while running heavy traffic with NCSI enabled for 5717 and 5719. Since 5720 belongs to same ASIC family, we observed same issue and same fix could solve this problem for 5720.
--- drivers/net/ethernet/broadcom/tg3.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/ethernet/broadcom/tg3.c +2 -1
@@ -14214,7 +14214,8 @@ static int tg3_change_mtu(struct net_dev*/ if (tg3_asic_rev (tp) ==ASIC_REV_57766 ||tg3_asic_rev (tp) ==ASIC_REV_5717 || -tg3_asic_rev (tp) ==ASIC_REV_5719 ) +tg3_asic_rev (tp) ==ASIC_REV_5719 || +tg3_asic_rev (tp) ==ASIC_REV_5720 ) reset_phy = true; err =tg3_restart_hw (tp, reset_phy);
Greg Kroah-Hartman
maintainerPATCH 11/24 bnx2x: Improve reliability in case of nested PCI errors
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Guilherme G. Piccoli" <[email protected]>
[ Upstream commit f7084059a9cb9e56a186e1677b1dcffd76c2cd24 ]
While in recovery process of PCI error (called EEH on PowerPC arch), another PCI transaction could be corrupted causing a situation of nested PCI errors. Also, this scenario could be reproduced with error injection mechanisms (for debug purposes).
We observe that in case of nested PCI errors, bnx2x might attempt to initialize its shmem and cause a kernel crash due to bad addresses read from MCP. Multiple different stack traces were observed depending on the point the second PCI error happens.
This patch avoids the crashes by:
* failing PCI recovery in case of nested errors (since multiple PCI errors in a row are not expected to lead to a functional adapter anyway), and by,
* preventing access to adapter FW when MCP is failed (we mark it as failed when shmem cannot get initialized properly).
--- drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 4 ++-- drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c | 14 +++++++++++++- 2 files changed, 15 insertions(+), 3 deletions(-)
drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c +2 -2
@@ -2994,7 +2994,7 @@ int bnx2x_nic_unload(struct bnx2x *bp, idel_timer_sync (&bp->timer); -if (IS_PF (bp)) { +if (IS_PF (bp) && !BP_NOMCP (bp)) {/* Set ALWAYS_ALIVE bit in shmem */ bp->fw_drv_pulse_wr_seq |=DRV_PULSE_ALWAYS_ALIVE ;bnx2x_drv_pulse (bp);
@@ -3076,7 +3076,7 @@ int bnx2x_nic_unload(struct bnx2x *bp, i bp->cnic_loaded = false;/* Clear driver version indication in shmem */ -if (IS_PF (bp)) +if (IS_PF (bp) && !BP_NOMCP (bp))bnx2x_update_mng_version (bp);/* Check if there are pending parity attentions. If there are - set
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c +13 -1
@@ -9472,6 +9472,15 @@ static int bnx2x_init_shmem(struct bnx2x do { bp->common.shmem_base = REG_RD(bp, MISC_REG_SHARED_MEM_ADDR); + + /* If we read all 0xFFs, means we are in PCI error state and + * should bail out to avoid crashes on adapter's FW reads. + */ + if (bp->common.shmem_base == 0xFFFFFFFF) { + bp->flags |= NO_MCP_FLAG; + return -ENODEV; + } + if (bp->common.shmem_base) { val = SHMEM_RD(bp, validity_map[BP_PORT(bp)]); if (val & SHR_MEM_VALIDITY_MB)
@@ -13743,7 +13752,10 @@ static pci_ers_result_t bnx2x_io_slot_reBNX2X_ERR ("IO slot reset --> driver unload\n" );/* MCP should have been reset; Need to wait for validity */ -bnx2x_init_shmem (bp); +if (bnx2x_init_shmem (bp)) { +rtnl_unlock (); +return PCI_ERS_RESULT_DISCONNECT ; + }if (IS_PF (bp) &&SHMEM2_HAS (bp, drv_capabilities_flag)) {u32 v;
Greg Kroah-Hartman
maintainerPATCH 12/24 led: core: Fix brightness setting when setting delay_off=0
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Matthieu CASTET <[email protected]>
[ Upstream commit 2b83ff96f51d0b039c4561b9f95c824d7bddb85c ]
With the current code, the following sequence won't work :
echo timer > trigger
echo 0 > delay_off
* at this point we call
** led_delay_off_store
** led_blink_set
--- drivers/leds/led-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/leds/led-core.c +1 -1
@@ -76,7 +76,7 @@ void led_blink_set(struct led_classdev *unsigned long *delay_on, unsigned long *delay_off) { - del_timer_sync(&led_cdev->blink_timer); +led_stop_software_blink (led_cdev ); led_cdev->flags &= ~LED_BLINK_ONESHOT ; led_cdev->flags &= ~LED_BLINK_ONESHOT_STOP ;
Greg Kroah-Hartman
maintainerPATCH 13/24 s390/dasd: fix wrongly assigned configuration data
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stefan Haberland <[email protected]>
[ Upstream commit 8a9bd4f8ebc6800bfc0596e28631ff6809a2f615 ]
We store per path and per device configuration data to identify the path or device correctly. The per path configuration data might get mixed up if the original request gets into error recovery and is started with a random path mask.
This would lead to a wrong identification of a path in case of a CUIR event for example.
Fix by copying the path mask from the original request to the error recovery request in case it is a path verification request.
--- drivers/s390/block/dasd_3990_erp.c | 10 ++++++++++ 1 file changed, 10 insertions(+)
drivers/s390/block/dasd_3990_erp.c +10 -0
@@ -2743,6 +2743,16 @@ dasd_3990_erp_action(struct dasd_ccw_req erp =dasd_3990_erp_handle_match_erp (cqr, erp); } + +/* +* For path verification work we need to stick with the path that was +* originally chosen so that the per path configuration data is +* assigned correctly. +*/ +if (test_bit (DASD_CQR_VERIFY_PATH , &erp->flags) && cqr->lpm) { + erp->lpm = cqr->lpm; + } +if (device->features &DASD_FEATURE_ERPLOG ) {/* print current erp_chain */ dev_err(&device->cdev->dev,
Greg Kroah-Hartman
maintainerPATCH 14/24 xfs: quota: fix missed destroy of qi_tree_lock
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Aliaksei Karaliou <[email protected]>
[ Upstream commit 2196881566225f3c3428d1a5f847a992944daa5b ]
xfs_qm_destroy_quotainfo() does not destroy quotainfo->qi_tree_lock while destroys quotainfo->qi_quotaofflock.
--- fs/xfs/xfs_qm.c | 1 + 1 file changed, 1 insertion(+)
fs/xfs/xfs_qm.c +1 -0
@@ -703,6 +703,7 @@ xfs_qm_destroy_quotainfo(IRELE (qi->qi_pquotaip); qi->qi_pquotaip =NULL ; } +mutex_destroy (&qi->qi_tree_lock);mutex_destroy (&qi->qi_quotaofflock);kmem_free (qi); mp->m_quotainfo =NULL ;
Greg Kroah-Hartman
maintainerPATCH 15/24 xfs: quota: check result of register_shrinker()
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Aliaksei Karaliou <[email protected]>
[ Upstream commit 3a3882ff26fbdbaf5f7e13f6a0bccfbf7121041d ]
xfs_qm_init_quotainfo() does not check result of register_shrinker() which was tagged as __must_check recently, reported by sparse.
--- fs/xfs/xfs_qm.c | 45 +++++++++++++++++++++++++++++---------------- 1 file changed, 29 insertions(+), 16 deletions(-)
fs/xfs/xfs_qm.c +29 -16
@@ -49,7 +49,7 @@ STATIC int xfs_qm_init_quotainos(xfs_mount_t *); STATIC int xfs_qm_init_quotainfo(xfs_mount_t *); - +STATIC void xfs_qm_destroy_quotainos(xfs_quotainfo_t *qi); STATIC void xfs_qm_dqfree_one(struct xfs_dquot *dqp);/* * We use the batch lookup interface to iterate over the dquots as it
@@ -662,9 +662,17 @@ xfs_qm_init_quotainfo( qinf->qi_shrinker.scan_objects = xfs_qm_shrink_scan; qinf->qi_shrinker.seeks =DEFAULT_SEEKS ; qinf->qi_shrinker.flags =SHRINKER_NUMA_AWARE ; -register_shrinker (&qinf->qi_shrinker); + + error =register_shrinker (&qinf->qi_shrinker); +if (error) + goto out_free_inos; +return 0 ; +out_free_inos: +mutex_destroy (&qinf->qi_quotaofflock); +mutex_destroy (&qinf->qi_tree_lock); +xfs_qm_destroy_quotainos (qinf); out_free_lru:list_lru_destroy (&qinf->qi_lru); out_free_qinf:
@@ -673,7 +681,6 @@ out_free_qinf:return error; } -/* * Gets called when unmounting a filesystem or when all quotas get * turned off.
@@ -690,19 +697,7 @@ xfs_qm_destroy_quotainfo(unregister_shrinker (&qi->qi_shrinker);list_lru_destroy (&qi->qi_lru); - -if (qi->qi_uquotaip) { -IRELE (qi->qi_uquotaip); - qi->qi_uquotaip =NULL ;/* paranoia */ - } -if (qi->qi_gquotaip) { -IRELE (qi->qi_gquotaip); - qi->qi_gquotaip =NULL ; - } -if (qi->qi_pquotaip) { -IRELE (qi->qi_pquotaip); - qi->qi_pquotaip =NULL ; - } +xfs_qm_destroy_quotainos (qi);mutex_destroy (&qi->qi_tree_lock);mutex_destroy (&qi->qi_quotaofflock);kmem_free (qi);
@@ -1574,6 +1569,24 @@ error_rele: } STATIC void +xfs_qm_destroy_quotainos ( +xfs_quotainfo_t *qi) +{ +if (qi->qi_uquotaip) { +IRELE (qi->qi_uquotaip); + qi->qi_uquotaip =NULL ;/* paranoia */ + } +if (qi->qi_gquotaip) { +IRELE (qi->qi_gquotaip); + qi->qi_gquotaip =NULL ; + } +if (qi->qi_pquotaip) { +IRELE (qi->qi_pquotaip); + qi->qi_pquotaip =NULL ; + } +} + +STATIC voidxfs_qm_dqfree_one (struct xfs_dquot *dqp) {
Greg Kroah-Hartman
maintainerPATCH 16/24 e1000: fix disabling already-disabled warning
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tushar Dave <[email protected]>
[ Upstream commit 0b76aae741abb9d16d2c0e67f8b1e766576f897d ]
This patch adds check so that driver does not disable already disabled device.
[ 44.637743] advantechwdt: Unexpected close, not stopping watchdog! [ 44.997548] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input6 [ 45.013419] e1000 0000:00:03.0: disabling already-disabled device [ 45.013447] ------------[ cut here ]------------ [ 45.014868] WARNING: CPU: 1 PID: 71 at drivers/pci/pci.c:1641 pci_disable_device+0xa1/0x105: pci_disable_device at drivers/pci/pci.c:1640 [ 45.016171] CPU: 1 PID: 71 Comm: rcu_perf_shutdo Not tainted 4.14.0-01330-g3c07399 #1 [ 45.017197] task: ffff88011bee9e40 task.stack: ffffc90000860000 [ 45.017987] RIP: 0010:pci_disable_device+0xa1/0x105: pci_disable_device at drivers/pci/pci.c:1640 [ 45.018603] RSP: 0000:ffffc90000863e30 EFLAGS: 00010286 [ 45.019282] RAX: 0000000000000035 RBX: ffff88013a230008 RCX: 0000000000000000 [ 45.020182] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000203 [ 45.021084] RBP: ffff88013a3f31e8 R08: 0000000000000001 R09: 0000000000000000 [ 45.021986] R10: ffffffff827ec29c R11: 0000000000000002 R12: 0000000000000001 [ 45.022946] R13: ffff88013a230008 R14: ffff880117802b20 R15: ffffc90000863e8f [ 45.023842] FS: 0000000000000000(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000 [ 45.024863] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 45.025583] CR2: ffffc900006d4000 CR3: 000000000220f000 CR4: 00000000000006a0 [ 45.026478] Call Trace: [ 45.026811] __e1000_shutdown+0x1d4/0x1e2: __e1000_shutdown at drivers/net/ethernet/intel/e1000/e1000_main.c:5162 [ 45.027344] ? rcu_perf_cleanup+0x2a1/0x2a1: rcu_perf_shutdown at kernel/rcu/rcuperf.c:627 [ 45.027883] e1000_shutdown+0x14/0x3a: e1000_shutdown at drivers/net/ethernet/intel/e1000/e1000_main.c:5235 [ 45.028351] device_shutdown+0x110/0x1aa: device_shutdown at drivers/base/core.c:2807 [ 45.028858] kernel_power_off+0x31/0x64: kernel_power_off at kernel/reboot.c:260 [ 45.029343] rcu_perf_shutdown+0x9b/0xa7: rcu_perf_shutdown at kernel/rcu/rcuperf.c:637 [ 45.029852] ? __wake_up_common_lock+0xa2/0xa2: autoremove_wake_function at kernel/sched/wait.c:376 [ 45.030414] kthread+0x126/0x12e: kthread at kernel/kthread.c:233 [ 45.030834] ? __kthread_bind_mask+0x8e/0x8e: kthread at kernel/kthread.c:190 [ 45.031399] ? ret_from_fork+0x1f/0x30: ret_from_fork at arch/x86/entry/entry_64.S:443 [ 45.031883] ? kernel_init+0xa/0xf5: kernel_init at init/main.c:997 [ 45.032325] ret_from_fork+0x1f/0x30: ret_from_fork at arch/x86/entry/entry_64.S:443 [ 45.032777] Code: 00 48 85 ed 75 07 48 8b ab a8 00 00 00 48 8d bb 98 00 00 00 e8 aa d1 11 00 48 89 ea 48 89 c6 48 c7 c7 d8 e4 0b 82 e8 55 7d da ff <0f> ff b9 01 00 00 00 31 d2 be 01 00 00 00 48 c7 c7 f0 b1 61 82 [ 45.035222] ---[ end trace c257137b1b1976ef ]--- [ 45.037838] ACPI: Preparing to enter system sleep state S5
--- drivers/net/ethernet/intel/e1000/e1000.h | 3 +- drivers/net/ethernet/intel/e1000/e1000_main.c | 27 +++++++++++++++++++++----- 2 files changed, 24 insertions(+), 6 deletions(-)
drivers/net/ethernet/intel/e1000/e1000.h +2 -1
@@ -328,7 +328,8 @@ struct e1000_adapter {enum e1000_state_t { __E1000_TESTING, __E1000_RESETTING, - __E1000_DOWN + __E1000_DOWN, + __E1000_DISABLED };#undef pr_fmt
drivers/net/ethernet/intel/e1000/e1000_main.c +22 -5
@@ -940,7 +940,7 @@ static int e1000_init_hw_struct(struct estatic int e1000_probe (struct pci_dev *pdev,const struct pci_device_id *ent) {struct net_device *netdev; -struct e1000_adapter *adapter; +struct e1000_adapter *adapter =NULL ;struct e1000_hw *hw;static int cards_found =0 ;
@@ -950,6 +950,7 @@ static int e1000_probe(struct pci_dev *pu16 tmp =0 ;u16 eeprom_apme_mask =E1000_EEPROM_APME ;int bars, need_ioport; +bool disable_dev = false;/* do not allocate ioport bars when not needed */ need_ioport =e1000_is_need_ioport (pdev);
@@ -1250,11 +1251,13 @@ err_mdio_ioremap:iounmap (hw->ce4100_gbe_mdio_base_virt);iounmap (hw->hw_addr); err_ioremap: + disable_dev = !test_and_set_bit (__E1000_DISABLED, &adapter->flags);free_netdev (netdev); err_alloc_etherdev:pci_release_selected_regions (pdev, bars); err_pci_reg: -pci_disable_device (pdev); +if (!adapter || disable_dev) +pci_disable_device (pdev);return err; }
@@ -1272,6 +1275,7 @@ static void e1000_remove(struct pci_devstruct net_device *netdev =pci_get_drvdata (pdev);struct e1000_adapter *adapter =netdev_priv (netdev);struct e1000_hw *hw = &adapter->hw; +bool disable_dev;e1000_down_and_stop (adapter);e1000_release_manageability (adapter);
@@ -1290,9 +1294,11 @@ static void e1000_remove(struct pci_deviounmap (hw->flash_address);pci_release_selected_regions (pdev, adapter->bars); + disable_dev = !test_and_set_bit (__E1000_DISABLED, &adapter->flags);free_netdev (netdev); -pci_disable_device (pdev); +if (disable_dev) +pci_disable_device (pdev); }/**
@@ -5137,7 +5143,8 @@ static int __e1000_shutdown(struct pci_dif (netif_running (netdev))e1000_free_irq (adapter); -pci_disable_device (pdev); +if (!test_and_set_bit (__E1000_DISABLED, &adapter->flags)) +pci_disable_device (pdev);return 0 ; }
@@ -5181,6 +5188,10 @@ static int e1000_resume(struct pci_dev *pr_err ("Cannot enable PCI device from suspend\n" );return err; } + +/* flush memory to make sure state is correct */ +smp_mb__before_atomic (); +clear_bit (__E1000_DISABLED, &adapter->flags);pci_set_master (pdev);pci_enable_wake (pdev, PCI_D3hot,0 );
@@ -5255,7 +5266,9 @@ static pci_ers_result_t e1000_io_error_dif (netif_running (netdev))e1000_down (adapter); -pci_disable_device (pdev); + +if (!test_and_set_bit (__E1000_DISABLED, &adapter->flags)) +pci_disable_device (pdev);/* Request a slot slot reset. */ return PCI_ERS_RESULT_NEED_RESET ;
@@ -5283,6 +5296,10 @@ static pci_ers_result_t e1000_io_slot_repr_err ("Cannot re-enable PCI device after reset.\n" );return PCI_ERS_RESULT_DISCONNECT ; } + +/* flush memory to make sure state is correct */ +smp_mb__before_atomic (); +clear_bit (__E1000_DISABLED, &adapter->flags);pci_set_master (pdev);pci_enable_wake (pdev, PCI_D3hot,0 );
Greg Kroah-Hartman
maintainerPATCH 19/24 mdio-sun4i: Fix a memory leak
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christophe JAILLET <[email protected]>
[ Upstream commit 56c0290202ab94a2f2780c449395d4ae8495fab4 ]
If the probing of the regulator is deferred, the memory allocated by 'mdiobus_alloc_size()' will be leaking.
It should be freed before the next call to 'sun4i_mdio_probe()' which will reallocate it.
--- drivers/net/phy/mdio-sun4i.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/net/phy/mdio-sun4i.c +4 -2
@@ -128,8 +128,10 @@ static int sun4i_mdio_probe(struct platf data->regulator =devm_regulator_get (&pdev->dev,"phy" );if (IS_ERR (data->regulator)) { -if (PTR_ERR (data->regulator) == -EPROBE_DEFER ) -return -EPROBE_DEFER ; +if (PTR_ERR (data->regulator) == -EPROBE_DEFER ) { + ret = -EPROBE_DEFER ; + goto err_out_free_mdiobus; + }dev_info (&pdev->dev,"no regulator found\n" ); }else {
Greg Kroah-Hartman
maintainerPATCH 2/24 hrtimer: Ensure POSIX compliance (relative CLOCK_REALTIME hrtimers)
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Anna-Maria Gleixner <[email protected]>
commit 48d0c9becc7f3c66874c100c126459a9da0fdced upstream.
The POSIX specification defines that relative CLOCK_REALTIME timers are not affected by clock modifications. Those timers have to use CLOCK_MONOTONIC to ensure POSIX compliance.
The introduction of the additional HRTIMER_MODE_PINNED mode broke this requirement for pinned timers.
There is no user space visible impact because user space timers are not using pinned mode, but for consistency reasons this needs to be fixed.
Check whether the mode has the HRTIMER_MODE_REL bit set instead of comparing with HRTIMER_MODE_ABS.
--- kernel/time/hrtimer.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
kernel/time/hrtimer.c +6 -1
@@ -1149,7 +1149,12 @@ static void __hrtimer_init(struct hrtime cpu_base =raw_cpu_ptr (&hrtimer_bases); -if (clock_id ==CLOCK_REALTIME && mode !=HRTIMER_MODE_ABS ) +/* +* POSIX magic: Relative CLOCK_REALTIME timers are not affected by +* clock modifications, so they needs to become CLOCK_MONOTONIC to +* ensure POSIX compliance. +*/ +if (clock_id ==CLOCK_REALTIME && mode &HRTIMER_MODE_REL ) clock_id =CLOCK_MONOTONIC ; base =hrtimer_clockid_to_base (clock_id);
Greg Kroah-Hartman
maintainerPATCH 20/24 SolutionEngine771x: fix Ether platform data
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sergei Shtylyov <[email protected]>
[ Upstream commit 195e2addbce09e5afbc766efc1e6567c9ce840d3 ]
The 'sh_eth' driver's probe() method would fail on the SolutionEngine7710 board and crash on SolutionEngine7712 board as the platform code is hopelessly behind the driver's platform data -- it passes the PHY address instead of 'struct sh_eth_plat_data *'; pass the latter to the driver in order to fix the bug...
--- arch/sh/boards/mach-se/770x/setup.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
arch/sh/boards/mach-se/770x/setup.c +8 -2
@@ -8,6 +8,7 @@*/ #include <linux/init.h> #include <linux/platform_device.h> +#include <linux/sh_eth.h> #include <mach-se/mach/se.h> #include <mach-se/mach/mrshpc.h> #include <asm/machvec.h>
@@ -114,6 +115,11 @@ static struct platform_device heartbeat_ #if defined(CONFIG_CPU_SUBTYPE_SH7710) ||\ defined(CONFIG_CPU_SUBTYPE_SH7712) /* SH771X Ethernet driver */ +static struct sh_eth_plat_data sh_eth_plat = { + .phy = PHY_ID, + .phy_interface = PHY_INTERFACE_MODE_MII, +}; + static struct resource sh_eth0_resources[] = { [0] = { .start = SH_ETH0_BASE,
@@ -131,7 +137,7 @@ static struct platform_device sh_eth0_de .name = "sh771x-ether", .id = 0, .dev = { - .platform_data = PHY_ID, + .platform_data = &sh_eth_plat, }, .num_resources = ARRAY_SIZE(sh_eth0_resources), .resource = sh_eth0_resources,
@@ -154,7 +160,7 @@ static struct platform_device sh_eth1_de .name = "sh771x-ether", .id = 1, .dev = { - .platform_data = PHY_ID, + .platform_data = &sh_eth_plat, }, .num_resources = ARRAY_SIZE(sh_eth1_resources), .resource = sh_eth1_resources,
Greg Kroah-Hartman
maintainerPATCH 21/24 xen/gntdev: Fix off-by-one error when unmapping with holes
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ross Lagerwall <[email protected]>
[ Upstream commit 951a010233625b77cde3430b4b8785a9a22968d1 ]
If the requested range has a hole, the calculation of the number of pages to unmap is off by one. Fix it.
--- drivers/xen/gntdev.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/xen/gntdev.c +1 -3
@@ -348,10 +348,8 @@ static int unmap_grant_pages(struct gran } range =0 ;while (range < pages) { -if (map->unmap_ops[offset+range].handle ==-1 ) { - range--; +if (map->unmap_ops[offset+range].handle ==-1 )break ; - } range++; } err =__unmap_grant_pages (map, offset, range);
Greg Kroah-Hartman
maintainerPATCH 23/24 sctp: make use of pre-calculated len
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marcelo Ricardo Leitner <[email protected]>
[ Upstream commit c76f97c99ae6d26d14c7f0e50e074382bfbc9f98 ]
Some sockopt handling functions were calculating the length of the buffer to be written to userspace and then calculating it again when actually writing the buffer, which could lead to some write not using an up-to-date length.
This patch updates such places to just make use of the len variable.
Also, replace some sizeof(type) to sizeof(var).
--- net/sctp/socket.c | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-)
net/sctp/socket.c +10 -6
@@ -4458,7 +4458,7 @@ static int sctp_getsockopt_autoclose(str len =sizeof (int );if (put_user (len, optlen))return -EFAULT ; -if (copy_to_user (optval, &sctp_sk (sk)->autoclose,sizeof (int ))) +if (copy_to_user (optval, &sctp_sk (sk)->autoclose, len))return -EFAULT ;return 0 ; }
@@ -5035,6 +5035,9 @@ copy_getaddrs: err = -EFAULT ; goto out; } +/* XXX: We should have accounted for sizeof(struct sctp_getaddrs) too, +* but we can't change it anymore. +*/ if (put_user (bytes_copied, optlen)) err = -EFAULT ; out:
@@ -5471,7 +5474,7 @@ static int sctp_getsockopt_maxseg(struct params.assoc_id =0 ; }else if (len >=sizeof (struct sctp_assoc_value )) { len =sizeof (struct sctp_assoc_value ); -if (copy_from_user (¶ms, optval,sizeof (params))) +if (copy_from_user (¶ms, optval, len))return -EFAULT ; }else return -EINVAL ;
@@ -5635,7 +5638,9 @@ static int sctp_getsockopt_active_key(stif (len <sizeof (struct sctp_authkeyid ))return -EINVAL ; -if (copy_from_user (&val, optval,sizeof (struct sctp_authkeyid ))) + + len =sizeof (struct sctp_authkeyid ); +if (copy_from_user (&val, optval, len))return -EFAULT ; asoc =sctp_id2assoc (sk, val.scact_assoc_id);
@@ -5647,7 +5652,6 @@ static int sctp_getsockopt_active_key(stelse val.scact_keynumber = ep->active_key_id; - len =sizeof (struct sctp_authkeyid );if (put_user (len, optlen))return -EFAULT ;if (copy_to_user (optval, &val, len))
@@ -5673,7 +5677,7 @@ static int sctp_getsockopt_peer_auth_chuif (len <sizeof (struct sctp_authchunks ))return -EINVAL ; -if (copy_from_user (&val, optval,sizeof (struct sctp_authchunks ))) +if (copy_from_user (&val, optval,sizeof (val)))return -EFAULT ; to = p->gauth_chunks;
@@ -5718,7 +5722,7 @@ static int sctp_getsockopt_local_auth_chif (len <sizeof (struct sctp_authchunks ))return -EINVAL ; -if (copy_from_user (&val, optval,sizeof (struct sctp_authchunks ))) +if (copy_from_user (&val, optval,sizeof (val)))return -EFAULT ; to = p->gauth_chunks;
Greg Kroah-Hartman
maintainerPATCH 24/24 net: gianfar_ptp: move set_fipers() to spinlock protecting area
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yangbo Lu <[email protected]>
[ Upstream commit 11d827a993a969c3c6ec56758ff63a44ba19b466 ]
set_fipers() calling should be protected by spinlock in case that any interrupt breaks related registers setting and the function we expect. This patch is to move set_fipers() to spinlock protecting area in ptp_gianfar_adjtime().
--- drivers/net/ethernet/freescale/gianfar_ptp.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/net/ethernet/freescale/gianfar_ptp.c +1 -2
@@ -314,11 +314,10 @@ static int ptp_gianfar_adjtime(struct pt now =tmr_cnt_read (etsects); now += delta;tmr_cnt_write (etsects, now); +set_fipers (etsects);spin_unlock_irqrestore (&etsects->lock, flags); -set_fipers (etsects); -return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 3/24 mtd: nand: gpmi: Fix failure when a erased page has a bitflip at BBM
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sascha Hauer <[email protected]>
[ Upstream commit fdf2e821052958a114618a95ab18a300d0b080cb ]
When erased subpages are read then the BCH decoder returns STATUS_ERASED if they are all empty, or STATUS_UNCORRECTABLE if there are bitflips. When there are bitflips, we have to set these bits again to show the upper layers a completely erased page. When a bitflip happens in the exact byte where the bad block marker is, then this byte is swapped with another byte in block_mark_swapping(). The correction code then detects a bitflip in another subpage and no longer corrects the bitflip where it really happens.
Correct this behaviour by calling block_mark_swapping() after the bitflips have been corrected.
In our case UBIFS failed with this bug because it expects erased pages to be really empty:
UBIFS error (pid 187): ubifs_scan: corrupt empty space at LEB 36:118735 UBIFS error (pid 187): ubifs_scanned_corruption: corruption at LEB 36:118735 UBIFS error (pid 187): ubifs_scanned_corruption: first 8192 bytes from LEB 36:118735 UBIFS error (pid 187): ubifs_scan: LEB 36 scanning failed
UBIFS error (pid 187): do_commit: commit failed, error -117
--- drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/mtd/nand/gpmi-nand/gpmi-nand.c +3 -3
@@ -1025,9 +1025,6 @@ static int gpmi_ecc_read_page(struct mtdreturn ret; } -/* handle the block mark swapping */ -block_mark_swapping (this, payload_virt, auxiliary_virt); -/* Loop over status bytes, accumulating ECC status. */ status = auxiliary_virt + nfc_geo->auxiliary_status_offset;
@@ -1043,6 +1040,9 @@ static int gpmi_ecc_read_page(struct mtd max_bitflips = max_t(unsigned int, max_bitflips, *status); } +/* handle the block mark swapping */ +block_mark_swapping (this, buf, auxiliary_virt); +if (oob_required) {/* * It's time to deliver the OOB bytes. See gpmi_ecc_read_oob()
Greg Kroah-Hartman
maintainerPATCH 4/24 ipv6: icmp6: Allow icmp messages to be looped back
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Brendan McGrath <[email protected]>
[ Upstream commit 588753f1eb18978512b1c9b85fddb457d46f9033 ]
One example of when an ICMPv6 packet is required to be looped back is when a host acts as both a Multicast Listener and a Multicast Router.
A Multicast Router will listen on address ff02::16 for MLDv2 messages.
Currently, MLDv2 messages originating from a Multicast Listener running on the same host as the Multicast Router are not being delivered to the Multicast Router. This is due to dst.input being assigned the default value of dst_discard.
This results in the packet being looped back but discarded before being delivered to the Multicast Router.
This patch sets dst.input to ip6_input to ensure a looped back packet is delivered to the Multicast Router.
--- net/ipv6/route.c | 1 + 1 file changed, 1 insertion(+)
net/ipv6/route.c +1 -0
@@ -1367,6 +1367,7 @@ struct dst_entry *icmp6_dst_alloc(struct } rt->dst.flags |=DST_HOST ; + rt->dst.input = ip6_input; rt->dst.output = ip6_output;atomic_set (&rt->dst.__refcnt,1 ); rt->rt6i_gateway = fl6->daddr;
Greg Kroah-Hartman
maintainerPATCH 5/24 sget(): handle failures of register_shrinker()
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Al Viro <[email protected]>
[ Upstream commit 9ee332d99e4d5a97548943b81c54668450ce641b ]
--- fs/super.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
fs/super.c +5 -1
@@ -476,7 +476,11 @@ retry:hlist_add_head (&s->s_instances, &type->fs_supers);spin_unlock (&sb_lock);get_filesystem (type); -register_shrinker (&s->s_shrink); + err =register_shrinker (&s->s_shrink); +if (err) { +deactivate_locked_super (s); + s =ERR_PTR (err); + }return s; }
Greg Kroah-Hartman
maintainerPATCH 6/24 spi: atmel: fixed spin_lock usage inside atmel_spi_remove
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Radu Pirea <[email protected]>
[ Upstream commit 66e900a3d225575c8b48b59ae1fe74bb6e5a65cc ]
The only part of atmel_spi_remove which needs to be atomic is hardware reset.
atmel_spi_stop_dma calls dma_terminate_all and this needs interrupts enabled.atmel_spi_release_dma calls dma_release_channel and dma_release_channel locks a mutex inside of spin_lock.
So the call of these functions can't be inside a spin_lock.
--- drivers/spi/spi-atmel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi-atmel.c +1 -1
@@ -1416,12 +1416,12 @@ static int atmel_spi_remove(struct platfstruct atmel_spi *as =spi_master_get_devdata (master);/* reset the hardware and block queue progress */ -spin_lock_irq (&as->lock);if (as->use_dma) {atmel_spi_stop_dma (as);atmel_spi_release_dma (as); } +spin_lock_irq (&as->lock);spi_writel (as,CR ,SPI_BIT (SWRST ));spi_writel (as,CR ,SPI_BIT (SWRST ));/* AT91SAM9263 Rev B workaround */ spi_readl (as,SR );
Greg Kroah-Hartman
maintainerPATCH 7/24 net: arc_emac: fix arc_emac_rx() error paths
In reply to Greg Kroah-Hartman3.18-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexander Kochetkov <[email protected]>
[ Upstream commit e688822d035b494071ecbadcccbd6f3325fb0f59 ]
arc_emac_rx() has some issues found by code review.
In case netdev_alloc_skb_ip_align() or dma_map_single() failure rx fifo entry will not be returned to EMAC.
In case dma_map_single() failure previously allocated skb became lost to driver. At the same time address of newly allocated skb will not be provided to EMAC.
--- drivers/net/ethernet/arc/emac_main.c | 53 ++++++++++++++++++++--------------- 1 file changed, 31 insertions(+), 22 deletions(-)
drivers/net/ethernet/arc/emac_main.c +31 -22
@@ -250,39 +250,48 @@ static int arc_emac_rx(struct net_devicecontinue ; } - pktlen = info &LEN_MASK ; - stats->rx_packets++; - stats->rx_bytes += pktlen; - skb = rx_buff->skb; -skb_put (skb, pktlen); - skb->dev = ndev; - skb->protocol =eth_type_trans (skb, ndev); - -dma_unmap_single (&ndev->dev,dma_unmap_addr (rx_buff, addr), -dma_unmap_len (rx_buff, len),DMA_FROM_DEVICE ); - -/* Prepare the BD for next cycle */ - rx_buff->skb =netdev_alloc_skb_ip_align (ndev, -EMAC_BUFFER_SIZE ); -if (unlikely (!rx_buff->skb)) { +/* Prepare the BD for next cycle. netif_receive_skb() +* only if new skb was allocated and mapped to avoid holes +* in the RX fifo. +*/ + skb =netdev_alloc_skb_ip_align (ndev,EMAC_BUFFER_SIZE ); +if (unlikely (!skb)) { +if (net_ratelimit ()) +netdev_err (ndev,"cannot allocate skb\n" ); +/* Return ownership to EMAC */ + rxbd->info =cpu_to_le32 (FOR_EMAC |EMAC_BUFFER_SIZE ); stats->rx_errors++; -/* Because receive_skb is below, increment rx_dropped */ stats->rx_dropped++;continue ; } -/* receive_skb only if new skb was allocated to avoid holes */ -netif_receive_skb (skb); - - addr =dma_map_single (&ndev->dev, (void *)rx_buff->skb->data, + addr =dma_map_single (&ndev->dev, (void *)skb->data,EMAC_BUFFER_SIZE ,DMA_FROM_DEVICE );if (dma_mapping_error (&ndev->dev, addr)) {if (net_ratelimit ()) -netdev_err (ndev,"cannot dma map\n" ); -dev_kfree_skb (rx_buff->skb); +netdev_err (ndev,"cannot map dma buffer\n" ); +dev_kfree_skb (skb); +/* Return ownership to EMAC */ + rxbd->info =cpu_to_le32 (FOR_EMAC |EMAC_BUFFER_SIZE ); stats->rx_errors++; + stats->rx_dropped++;continue ; } + +/* unmap previosly mapped skb */ +dma_unmap_single (&ndev->dev,dma_unmap_addr (rx_buff, addr), +dma_unmap_len (rx_buff, len),DMA_FROM_DEVICE ); + + pktlen = info &LEN_MASK ; + stats->rx_packets++; + stats->rx_bytes += pktlen; +skb_put (rx_buff->skb, pktlen); + rx_buff->skb->dev = ndev; + rx_buff->skb->protocol =eth_type_trans (rx_buff->skb, ndev); + +netif_receive_skb (rx_buff->skb); + + rx_buff->skb = skb;dma_unmap_addr_set (rx_buff, addr, addr);dma_unmap_len_set (rx_buff, len,EMAC_BUFFER_SIZE );
stable-rc/linux-3.18.y boot: 33 boots: 0 failed, 33 passed (v3.18.97-25-g185185965d8b)
stable-rc/linux-3.18.y boot: 33 boots: 0 failed, 33 passed (v3.18.97-25-g185185965d8b)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-3.18.y/kernel/v3.18.97-25-g185185965d8b/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-3.18.y/kernel/v3.18.97-25-g185185965d8b/
Tree: stable-rc
Branch: linux-3.18.y
Git Describe: v3.18.97-25-g185185965d8b
Git Commit: 185185965d8b441876c21a1597393f77d1b5d9ae
Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 16 unique boards, 9 SoC families, 11 builds out of 167
---
For more info write to <[email protected]>
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.18.98 release. There are 24 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sun Mar 4 08:42:22 UTC 2018. Anything received after that time might be too late.
Build results:
total: 136 pass: 136 fail: 0 Qemu test results: total: 117 pass: 117 fail: 0
Details are available at http://kerneltests.org/builders.
Guenter
Quoted 8 lines · Greg Kroah-Hartman,
This is the start of the stable review cycle for the 3.18.98 release. There are 24 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sun Mar 4 08:42:22 UTC 2018. Anything received after that time might be too late.
Quoted 9 lines
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.98-rc1.gz
or in the git tree and branch at:git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-3.18.y
and the diffstat can be found below.
Builds and boots on the OnePlus 3T, no merge issues with CAF's msm-3.18 tree.
Quoted 1 line
Greg Kroah-Hartman
maintainerQuoted 21 lines · Harsh Shandilya
Quoted 8 lines · Greg Kroah-Hartman,
This is the start of the stable review cycle for the 3.18.98 release. There are 24 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sun Mar 4 08:42:22 UTC 2018. Anything received after that time might be too late.
Quoted 9 lines
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.98-rc1.gz
or in the git tree and branch at:git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-3.18.y
and the diffstat can be found below.
Quoted 2 lines
Builds and boots on the OnePlus 3T, no merge issues with CAF's msm-3.18 tree.
Great, thanks for testing and letting me know.
greg k-h
Quoted 1 line
Quoted 1 line
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.18.98 release. There are 24 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sun Mar 4 08:42:22 UTC 2018. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.18.98-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-3.18.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah