On Sat, Feb 27, 2021 at 08:21:55AM -0800, Linus Torvalds wrote:
> On Fri, Feb 26, 2021 at 10:00 PM Al Viro wrote:
> >
> > Al Viro (3):
> > 9p: fix misuse of sscanf() in v9fs_stat2inode()
>
> Hmm. Technically this changes some of the rules. It used to check that
> i tall fit in 32 bytes. Now
The pull request you sent on Sat, 27 Feb 2021 06:00:29 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5ceabb6078b80a8544ba86d6ee523ad755ae6d5e
Thank you!
--
Deet-doot-dot, I am a bot.
http
On Fri, Feb 26, 2021 at 10:00 PM Al Viro wrote:
>
> Al Viro (3):
> 9p: fix misuse of sscanf() in v9fs_stat2inode()
Hmm. Technically this changes some of the rules. It used to check that
i tall fit in 32 bytes. Now there could be arbitrary spaces in there
that pushes it over the limit.
I do
Assorted stuff pile - no common topic here.
One trivial conflict in Documentation/filesystems/porting.rst
The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)
are available in the git repository at:
git://git.kerne
The pull request you sent on Sun, 17 Jan 2021 03:21:15 +:
> 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/a527a2b32d20a2bd8070f49e98cb1a89b0c98bb3
Thank you!
--
Deet-doot-dot, I am a bot.
https://
Several assorted fixes. I still think that audit ->d_name race
is better fixed that way for the benefit of backports, with any fancier
variants done on top of that.
The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)
The pull request you sent on Thu, 24 Dec 2020 23:35:07 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7bb5226c8a4bbf26a9ededc90532b0ad539d2017
Thank you!
--
Deet-doot-dot, I am a bot.
http
Assorted patches from previous cycle(s)...
The following changes since commit b65054597872ce3aefbc6a666385eabdf9e288da:
Linux 5.10-rc6 (2020-11-29 15:50:50 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you to
The pull request you sent on Thu, 22 Oct 2020 07:01:28 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.set_fs
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f56e65dff6ad52395ef45738799b4fb70ff43376
Thank you!
--
Deet-doot-dot, I am a bot.
ht
Christoph's set_fs base series + fixups. A few trivial conflicts
(arch/{ia64,m68k/s390}/Kconfig and arch/x86/lib/getuser.S); proposed
resolution in #merge-candidate, same as in -next.
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16
The pull request you sent on Mon, 12 Oct 2020 04:17:22 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.iov_iter
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/85ed13e78dbedf9433115a62c85429922bc5035c
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Mon, 12 Oct 2020 04:19:53 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.quota-compat
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e18afa5bfa4a2f0e07b0864370485df701dacbc1
Thank you!
--
Deet-doot-dot, I am a b
The pull request you sent on Mon, 12 Oct 2020 04:27:48 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git compat.mount
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/22230cd2c55bd27ee2c3a3def97c0d5577a75b82
Thank you!
--
Deet-doot-dot, I am a bot.
h
The pull request you sent on Mon, 12 Oct 2020 04:14:55 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.csum_and_copy
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c90578360c92c71189308ebc71087197080e94c3
Thank you!
--
Deet-doot-dot, I am a
The last remnants of mount(2) compat buried. Buried into NFS, that is;
generally I'm less enthusiastic about "let's use in_compat_syscall() deep in
call chain" kind of approach than Christoph seems to be, but in this case it's
warranted - that crap had been an NFS-specific wart, hopefully
More Christoph's compat cleanups: quotactl(2).
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.quota-compat
Christoph's series around import_iovec() and compat variant thereof.
The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:
Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.
Saner calling conventions for csum_and_copy_..._user() and friends.
Sat in -next for two cycles now...
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the git repository at:
git://git.kernel.org/
The pull request you sent on Sun, 11 Oct 2020 19:06:09 +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/5b697f86f9f136d200c9827d6eca0437b7eb96cf
Thank you!
--
Deet-doot-dot, I am a bot.
https://
Sat in -next for a while, fixes an obvious bug
(leak introduced in 5.8, i.e. the mess from previous cycle).
The following changes since commit 933a3752babcf6513117d5773d2b70782d6ad149:
fuse: fix the ->direct_IO() treatment of iov_iter (2020-09-17 17:26:56 -0400)
are available in the gi
The pull request you sent on Wed, 3 Jun 2020 20:26:15 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.splice
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ae03c53d005ef8a1e0253ad67b7b62103ea1fae6
Thank you!
--
Deet-doot-dot, I am a bot.
htt
Christoph's assorted splice cleanups.
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.splice
for you to fet
The pull request you sent on Tue, 28 Apr 2020 22:18:55 +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/96c9a7802af7d500a582d89a8b864584fe878c1b
Thank you!
--
Deet-doot-dot, I am a bot.
https://
Two old bugs...
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
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 b0d3869ce9e
On Mon, Sep 16, 2019 at 6:35 PM Al Viro wrote:
>
> pathwalk-related stuff
That could have done with a few more words of explanation.
I added "Audit-related cleanups, misc simplifications, and easier to
follow nd->root refcounts"
Linus
The pull request you sent on Wed, 31 Jul 2019 19:53:27 +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/5c6207539aea8b22490f9569db5aa72ddfd0d486
Thank you!
--
Deet-doot-dot, I am a bot.
https://
Since nobody gave any specific objections and the thing
appears to work...
The following changes since commit 19a1c4092e7ca1ad1a72ac5535f902c483372cd5:
fix the struct mount leak in umount_tree() (2019-07-26 07:59:06 -0400)
are available in the git repository at:
git://git.kernel.org
The pull request you sent on Sat, 20 Jul 2019 04:02:18 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.dcache2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/18253e034d2aeee140f82fc9fe89c4bce5c81799
Thank you!
--
Deet-doot-dot, I am a bot.
h
Saner handling of refcounts to mountpoints.
Transfer the counting reference from struct mount ->mnt_mountpoint
over to struct mountpoint ->m_dentry. That allows to get rid of
the convoluted games with ordering of mount shutdowns. The cost
is in teaching shrink_dcache_{parent,for_umount} t
The pull request you sent on Fri, 19 Jul 2019 04:44:19 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.mount0
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/933a90bf4f3505f8ec83bda21a3c7d70d7c2b426
Thank you!
--
Deet-doot-dot, I am a bot.
ht
The pull request you sent on Fri, 19 Jul 2019 04:45:15 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.adfs
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d2fbf4b6d585e40f2369675148777abce3abd0e7
Thank you!
--
Deet-doot-dot, I am a bot.
http
The pull request you sent on Fri, 19 Jul 2019 04:46:04 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4f5ed1318c0108369a76f4a56242fbeea537abe9
Thank you!
--
Deet-doot-dot, I am a bot.
http
Assorted stuff.
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you to fetch changes up to 02e5ad9
More ADFS patches from rmk.
The following changes since commit d1fdb6d8f6a4109a4263176c84b899076a5f8008:
Linux 5.2-rc4 (2019-06-08 20:24:46 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.adfs
for you to fetch changes u
The first part of mount updates. It's messier than I'd like;
the branch itself merges with a couple of trivial conflicts, but there
are two filesystems that have grown the need of update while in
separate branches. I can do backmerges for those two (dmabuf and
vmballon), but fixups requir
The pull request you sent on Fri, 17 May 2019 04:11:26 +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/bf8a9a4755737f6630756f0d87bea9b38f0ed369
Thank you!
--
Deet-doot-dot, I am a bot.
https://
Propagation of new syscalls to other architectures + cosmetical
change from Christian (fscontext didn't follow the convention for anon
inode names).
What is _not_ included is cloexec changes - I really don't see
the benefits for the cloexec-by-default for new syscalls, when there's
The pull request you sent on Fri, 10 May 2019 03:33:33 +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/8ea5b2abd07e2280a332bd9c1a7f4dd15b9b6c13
Thank you!
--
Deet-doot-dot, I am a bot.
https://
Fix for umount -l/mount --move race caught by syzbot yesterday...
The following changes since commit 80f232121b69cc69a31ccb2b38c1665d770b0710:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next
(2019-05-07 22:03:58 -0700)
are available in the git repository at:
git:
The pull request you sent on Tue, 7 May 2019 21:49:21 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.mount-syscalls
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/400913252d09f9cfb8cce33daee43167921fc343
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Tue, 7 May 2019 21:53:19 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/149e703cb8bfcbdae46140b108bb6f7d2407df8f
Thank you!
--
Deet-doot-dot, I am a bot.
https
The pull request you sent on Tue, 7 May 2019 21:52:09 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.file
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d897166d8598e362a31d79dfd9a1e2eedb9ac85c
Thank you!
--
Deet-doot-dot, I am a bot.
https
The pull request you sent on Tue, 7 May 2019 21:33:55 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.dcache
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d27fb65bc2389621040e5107baedb94b4cccf641
Thank you!
--
Deet-doot-dot, I am a bot.
htt
Assorted stuff, with no common topic whatsoever...
The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:
Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for
A bit more of "this fget() would be better off as fdget()"
whack-a-mole + a couple of ->f_count-related cleanups
The following changes since commit 15ade5d2e7775667cf191cf2f94327a4889f8b9d:
Linux 5.1-rc4 (2019-04-07 14:09:59 -1000)
are available in the git repository at:
git
Syscalls themselves, finally. That's not all there is to that
stuff, but switching individual filesystems to new methods is
fortunately independent from everything else, so e.g. NFS series can
go through NFS tree, etc. As those conversions get done, we'll be
finally able to get rid of a b
Most of that pile is putting name length into struct name_snapshot
and making use of it. Beginning of that series ("ovl_lookup_real_one():
don't bother with strlen()") ought to have been split in two (separate
switch of name_snapshot to struct qstr from overlayfs reaping the trivial
benefi
The pull request you sent on Tue, 7 May 2019 01:50:37 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.icache
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/168e153d5ebbdd6a3fa85db1cc4879ed4b7030e0
Thank you!
--
Deet-doot-dot, I am a bot.
htt
The pull request you sent on Tue, 7 May 2019 01:58:42 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git stable-fodder
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/78438ce18f26dbcaa8993bb45d20ffb0cec3bc3e
Thank you!
--
Deet-doot-dot, I am a bot.
h
acct_on() fix for deadlock caught be overlayfs folks,
autofs RCU use-after-free SNAFU (->d_manage() can be called
lockless, so we need to RCU-delay freeing the objects it
looks at) and (hopefully) the end of "do we need freeing this
dentry RCU-delayed" whack-a-mole.
The following changes s
Introduction of separate method for RCU-delayed
part of ->destroy_inode() (if any). Pretty much as posted,
except that destroy_inode() stashes ->free_inode into the
victim (anon-unioned with ->i_fops) before scheduling
i_callback() and the last two patches (sockfs conversion
and folding st
The pull request you sent on Sun, 5 May 2019 03:18:46 +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/51987affd626b8e4ce9f4c65e1950cb9159f0f58
Thank you!
--
Deet-doot-dot, I am a bot.
https://k
A couple of ->i_link use-after-free fixes, regression fix for
wrong errno on absent device name in mount(2) (this cycle stuff) +
ancient UFS braino in large GID handling on Solaris UFS images (bogus
cut'n'paste from large UID handling; wrong field checked to decide
whether we should look at
The pull request you sent on Sun, 3 Mar 2019 03:42:53 +:
> 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/4f9020ffde71ddb92bc2f65ce0b00232bc88c590
Thank you!
--
Deet-doot-dot, I am a bot.
https://k
On Sat, Mar 2, 2019 at 7:43 PM Al Viro wrote:
>
> Assorted fixes that sat in -next for a while, all over the
> place.
Is this for the merge window or _very_ late fixes for 5.0?
One of the commits doesn't look appropriate for this (very late) stage
of the rc series: "cgroup: saner refcoun
Assorted fixes that sat in -next for a while, all over the
place.
The following changes since commit 1c7fc5cbc33980acd13d668f1c8f0313d6ae9fd8:
Linux 5.0-rc2 (2019-01-14 10:41:12 +1200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
The pull request you sent on Fri, 4 Jan 2019 19:26:48 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git mount.part1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/505b050fdf42097883b2d37b8e796e1f11dbef50
Thank you!
--
Deet-doot-dot, I am a bot.
htt
On Sat, Jan 05, 2019 at 01:31:21PM -0600, Eric W. Biederman wrote:
> Not having had a chance to review this code I can't really comment on
> the quality of this code. What I do know from a glance is that
> you have not removed FS_BINARY_MOUNTDATA. Which is the root cause
> of some of the crazy s
Al Viro writes:
> mount API prereqs. Mostly that's LSM mount options cleanups.
> One trivial conflict in security/selinux/hooks.c, resolved by taking
> the variant from this branch - the method has been split, leaving
> only the part that used to be conditional upon "it's not an internal
>
mount API prereqs. Mostly that's LSM mount options cleanups.
One trivial conflict in security/selinux/hooks.c, resolved by taking
the variant from this branch - the method has been split, leaving
only the part that used to be conditional upon "it's not an internal
mount" and check has been
The pull request you sent on Fri, 30 Nov 2018 05:15:22 +:
> 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/5f1ca5c619c2af5e03114b0276642cdc15d11a94
Thank you!
--
Deet-doot-dot, I am a bot.
https://
Assorted fixes all over the place; iov_iter one is this cycle regression
(splice from UDP triggering WARN_ON()), the rest is older.
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the git repository at:
I expected more fs/dcache.c cleanups this cycle, so that went into
a separate branch; said cleanups have missed the window, so in the
hindsight it could've gone into work.misc instead. Decided not
to cherry-pick, thus the separate pull request.
PS: That's the last pull request for today; the only
misc cleanups from various folks all over the place
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you t
Fix several places that screw up cleanups after failures halfway
through opening a file (one open-coding filp_clone_open() and getting
it wrong, two misusing alloc_file()). That part is -stable fodder from
#work.open.
And Christoph's regression fix for uapi breakage in aio series;
Assorted AFS stuff - ended up in vfs.git since most of that consists
of David's AFS-related followups to Christoph's procfs series.
The following changes since commit 96362fb474bad694812c18cbc9943fe0f7e2ce31:
isdn/gigaset: add back gigaset_procinfo assignment (2018-05-17 19:59:55 -0400)
Some biarch patches - getting rid of assorted compat_alloc_user_space()
(mis)uses. Not much in that area this cycle...
The following changes since commit 4faa99965e027cc057c5145ce45fa772caa04e8d:
fix io_destroy()/aio_complete() race (2018-05-23 22:53:22 -0400)
are available in the git
Assorted AIO followups and fixes.
The following changes since commit 9a6d9a62e0fd4b9927c3124db0f25fc6b4fb6576:
fs: aio ioprio use ioprio_check_cap ret val (2018-06-04 14:20:39 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git w
Regression fix for proc_fill_cache() braino introduced when
switching instantiate() callback to d_splice_alias().
[with apologies for being MIA for several days - flu started on Sunday and
got really nasty on Tuesday; back to normal now, hopefully]
The following changes since commit 888e2
The rest of aio stuff for this cycle - Adam's aio ioprio series
The following changes since commit 1da92779e2e8f309d5aecbbed346e7f812b174e8:
aio: sanitize the limit checking in io_submit(2) (2018-05-29 23:20:17 -0400)
are available in the git repository at:
git://git.kernel.org/pub/
Making lookup_one_len() safe with parent locked only shared
(incoming afs series wants that) + fix of getname_kernel() regression
from 2015 (-stable fodder, that one).
The following changes since commit 04bbc9795d2e89c79edf48fb1303ace2e8c90a60:
Merge branch 'old.dcache' into work.dcache
Backport-friendly part of lock_parent() race fix, a fix for assumption
in the heurisic used by path_connected() that is not true on NFS and livelock
fixes for d_alloc_parallel().
The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51:
Linux 4.16-rc2 (2018-02-18 17:2
On Wed, Jan 31, 2018 at 04:46:20AM +, Al Viro wrote:
> On Tue, Jan 30, 2018 at 07:19:19PM -0800, Linus Torvalds wrote:
> > On Tue, Jan 30, 2018 at 7:13 PM, Al Viro wrote:
> > >
> > > As for the place for mangle/demangle... where would you prefer them?
> >
> > If we can make gcc generate ok co
On Wed, Jan 31, 2018 at 04:46:20AM +, Al Viro wrote:
> MSG and REMOVE are never triggered, so it's all down to {WR{NORM,BAND},RDHUP}.
Actually, POLLREMOVE is an amusing story (FSVO amusing): it's a part of
UnixWare /dev/poll ABI. It had _not_ lasted in Linux - epoll_ctl()
EPOLL_CTL_DEL is us
On Tue, Jan 30, 2018 at 07:19:19PM -0800, Linus Torvalds wrote:
> On Tue, Jan 30, 2018 at 7:13 PM, Al Viro wrote:
> >
> > As for the place for mangle/demangle... where would you prefer them?
>
> If we can make gcc generate ok code for the generic case and not need
> any arch-specific ones, why no
On Tue, Jan 30, 2018 at 7:13 PM, Al Viro wrote:
>
> As for the place for mangle/demangle... where would you prefer them?
If we can make gcc generate ok code for the generic case and not need
any arch-specific ones, why not just do in ?
(And I guess POLLIN/OUT/ERR are standard, so it's only a cou
On Tue, Jan 30, 2018 at 06:21:37PM -0800, Linus Torvalds wrote:
> On Tue, Jan 30, 2018 at 10:39 AM, Al Viro wrote:
> > Introduces a __bitwise type for POLL... bitmap, propagates
> > the annotations through the tree.
>
> Ok, I'm not entirely happy with this.
>
> I don't think the mangle/d
On Tue, Jan 30, 2018 at 10:39 AM, Al Viro wrote:
> Introduces a __bitwise type for POLL... bitmap, propagates
> the annotations through the tree.
Ok, I'm not entirely happy with this.
I don't think the mangle/demangle_poll() stuff should be in the uapi
headers, and it really worries me t
Introduces a __bitwise type for POLL... bitmap, propagates
the annotations through the tree. Most of that stuff is as simple
as "make ->poll() instances return __poll_t and do the same to local
variables used to hold the future return value".
Some of the obvious brainos found in p
On Sat, Nov 18, 2017 at 09:45:31PM +, Al Viro wrote:
> in __get_user_pages_locked(), or am I missing something subtle there? Andrea?
You're not missing anything as far as the logic is concerned.
However see the __always_inline, I added "notify_drop" purely to
optimize away such branch at bui
On Fri, Nov 17, 2017 at 09:32:15PM +, Al Viro wrote:
[snip]
> drivers/infiniband/hw/mthca/mthca_memfree.c:475:ret =
> get_user_pages(uaddr & PAGE_MASK, 1, FOLL_WRITE, pages, NULL);
[snip]
> Itanic
> one is almost certainly buggered - we are not holding ->mmap_sem there.
So's the mth
On Fri, Nov 17, 2017 at 1:32 PM, Al Viro wrote:
> On Fri, Nov 17, 2017 at 12:50:47PM -0800, Linus Torvalds wrote:
>
>> Not because the conversion was wrong, but because the original code is
>> so broken.
>>
>> In particular, that "1" that is unchanged in the arguments is correct
>> in the conversi
On Fri, Nov 17, 2017 at 09:32:15PM +, Al Viro wrote:
> And for get_user_pages() itself it's even more ridiculous - vmalist (the last
> argument) is non-NULL in only one caller. Which uses it only to check if all
> of the VMAs happen to be hugetlb ones, apparently.
>
> FWIW, I wanted to trim
On Fri, Nov 17, 2017 at 12:50:47PM -0800, Linus Torvalds wrote:
> Not because the conversion was wrong, but because the original code is
> so broken.
>
> In particular, that "1" that is unchanged in the arguments is correct
> in the conversion, but it was completely wrong in the original, even
>
On Thu, Nov 16, 2017 at 7:02 PM, Al Viro wrote:
> A bunch of places switched to get_user_pages_fast().
I really would have liked a bit of a commentary.
Looking at the individual patches, I notice this, for example:
- down_read(¤t->mm->mmap_sem);
- page_nr = g
Nicolas Pitre cramfs work.
The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f:
Linux 4.14-rc4 (2017-10-08 20:53:29 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.cramfs
for you to fetch changes
Assorted stuff, really no common topic here.
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you
A bunch of places switched to get_user_pages_fast().
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
work.get_u
* bio_{map,copy}_user_iov() series; those are cleanups - fixes from
the same pile went into mainline (and stable) in late September.
* fs/iomap.c iov_iter-related fixes
* new primitive - iov_iter_for_each_range(); apply a function to
kernel-mapped segments of an iov_iter. U
{get,put}_compat_sigset() series + assorted compat ioctl stuff +
more set_fs() elimination + a few more timespec64 conversions + several
removals of pointless access_ok() in places where it was followed only by
non-__ variants of primitives.
One conflict (in drivers/staging/pi433);
MS_I_VERSION fixes - Mimi's fix + missing bits picked from
Matthew (his patch contained a duplicate of the fs/namespace.c fix
as well, but by that point the original fix had already been applied)
The following changes since commit 1cfd0ddd82232804e03f3023f6a58b50dfef0574:
bio_copy_user_
On Sun, Oct 15, 2017 at 2:58 AM, Pavel Machek wrote:
>
> up is quite short and not-specific for global symbol. Rename to mutex_up?
Well, it is quite the traditional name in the OS community and in
Linux it goes back to before the 1.0 release.
We've got about 450 each of the up() and the down() (
On Tue 2017-09-26 02:00:36, Al Viro wrote:
> On Mon, Sep 25, 2017 at 03:18:29PM -0700, Kyle Huey wrote:
> > Beginning with 553f770ef71b, the following program fails when compiled
> > for 32 bit and executed on a 64 bit kernel and succeeds when compiled
> > for and executed on a 64 bit. It continue
On Wed, 11 Oct 2017 00:54:57 -0400,
Al Viro wrote:
>
> Fairly old DIO bug caught by Andreas (3.10+) and several slightly
> younger blk_rq_map_user_iov() bugs, both on map and copy codepaths (Vitaly
> and me).
I ran work.iov_iter changeset through our smoke test few days ago - no apparent
s
On Wed, Oct 11, 2017 at 10:03 AM, Al Viro wrote:
>
> Can I assume your normal S-o-b on that? Just noticed that thing sitting
> in misc queue with mismatched Author: and Signed-off-by:...
Yup, just add my sign-off.
Thanks,
Linus
On Wed, Oct 11, 2017 at 06:03:35PM +0100, Al Viro wrote:
> On Mon, Sep 25, 2017 at 07:02:16PM -0700, Linus Torvalds wrote:
> > On Mon, Sep 25, 2017 at 6:46 PM, Al Viro wrote:
> > >
> > > Which tree do you prefer it to go through? Direct to mainline, or vfs.git
> > > #for-next?
> >
> > for-next,
On Mon, Sep 25, 2017 at 07:02:16PM -0700, Linus Torvalds wrote:
> On Mon, Sep 25, 2017 at 6:46 PM, Al Viro wrote:
> >
> > Which tree do you prefer it to go through? Direct to mainline, or vfs.git
> > #for-next?
>
> for-next, it's not like it's in any way urgent.
Can I assume your normal S-o-b o
Fairly old DIO bug caught by Andreas (3.10+) and several slightly
younger blk_rq_map_user_iov() bugs, both on map and copy codepaths (Vitaly
and me).
The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f:
Linux 4.14-rc4 (2017-10-08 20:53:29 -0700)
are available in
Christoph Hellwig writes:
> On Mon, Sep 25, 2017 at 06:37:28PM -0700, Linus Torvalds wrote:
>> Pulled and pushed out, but I'd like to note that sparse would have
>> caught this. Except we are so far away from being sparse-clean that
>> nobody runs it.
>
> I tend to run sparse over the nvme code b
On Mon, Sep 25, 2017 at 07:07:01PM -0700, Linus Torvalds wrote:
> On Mon, Sep 25, 2017 at 7:03 PM, Linus Torvalds
> wrote:
> >
> > I agree. It might be better to just remove the address space logic,
> > because afaik it never worked for them.
>
> .. and sadly, we should probably disable the locki
1 - 100 of 328 matches
Mail list logo
