Re: [git pull] a couple of fixes in vfs.git
The pull request you sent on Tue, 6 Apr 2021 17:15:11 +: > git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/2d743660786ec51f5c1fefd5782bbdee7b227db0 Thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/prtracker.html
[git pull] a couple of fixes in vfs.git
Fairly old hostfs bug (in setups that are not used by anyone, apparently) + fix for this cycle regression: extra dput/mntput in LOOKUP_CACHED failure handling. The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15: Linux 5.12-rc2 (2021-03-05 17:33:41 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes for you to fetch changes up to 7d01ef7585c07afaf487759a48486228cd065726: Make sure nd->path.mnt and nd->path.dentry are always valid pointers (2021-04-06 12:33:07 -0400) Al Viro (2): hostfs: fix memory handling in follow_link() Make sure nd->path.mnt and nd->path.dentry are always valid pointers fs/hostfs/hostfs_kern.c | 7 +++ fs/namei.c | 6 -- 2 files changed, 7 insertions(+), 6 deletions(-)
Re: [git pull] a couple of fixes for mount stuff
The pull request you sent on Mon, 17 Jun 2019 23:32:57 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/29f785ff76b65696800b75c3d8e0b58e603bb1d0 Thank you! -- Deet-doot-dot, I am a bot. https://korg.wiki.kernel.org/userdoc/prtracker
[git pull] a couple of fixes for mount stuff
MS_MOVE regression fix + breakage in fsmount(2) (also introduced in this cycle, along with fsmount(2) itself). I'm still digging through the piles of mail, so there might be more fixes to follow, but these two are obvious and self-contained, so there's no point delaying those... The following changes since commit 9e0babf2c06c73cda2c0cd37a1653d823adb40ec: Linux 5.2-rc5 (2019-06-16 08:49:45 -1000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes for you to fetch changes up to d728cf79164bb38e9628d15276e636539f857ef1: fs/namespace: fix unprivileged mount propagation (2019-06-17 17:36:09 -0400) Christian Brauner (1): fs/namespace: fix unprivileged mount propagation Eric Biggers (1): vfs: fsmount: add missing mntget() fs/namespace.c | 2 ++ fs/pnode.c | 1 - 2 files changed, 2 insertions(+), 1 deletion(-)
[git pull] a couple of fixes
The following changes since commit ce4bb04cae8924792ed92f4af2793b77fc986f0e: Fix a leak in socket(2) when we fail to allocate a file descriptor. (2018-01-10 18:47:05 -0500) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus for you to fetch changes up to cf5eebae2cd28d37581507668605f4d23cd7218d: seq_file: fix incomplete reset on read from zero offset (2018-01-20 02:31:15 -0500) Ivan Vecera (1): kernfs: fix regression in kernfs_fop_write caused by wrong type Miklos Szeredi (1): seq_file: fix incomplete reset on read from zero offset fs/kernfs/file.c | 2 +- fs/seq_file.c| 5 - 2 files changed, 5 insertions(+), 2 deletions(-)
[git pull] a couple of fixes
The following changes since commit ce4bb04cae8924792ed92f4af2793b77fc986f0e: Fix a leak in socket(2) when we fail to allocate a file descriptor. (2018-01-10 18:47:05 -0500) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus for you to fetch changes up to cf5eebae2cd28d37581507668605f4d23cd7218d: seq_file: fix incomplete reset on read from zero offset (2018-01-20 02:31:15 -0500) Ivan Vecera (1): kernfs: fix regression in kernfs_fop_write caused by wrong type Miklos Szeredi (1): seq_file: fix incomplete reset on read from zero offset fs/kernfs/file.c | 2 +- fs/seq_file.c| 5 - 2 files changed, 5 insertions(+), 2 deletions(-)
[git pull] a couple of fixes
Fix for my dumb braino in ncpfs and a long-standing breakage on recovery from failed rename() in jffs2. The following changes since commit a528aca7f359f4b0b1d72ae406097e491a5ba9ea: use ->d_seq to get coherency between ->d_inode and ->d_flags (2016-02-29 12:16:43 -0500) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus for you to fetch changes up to f93812846f31381d35c04c6c577d724254355e7f: jffs2: reduce the breakage on recovery from halfway failed rename() (2016-03-07 23:07:10 -0500) Al Viro (2): ncpfs: fix a braino in OOM handling in ncp_fill_cache() jffs2: reduce the breakage on recovery from halfway failed rename() fs/jffs2/dir.c | 11 --- fs/ncpfs/dir.c | 2 +- 2 files changed, 9 insertions(+), 4 deletions(-)
[git pull] a couple of fixes
Fix for my dumb braino in ncpfs and a long-standing breakage on recovery from failed rename() in jffs2. The following changes since commit a528aca7f359f4b0b1d72ae406097e491a5ba9ea: use ->d_seq to get coherency between ->d_inode and ->d_flags (2016-02-29 12:16:43 -0500) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus for you to fetch changes up to f93812846f31381d35c04c6c577d724254355e7f: jffs2: reduce the breakage on recovery from halfway failed rename() (2016-03-07 23:07:10 -0500) Al Viro (2): ncpfs: fix a braino in OOM handling in ncp_fill_cache() jffs2: reduce the breakage on recovery from halfway failed rename() fs/jffs2/dir.c | 11 --- fs/ncpfs/dir.c | 2 +- 2 files changed, 9 insertions(+), 4 deletions(-)
[git pull] a couple of fixes in vfs.git
A couple of fixes, both -stable fodder (9p one all way back to 2.6.32, dio - to all branches where "Fix negative return from dio read beyond eof" will end up it; it's a fixup to commit marked for -stable). Please, pull from the usual place - git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus Shortlog: Al Viro (2): 9p: ->evict_inode() should kick out ->i_data, not ->i_mapping fix the regression from "direct-io: Fix negative return from dio read beyond eof" Diffstat: fs/9p/vfs_inode.c | 4 ++-- fs/direct-io.c| 1 + 2 files changed, 3 insertions(+), 2 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[git pull] a couple of fixes in vfs.git
A couple of fixes, both -stable fodder (9p one all way back to 2.6.32, dio - to all branches where "Fix negative return from dio read beyond eof" will end up it; it's a fixup to commit marked for -stable). Please, pull from the usual place - git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus Shortlog: Al Viro (2): 9p: ->evict_inode() should kick out ->i_data, not ->i_mapping fix the regression from "direct-io: Fix negative return from dio read beyond eof" Diffstat: fs/9p/vfs_inode.c | 4 ++-- fs/direct-io.c| 1 + 2 files changed, 3 insertions(+), 2 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [GIT PULL] arm64: couple of fixes for -rc5
On Fri, Sep 12, 2014 at 7:39 AM, Will Deacon wrote: > > To keep things interesting, I've signed the tag using my Yubikey from KS. > Given that it only supports 2048-bit keys, I've used a new subkey so you > may need to update your keyring to verify the signature. BTW, thanks for mentioning things like this, that would have otherwise potentially made me waste time trying to figure out why your key wasn't in my keyring and didn't match the old one. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[GIT PULL] arm64: couple of fixes for -rc5
Hi Linus, Please can you pull these two arm64 fixes for -rc5? The IRQ migration fix turned up late last time and there's also a TLS leaking issue that we just fixed for arch/arm/ too. To keep things interesting, I've signed the tag using my Yubikey from KS. Given that it only supports 2048-bit keys, I've used a new subkey so you may need to update your keyring to verify the signature. Cheers, Will --->8 The following changes since commit 5e39977edf6500fd12f169e6c458d33b0ef62feb: Revert "arm64: cpuinfo: print info for all CPUs" (2014-09-01 15:55:22 +0100) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes for you to fetch changes up to eb35bdd7bca29a13c8ecd44e6fd747a84ce675db: arm64: flush TLS registers during exec (2014-09-11 18:34:58 +0100) arm64 fixes for -rc5 Just a couple of stragglers here: - Fix an issue migrating interrupts on CPU hotplug - Fix a potential information leak of TLS registers across an exec (Nathan has sent a corresponding patch for arch/arm/ to rmk) Sudeep Holla (1): arm64: use irq_set_affinity with force=false when migrating irqs Will Deacon (1): arm64: flush TLS registers during exec arch/arm64/kernel/irq.c| 12 arch/arm64/kernel/process.c| 18 ++ arch/arm64/kernel/sys_compat.c | 6 ++ 3 files changed, 28 insertions(+), 8 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[GIT PULL] arm64: couple of fixes for -rc5
Hi Linus, Please can you pull these two arm64 fixes for -rc5? The IRQ migration fix turned up late last time and there's also a TLS leaking issue that we just fixed for arch/arm/ too. To keep things interesting, I've signed the tag using my Yubikey from KS. Given that it only supports 2048-bit keys, I've used a new subkey so you may need to update your keyring to verify the signature. Cheers, Will ---8 The following changes since commit 5e39977edf6500fd12f169e6c458d33b0ef62feb: Revert arm64: cpuinfo: print info for all CPUs (2014-09-01 15:55:22 +0100) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes for you to fetch changes up to eb35bdd7bca29a13c8ecd44e6fd747a84ce675db: arm64: flush TLS registers during exec (2014-09-11 18:34:58 +0100) arm64 fixes for -rc5 Just a couple of stragglers here: - Fix an issue migrating interrupts on CPU hotplug - Fix a potential information leak of TLS registers across an exec (Nathan has sent a corresponding patch for arch/arm/ to rmk) Sudeep Holla (1): arm64: use irq_set_affinity with force=false when migrating irqs Will Deacon (1): arm64: flush TLS registers during exec arch/arm64/kernel/irq.c| 12 arch/arm64/kernel/process.c| 18 ++ arch/arm64/kernel/sys_compat.c | 6 ++ 3 files changed, 28 insertions(+), 8 deletions(-) -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [GIT PULL] arm64: couple of fixes for -rc5
On Fri, Sep 12, 2014 at 7:39 AM, Will Deacon will.dea...@arm.com wrote: To keep things interesting, I've signed the tag using my Yubikey from KS. Given that it only supports 2048-bit keys, I've used a new subkey so you may need to update your keyring to verify the signature. BTW, thanks for mentioning things like this, that would have otherwise potentially made me waste time trying to figure out why your key wasn't in my keyring and didn't match the old one. Linus -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [git pull] a couple of fixes for rc7
On Fri, Oct 25, 2013 at 03:33:46PM +0100, Linus Torvalds wrote: > On Fri, Oct 25, 2013 at 3:25 PM, Al Viro wrote: > > nfsd performance regression fix + seq_file lseek(2) fix. > > Please, pull from the usual place - > > git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus > > Not acceptable. > > fs/file_table.c: In function ???fput???: > fs/file_table.c:320:4: warning: passing argument 1 of > ???schedule_delayed_work??? from incompatible pointer type [enabled by > default] > schedule_delayed_work(_fput_work, 1); > ^ > In file included from include/linux/srcu.h:34:0, > from include/linux/notifier.h:15, > from include/linux/memory_hotplug.h:6, > from include/linux/mmzone.h:797, > from include/linux/gfp.h:4, > from include/linux/slab.h:14, > from fs/file_table.c:9: > include/linux/workqueue.h:594:60: note: expected ???struct delayed_work > *??? but argument is of type ???struct work_struct *??? > static inline bool schedule_delayed_work(struct delayed_work *dwork, > > Plase stop sending me untested crap that doesn't even compile cleanly! Oh, hell... git cherry-pick (for the wrong place, at that) instead of just pushing the bugger as it was - it sat on top of previous vfs.git#for-linus. Mea culpa ;-/ I've pushed the right branch now; should propagate in a few minutes. Head should be at 05e16745c. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [git pull] a couple of fixes for rc7
On Fri, Oct 25, 2013 at 3:25 PM, Al Viro wrote: > nfsd performance regression fix + seq_file lseek(2) fix. > Please, pull from the usual place - > git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus Not acceptable. fs/file_table.c: In function ‘fput’: fs/file_table.c:320:4: warning: passing argument 1 of ‘schedule_delayed_work’ from incompatible pointer type [enabled by default] schedule_delayed_work(_fput_work, 1); ^ In file included from include/linux/srcu.h:34:0, from include/linux/notifier.h:15, from include/linux/memory_hotplug.h:6, from include/linux/mmzone.h:797, from include/linux/gfp.h:4, from include/linux/slab.h:14, from fs/file_table.c:9: include/linux/workqueue.h:594:60: note: expected ‘struct delayed_work *’ but argument is of type ‘struct work_struct *’ static inline bool schedule_delayed_work(struct delayed_work *dwork, Plase stop sending me untested crap that doesn't even compile cleanly! Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[git pull] a couple of fixes for rc7
nfsd performance regression fix + seq_file lseek(2) fix. Please, pull from the usual place - git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus Shortlog: Al Viro (1): nfsd regression since delayed fput() Gu Zheng (1): seq_file: always update file->f_pos in seq_lseek() Diffstat: fs/file_table.c |2 +- fs/seq_file.c |2 ++ 2 files changed, 3 insertions(+), 1 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[git pull] a couple of fixes for rc7
nfsd performance regression fix + seq_file lseek(2) fix. Please, pull from the usual place - git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus Shortlog: Al Viro (1): nfsd regression since delayed fput() Gu Zheng (1): seq_file: always update file-f_pos in seq_lseek() Diffstat: fs/file_table.c |2 +- fs/seq_file.c |2 ++ 2 files changed, 3 insertions(+), 1 deletions(-) -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [git pull] a couple of fixes for rc7
On Fri, Oct 25, 2013 at 3:25 PM, Al Viro v...@zeniv.linux.org.uk wrote: nfsd performance regression fix + seq_file lseek(2) fix. Please, pull from the usual place - git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus Not acceptable. fs/file_table.c: In function ‘fput’: fs/file_table.c:320:4: warning: passing argument 1 of ‘schedule_delayed_work’ from incompatible pointer type [enabled by default] schedule_delayed_work(delayed_fput_work, 1); ^ In file included from include/linux/srcu.h:34:0, from include/linux/notifier.h:15, from include/linux/memory_hotplug.h:6, from include/linux/mmzone.h:797, from include/linux/gfp.h:4, from include/linux/slab.h:14, from fs/file_table.c:9: include/linux/workqueue.h:594:60: note: expected ‘struct delayed_work *’ but argument is of type ‘struct work_struct *’ static inline bool schedule_delayed_work(struct delayed_work *dwork, Plase stop sending me untested crap that doesn't even compile cleanly! Linus -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [git pull] a couple of fixes for rc7
On Fri, Oct 25, 2013 at 03:33:46PM +0100, Linus Torvalds wrote: On Fri, Oct 25, 2013 at 3:25 PM, Al Viro v...@zeniv.linux.org.uk wrote: nfsd performance regression fix + seq_file lseek(2) fix. Please, pull from the usual place - git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus Not acceptable. fs/file_table.c: In function ???fput???: fs/file_table.c:320:4: warning: passing argument 1 of ???schedule_delayed_work??? from incompatible pointer type [enabled by default] schedule_delayed_work(delayed_fput_work, 1); ^ In file included from include/linux/srcu.h:34:0, from include/linux/notifier.h:15, from include/linux/memory_hotplug.h:6, from include/linux/mmzone.h:797, from include/linux/gfp.h:4, from include/linux/slab.h:14, from fs/file_table.c:9: include/linux/workqueue.h:594:60: note: expected ???struct delayed_work *??? but argument is of type ???struct work_struct *??? static inline bool schedule_delayed_work(struct delayed_work *dwork, Plase stop sending me untested crap that doesn't even compile cleanly! Oh, hell... git cherry-pick (for the wrong place, at that) instead of just pushing the bugger as it was - it sat on top of previous vfs.git#for-linus. Mea culpa ;-/ I've pushed the right branch now; should propagate in a few minutes. Head should be at 05e16745c. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
