net: fec: set GPR bit on suspend by DT configuration.
Subsystems (8)
Sasha Levin
maintainerPATCH 7/18 scsi: target: fix PR IN / READ FULL STATUS for FC
In reply to Sasha LevinFrom: Bodo Stroesser <[email protected]>
[ Upstream commit 8fed04eb79a74cbf471dfaa755900a51b37273ab ]
Creation of the response to READ FULL STATUS fails for FC based reservations. Reason is the too high loop limit (< 24) in fc_get_pr_transport_id(). The string representation of FC WWPN is 23 chars long only ("11:22:33:44:55:66:77:88"). So when i is 23, the loop body is executed a last time for the ending '\0' of the string and thus hex2bin() reports an error.
--- drivers/target/target_core_fabric_lib.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/target/target_core_fabric_lib.c +1 -1
@@ -76,7 +76,7 @@ static int fc_get_pr_transport_id(* encoded TransportID. */ ptr = &se_nacl->initiatorname[0 ]; -for (i =0 ; i <24 ; ) { +for (i =0 ; i <23 ; ) {if (!strncmp (&ptr[i],":" ,1 )) { i++;continue ;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 8/18 scsi: target: tcmu: reset_ring should reset TCMU_DEV_BIT_BROKEN
In reply to Sasha LevinFrom: Bodo Stroesser <[email protected]>
[ Upstream commit 066f79a5fd6d1b9a5cc57b5cd445b3e4bb68a5b2 ]
In case command ring buffer becomes inconsistent, tcmu sets device flag TCMU_DEV_BIT_BROKEN. If the bit is set, tcmu rejects new commands from LIO core with TCM_LOGICAL_UNIT_COMMUNICATION_FAILURE, and no longer processes completions from the ring. The reset_ring attribute can be used to completely clean up the command ring, so after reset_ring the ring no longer is inconsistent.
Therefore reset_ring also should reset bit TCMU_DEV_BIT_BROKEN to allow normal processing.
--- drivers/target/target_core_user.c | 1 + 1 file changed, 1 insertion(+)
drivers/target/target_core_user.c +1 -0
@@ -2067,6 +2067,7 @@ static void tcmu_reset_ring(struct tcmu_dev *udev, u8 err_level) mb->cmd_tail =0 ; mb->cmd_head =0 ;tcmu_flush_dcache_range (mb,sizeof (*mb)); +clear_bit (TCMU_DEV_BIT_BROKEN , &udev->flags);del_timer (&udev->cmd_timer);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 4/18 xfs: fix partially uninitialized structure in xfs_reflink_remap_extent
In reply to Sasha LevinFrom: "Darrick J. Wong" <[email protected]>
[ Upstream commit c142932c29e533ee892f87b44d8abc5719edceec ]
In the reflink extent remap function, it turns out that uirec (the block mapping corresponding only to the part of the passed-in mapping that got unmapped) was not fully initialized. Specifically, br_state was not being copied from the passed-in struct to the uirec. This could lead to unpredictable results such as the reflinked mapping being marked unwritten in the destination file.
--- fs/xfs/xfs_reflink.c | 1 + 1 file changed, 1 insertion(+)
fs/xfs/xfs_reflink.c +1 -0
@@ -1058,6 +1058,7 @@ xfs_reflink_remap_extent( uirec.br_startblock = irec->br_startblock + rlen; uirec.br_startoff = irec->br_startoff + rlen; uirec.br_blockcount = unmap_len - rlen; + uirec.br_state = irec->br_state; unmap_len = rlen;/* If this isn't a real mapping, we're done. */
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 10/18 objtool: Support Clang non-section symbols in ORC dump
In reply to Sasha LevinFrom: Josh Poimboeuf <[email protected]>
[ Upstream commit 8782e7cab51b6bf01a5a86471dd82228af1ac185 ]
Historically, the relocation symbols for ORC entries have only been section symbols:
.text+0: sp:sp+8 bp:(und) type:call end:0
However, the Clang assembler is aggressive about stripping section symbols. In that case we will need to use function symbols:
freezing_slow_path+0: sp:sp+8 bp:(und) type:call end:0
In preparation for the generation of such entries in "objtool orc generate", add support for reading them in "objtool orc dump".
--- tools/objtool/orc_dump.c | 44 ++++++++++++++++++++++++---------------- 1 file changed, 27 insertions(+), 17 deletions(-)
tools/objtool/orc_dump.c +27 -17
@@ -78,7 +78,7 @@ int orc_dump(const char *_objname)char *name;size_t nr_sections;Elf64_Addr orc_ip_addr =0 ; -size_t shstrtab_idx; +size_t shstrtab_idx, strtab_idx =0 ;Elf *elf;Elf_Scn *scn;GElf_Shdr sh;
@@ -139,6 +139,8 @@ int orc_dump(const char *_objname)if (!strcmp (name,".symtab" )) { symtab = data; + }else if (!strcmp (name,".strtab" )) { + strtab_idx = i; }else if (!strcmp (name,".orc_unwind" )) { orc = data->d_buf; orc_size = sh.sh_size;
@@ -150,7 +152,7 @@ int orc_dump(const char *_objname) } } -if (!symtab || !orc || !orc_ip) +if (!symtab || !strtab_idx || !orc || !orc_ip)return 0 ;if (orc_size %sizeof (*orc) !=0 ) {
@@ -171,21 +173,29 @@ int orc_dump(const char *_objname)return -1 ; } - scn =elf_getscn (elf, sym.st_shndx); -if (!scn) { -WARN_ELF ("elf_getscn" ); -return -1 ; - } - -if (!gelf_getshdr (scn, &sh)) { -WARN_ELF ("gelf_getshdr" ); -return -1 ; - } - - name =elf_strptr (elf, shstrtab_idx, sh.sh_name); -if (!name || !*name) { -WARN_ELF ("elf_strptr" ); -return -1 ; +if (GELF_ST_TYPE (sym.st_info) ==STT_SECTION ) { + scn =elf_getscn (elf, sym.st_shndx); +if (!scn) { +WARN_ELF ("elf_getscn" ); +return -1 ; + } + +if (!gelf_getshdr (scn, &sh)) { +WARN_ELF ("gelf_getshdr" ); +return -1 ; + } + + name =elf_strptr (elf, shstrtab_idx, sh.sh_name); +if (!name) { +WARN_ELF ("elf_strptr" ); +return -1 ; + } + }else { + name =elf_strptr (elf, strtab_idx, sym.st_name); +if (!name) { +WARN_ELF ("elf_strptr" ); +return -1 ; + } }printf ("%s+%llx:" , name, (unsigned long long )rela.r_addend);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 12/18 ALSA: hda: call runtime_allow() for all hda controllers
In reply to Sasha LevinFrom: Hui Wang <[email protected]>
[ Upstream commit 9a6418487b566503c772cb6e7d3d44e652b019b0 ]
Before the pci_driver->probe() is called, the pci subsystem calls runtime_forbid() and runtime_get_sync() on this pci dev, so only call runtime_put_autosuspend() is not enough to enable the runtime_pm on this device.
For controllers with vgaswitcheroo feature, the pci/quirks.c will call runtime_allow() for this dev, then the controllers could enter rt_idle/suspend/resume, but for non-vgaswitcheroo controllers like Intel hda controllers, the runtime_pm is not enabled because the runtime_allow() is not called.
Since it is no harm calling runtime_allow() twice, here let hda driver call runtime_allow() for all controllers. Then the runtime_pm is enabled on all controllers after the put_autosuspend() is called.
--- sound/pci/hda/hda_intel.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/hda_intel.c +1 -0
@@ -2478,6 +2478,7 @@ static int azx_probe_continue(struct azx *chip)if (azx_has_pm_runtime (chip)) {pm_runtime_use_autosuspend (&pci->dev); +pm_runtime_allow (&pci->dev);pm_runtime_put_autosuspend (&pci->dev); }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 13/18 net/cxgb4: Check the return from t4_query_params properly
In reply to Sasha LevinFrom: Jason Gunthorpe <[email protected]>
[ Upstream commit c799fca8baf18d1bbbbad6c3b736eefbde8bdb90 ]
Positive return values are also failures that don't set val, although this probably can't happen. Fixes gcc 10 warning:
drivers/net/ethernet/chelsio/cxgb4/t4_hw.c: In function ‘t4_phy_fw_ver’:drivers/net/ethernet/chelsio/cxgb4/t4_hw.c:3747:14: warning: ‘val’ may be used uninitialized in this function [-Wmaybe-uninitialized]
3747 | *phy_fw_ver = val;
--- drivers/net/ethernet/chelsio/cxgb4/t4_hw.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/chelsio/cxgb4/t4_hw.c +1 -1
@@ -3748,7 +3748,7 @@ int t4_phy_fw_ver(struct adapter *adap, int *phy_fw_ver) FW_PARAMS_PARAM_Z_V(FW_PARAMS_PARAM_DEV_PHYFW_VERSION)); ret =t4_query_params (adap, adap->mbox, adap->pf,0 ,1 , ¶m, &val); -if (ret <0 ) +if (ret)return ret; *phy_fw_ver = val;return 0 ;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 15/18 ext4: use matching invalidatepage in ext4_writepage
In reply to Sasha LevinFrom: yangerkun <[email protected]>
[ Upstream commit c2a559bc0e7ed5a715ad6b947025b33cb7c05ea7 ]
Run generic/388 with journal data mode sometimes may trigger the warning in ext4_invalidatepage. Actually, we should use the matching invalidatepage in ext4_writepage.
--- fs/ext4/inode.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ext4/inode.c +1 -1
@@ -2128,7 +2128,7 @@ static int ext4_writepage(struct page *page,bool keep_towrite = false;if (unlikely (ext4_forced_shutdown (EXT4_SB (inode->i_sb)))) { -ext4_invalidatepage (page,0 ,PAGE_SIZE ); + inode->i_mapping->a_ops->invalidatepage (page,0 ,PAGE_SIZE );unlock_page (page);return -EIO ; }
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 17/18 ext4: convert BUG_ON's to WARN_ON's in mballoc.c
In reply to Sasha LevinFrom: Theodore Ts'o <[email protected]>
[ Upstream commit 907ea529fc4c3296701d2bfc8b831dd2a8121a34 ]
If the in-core buddy bitmap gets corrupted (or out of sync with the block bitmap), issue a WARN_ON and try to recover. In most cases this involves skipping trying to allocate out of a particular block group. We can end up declaring the file system corrupted, which is fair, since the file system probably should be checked before we proceed any further.
Google-Bug-Id: 34811296
Google-Bug-Id: 34639169
--- fs/ext4/mballoc.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
fs/ext4/mballoc.c +4 -2
@@ -1936,7 +1936,8 @@ void ext4_mb_complex_scan_group(struct ext4_allocation_context *ac,int free; free = e4b->bd_info->bb_free; -BUG_ON (free <=0 ); +if (WARN_ON (free <=0 )) +return ; i = e4b->bd_info->bb_first_free;
@@ -1959,7 +1960,8 @@ void ext4_mb_complex_scan_group(struct ext4_allocation_context *ac, }mb_find_extent (e4b, i, ac->ac_g_ex.fe_len, &ex); -BUG_ON (ex.fe_len <=0 ); +if (WARN_ON (ex.fe_len <=0 )) +break ;if (free < ex.fe_len) {ext4_grp_locked_error (sb, e4b->bd_group,0 ,0 , "%d free clusters as per "
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 11/18 xen/xenbus: ensure xenbus_map_ring_valloc() returns proper grant status
In reply to Sasha LevinFrom: Juergen Gross <[email protected]>
[ Upstream commit 6b51fd3f65a22e3d1471b18a1d56247e246edd46 ]
xenbus_map_ring_valloc() maps a ring page and returns the status of the used grant (0 meaning success).
There are Xen hypervisors which might return the value 1 for the status of a failed grant mapping due to a bug. Some callers of xenbus_map_ring_valloc() test for errors by testing the returned status to be less than zero, resulting in no error detected and crashing later due to a not available ring page.
Set the return value of xenbus_map_ring_valloc() to GNTST_general_error in case the grant status reported by Xen is greater than zero.
This is part of XSA-316.
--- drivers/xen/xenbus/xenbus_client.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
drivers/xen/xenbus/xenbus_client.c +8 -1
@@ -450,7 +450,14 @@ EXPORT_SYMBOL_GPL(xenbus_free_evtchn);int xenbus_map_ring_valloc (struct xenbus_device *dev,grant_ref_t *gnt_refs,unsigned int nr_grefs,void **vaddr) { -return ring_ops->map (dev, gnt_refs, nr_grefs, vaddr); +int err; + + err = ring_ops->map (dev, gnt_refs, nr_grefs, vaddr); +/* Some hypervisors are buggy and can return 1. */ +if (err >0 ) + err = GNTST_general_error; + +return err; }EXPORT_SYMBOL_GPL (xenbus_map_ring_valloc);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 14/18 arm64: Delete the space separator in __emit_inst
In reply to Sasha LevinFrom: Fangrui Song <[email protected]>
[ Upstream commit c9a4ef66450145a356a626c833d3d7b1668b3ded ]
In assembly, many instances of __emit_inst(x) expand to a directive. In a few places __emit_inst(x) is used as an assembler macro argument. For example, in arch/arm64/kvm/hyp/entry.S
ALTERNATIVE(nop, SET_PSTATE_PAN(1), ARM64_HAS_PAN, CONFIG_ARM64_PAN)
expands to the following by the C preprocessor:
alternative_insn nop, .inst (0xd500401f | ((0) << 16 | (4) << 5) | ((!!1) << 8)), 4, 1
Both comma and space are separators, with an exception that content inside a pair of parentheses/quotes is not split, so the clang integrated assembler splits the arguments to:
nop, .inst, (0xd500401f | ((0) << 16 | (4) << 5) | ((!!1) << 8)), 4, 1
GNU as preprocesses the input with do_scrub_chars(). Its arm64 backend (along with many other non-x86 backends) sees:
alternative_insn nop,.inst(0xd500401f|((0)<<16|(4)<<5)|((!!1)<<8)),4,1 # .inst(...) is parsed as one argument
while its x86 backend sees:
alternative_insn nop,.inst (0xd500401f|((0)<<16|(4)<<5)|((!!1)<<8)),4,1 # The extra space before '(' makes the whole .inst (...) parsed as two arguments
The non-x86 backend's behavior is considered unintentional
(https://sourceware.org/bugzilla/show_bug.cgi?id=25750).
So drop the space separator inside .inst (...) to make the clang integrated assembler work.
--- arch/arm64/include/asm/sysreg.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
arch/arm64/include/asm/sysreg.h +3 -1
@@ -60,7 +60,9 @@#ifndef CONFIG_BROKEN_GAS_INST #ifdef __ASSEMBLY__ -#define __emit_inst (x) .inst (x) +// The space separator is omitted so that __emit_inst(x) can be parsed as +// either an assembler directive or an assembler macro argument. +#define __emit_inst (x) .inst(x)#else #define __emit_inst (x) ".inst " __stringify((x)) "\n\t"#endif
Signature · 7 lines
2.20.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Sasha Levin
maintainerPATCH 18/18 hwmon: (jc42) Fix name to have no illegal characters
In reply to Sasha LevinFrom: Sascha Hauer <[email protected]>
[ Upstream commit c843b382e61b5f28a3d917712c69a344f632387c ]
The jc42 driver passes I2C client's name as hwmon device name. In case of device tree probed devices this ends up being part of the compatible string, "jc-42.4-temp". This name contains hyphens and the hwmon core doesn't like this:
jc42 2-0018: hwmon: 'jc-42.4-temp' is not a valid name attribute, please fix
This changes the name to "jc42" which doesn't have any illegal characters.
--- drivers/hwmon/jc42.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hwmon/jc42.c +1 -1
@@ -527,7 +527,7 @@ static int jc42_probe(struct i2c_client *client, const struct i2c_device_id *id) } data->config = config; - hwmon_dev =devm_hwmon_device_register_with_info (dev, client->name, + hwmon_dev =devm_hwmon_device_register_with_info (dev,"jc42" , data, &jc42_chip_info,NULL );return PTR_ERR_OR_ZERO (hwmon_dev);
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 9/18 objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings
In reply to Sasha LevinFrom: Josh Poimboeuf <[email protected]>
[ Upstream commit bd841d6154f5f41f8a32d3c1b0bc229e326e640a ]
CONFIG_UBSAN_TRAP causes GCC to emit a UD2 whenever it encounters an unreachable code path. This includes __builtin_unreachable(). Because the BUG() macro uses __builtin_unreachable() after it emits its own UD2, this results in a double UD2. In this case objtool rightfully detects that the second UD2 is unreachable:
init/main.o: warning: objtool: repair_env_string()+0x1c8: unreachable instruction
We weren't able to figure out a way to get rid of the double UD2s, so just silence the warning.
--- tools/objtool/check.c | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-)
tools/objtool/check.c +15 -2
@@ -2086,14 +2086,27 @@ static bool ignore_unreachable_insn(struct instruction *insn) !strcmp(insn->sec->name, ".altinstr_aux"))return true; +if (!insn->func) +return false; + +/* +* CONFIG_UBSAN_TRAP inserts a UD2 when it sees +* __builtin_unreachable(). The BUG() macro has an unreachable() after +* the UD2, which causes GCC's undefined trap logic to emit another UD2 +* (or occasionally a JMP to UD2). +*/ +if (list_prev_entry (insn, list)->dead_end && + (insn->type ==INSN_BUG || + (insn->type ==INSN_JUMP_UNCONDITIONAL && + insn->jump_dest && insn->jump_dest->type ==INSN_BUG ))) +return true; +/* * Check if this (or a subsequent) instruction is related to * CONFIG_UBSAN or CONFIG_KASAN. * * End the search at 5 instructions to avoid going into the weeds. */ -if (!insn->func) -return false;for (i =0 ; i <5 ; i++) {if (is_kasan_insn (insn) ||is_ubsan_insn (insn))
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 16/18 ext4: increase wait time needed before reuse of deleted inode numbers
In reply to Sasha LevinFrom: Theodore Ts'o <[email protected]>
[ Upstream commit a17a9d935dc4a50acefaf319d58030f1da7f115a ]
Current wait times have proven to be too short to protect against inode reuses that lead to metadata inconsistencies.
Now that we will retry the inode allocation if we can't find any recently deleted inodes, it's a lot safer to increase the recently deleted time from 5 seconds to a minute.
Google-Bug-Id: 36602237
--- fs/ext4/ialloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ext4/ialloc.c +1 -1
@@ -665,7 +665,7 @@ static int find_group_other(struct super_block *sb, struct inode *parent,* block has been written back to disk. (Yes, these values are * somewhat arbitrary...) */ -#define RECENTCY_MIN 5 +#define RECENTCY_MIN 60#define RECENTCY_DIRTY 300static int recently_deleted (struct super_block *sb,ext4_group_t group,int ino)
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 5/18 ALSA: hda: Keep the controller initialization even if no codecs found
In reply to Sasha LevinFrom: Takashi Iwai <[email protected]>
[ Upstream commit 9479e75fca370a5220784f7596bf598c4dad0b9b ]
Currently, when the HD-audio controller driver doesn't detect any codecs, it tries to abort the probe. But this abort happens at the delayed probe, i.e. the primary probe call already returned success, hence the driver is never unbound until user does so explicitly. As a result, it may leave the HD-audio device in the running state without the runtime PM. More badly, if the device is a HD-audio bus that is tied with a GPU, GPU cannot reach to the full power down and consumes unnecessarily much power.
This patch changes the logic after no-codec situation; it continues probing without the further codec initialization but keep the controller driver running normally.
--- sound/pci/hda/hda_intel.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-)
sound/pci/hda/hda_intel.c +7 -5
@@ -2054,7 +2054,7 @@ static int azx_first_init(struct azx *chip)/* codec detection */ if (!azx_bus (chip)->codec_mask) {dev_err (card->dev,"no codecs found!\n" ); -return -ENODEV ; +/* keep running the rest for the runtime PM */ }if (azx_acquire_irq (chip,0 ) <0 )
@@ -2441,9 +2441,11 @@ static int azx_probe_continue(struct azx *chip)#endif /* create codec instances */ - err =azx_probe_codecs (chip, azx_max_codecs[chip->driver_type]); -if (err <0 ) - goto out_free; +if (bus->codec_mask) { + err =azx_probe_codecs (chip, azx_max_codecs[chip->driver_type]); +if (err <0 ) + goto out_free; + }#ifdef CONFIG_SND_HDA_PATCH_LOADER if (chip->fw) {
@@ -2457,7 +2459,7 @@ static int azx_probe_continue(struct azx *chip) #endif }#endif -if ((probe_only[dev] &1 ) ==0 ) { +if (bus->codec_mask && !(probe_only[dev] &1 )) { err =azx_codec_configure (chip);if (err <0 ) goto out_free;
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 6/18 ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported
In reply to Sasha LevinFrom: Roy Spliet <[email protected]>
[ Upstream commit 3ba21113bd33d49f3c300a23fc08cf114c434995 ]
This fixes runtime PM not working after a suspend-to-RAM cycle at least for the codec-less HDA device found on NVIDIA GPUs.
--- sound/pci/hda/hda_intel.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
sound/pci/hda/hda_intel.c +3 -1
@@ -2476,8 +2476,10 @@ static int azx_probe_continue(struct azx *chip)set_default_power_save (chip); -if (azx_has_pm_runtime (chip)) +if (azx_has_pm_runtime (chip)) { +pm_runtime_use_autosuspend (&pci->dev);pm_runtime_put_autosuspend (&pci->dev); + } out_free: if ((chip->driver_caps & AZX_DCAPS_I915_POWERWELL)
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 3/18 xfs: acquire superblock freeze protection on eofblocks scans
In reply to Sasha LevinFrom: Brian Foster <[email protected]>
[ Upstream commit 4b674b9ac852937af1f8c62f730c325fb6eadcdb ]
The filesystem freeze sequence in XFS waits on any background eofblocks or cowblocks scans to complete before the filesystem is quiesced. At this point, the freezer has already stopped the transaction subsystem, however, which means a truncate or cowblock cancellation in progress is likely blocked in transaction allocation. This results in a deadlock between freeze and the associated scanner.
Fix this problem by holding superblock write protection across calls into the block reapers. Since protection for background scans is acquired from the workqueue task context, trylock to avoid a similar deadlock between freeze and blocking on the write lock.
--- fs/xfs/xfs_icache.c | 10 ++++++++++ fs/xfs/xfs_ioctl.c | 5 ++++- 2 files changed, 14 insertions(+), 1 deletion(-)
fs/xfs/xfs_icache.c +10 -0
@@ -902,7 +902,12 @@ xfs_eofblocks_worker( {struct xfs_mount *mp =container_of (to_delayed_work (work), struct xfs_mount, m_eofblocks_work); + +if (!sb_start_write_trylock (mp->m_super)) +return ;xfs_icache_free_eofblocks (mp,NULL ); +sb_end_write (mp->m_super); +xfs_queue_eofblocks (mp); }
@@ -929,7 +934,12 @@ xfs_cowblocks_worker( {struct xfs_mount *mp =container_of (to_delayed_work (work), struct xfs_mount, m_cowblocks_work); + +if (!sb_start_write_trylock (mp->m_super)) +return ;xfs_icache_free_cowblocks (mp,NULL ); +sb_end_write (mp->m_super); +xfs_queue_cowblocks (mp); }
fs/xfs/xfs_ioctl.c +4 -1
@@ -2182,7 +2182,10 @@ xfs_file_ioctl(if (error)return error; -return xfs_icache_free_eofblocks (mp, &keofb); +sb_start_write (mp->m_super); + error =xfs_icache_free_eofblocks (mp, &keofb); +sb_end_write (mp->m_super); +return error; }default :
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 2/18 x86: hyperv: report value of misc_features
In reply to Sasha LevinFrom: Olaf Hering <[email protected]>
[ Upstream commit 97d9f1c43bedd400301d6f1eff54d46e8c636e47 ]
A few kernel features depend on ms_hyperv.misc_features, but unlike its siblings ->features and ->hints, the value was never reported during boot.
--- arch/x86/kernel/cpu/mshyperv.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/x86/kernel/cpu/mshyperv.c +2 -2
@@ -214,8 +214,8 @@ static void __init ms_hyperv_init_platform(void) ms_hyperv.misc_features =cpuid_edx (HYPERV_CPUID_FEATURES ); ms_hyperv.hints =cpuid_eax (HYPERV_CPUID_ENLIGHTMENT_INFO ); -pr_info ("Hyper-V: features 0x%x, hints 0x%x\n" , - ms_hyperv.features, ms_hyperv.hints); +pr_info ("Hyper-V: features 0x%x, hints 0x%x, misc 0x%x\n" , + ms_hyperv.features, ms_hyperv.hints, ms_hyperv.misc_features); ms_hyperv.max_vp_index =cpuid_eax (HYPERV_CPUID_IMPLEMENT_LIMITS ); ms_hyperv.max_lp_index =cpuid_ebx (HYPERV_CPUID_IMPLEMENT_LIMITS );
Signature · 1 line
2.20.1
Sasha Levin
maintainerPATCH 1/18 net: fec: set GPR bit on suspend by DT configuration.
From: Martin Fuzzey <[email protected]>
[ Upstream commit da722186f6549d752ea5b5fbc18111833c81a133 ]
On some SoCs, such as the i.MX6, it is necessary to set a bit in the SoC level GPR register before suspending for wake on lan to work.
The fec platform callback sleep_mode_enable was intended to allow this but the platform implementation was NAK'd back in 2015 [1]
This means that, currently, wake on lan is broken on mainline for the i.MX6 at least.
So implement the required bit setting in the fec driver by itself by adding a new optional DT property indicating the GPR register and adding the offset and bit information to the driver.
[1] https://www.spinics.net/lists/netdev/msg310922.html
--- drivers/net/ethernet/freescale/fec.h | 7 + drivers/net/ethernet/freescale/fec_main.c | 149 +++++++++++++++++----- 2 files changed, 127 insertions(+), 29 deletions(-)
drivers/net/ethernet/freescale/fec.h +7 -0
@@ -488,6 +488,12 @@ struct fec_enet_priv_rx_q {struct sk_buff *rx_skbuff[RX_RING_SIZE ]; }; +struct fec_stop_mode_gpr { +struct regmap *gpr; +u8 reg; +u8 bit; +}; +/* The FEC buffer descriptors track the ring buffers. The rx_bd_base and * tx_bd_base always point to the base of the buffer descriptors. The * cur_rx and cur_tx point to the currently available buffer.
@@ -563,6 +569,7 @@ struct fec_enet_private {int hwts_tx_en;struct delayed_work time_keep;struct regulator *reg_phy; +struct fec_stop_mode_gpr stop_gpr;unsigned int tx_align;unsigned int rx_align;
drivers/net/ethernet/freescale/fec_main.c +120 -29
237 lines not on this page · raw message
Signature · 1 line
2.20.1