* [git pull] vfs fixes
[not found] ` <CAHk-=whn5qk-e-KnYr6HNe5hp45v+XyDbsA2+szXvK3gC06A2w@mail.gmail.com>
@ 2020-01-15 6:41 ` Al Viro
2020-01-15 19:35 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2020-01-15 6:41 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
Fixes for mountpoint_last() bugs (by converting to use of lookup_last()) +
autofs regression fix from this cycle (caused by follow_managed() breakage
introduced in barrier fixes series).
The following changes since commit 1edc8eb2e93130e36ac74ac9c80913815a57d413:
fs: call fsnotify_sb_delete after evict_inodes (2019-12-18 00:03:01 -0500)
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 508c8772760d4ef9c1a044519b564710c3684fc5:
fix autofs regression caused by follow_managed() changes (2020-01-15 01:36:46 -0500)
----------------------------------------------------------------
Al Viro (2):
reimplement path_mountpoint() with less magic
fix autofs regression caused by follow_managed() changes
fs/namei.c | 90 ++++++++-------------------------------------------
fs/nfs/nfstrace.h | 2 --
include/linux/namei.h | 1 -
3 files changed, 13 insertions(+), 80 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread
* [GIT PULL] vfs fixes
@ 2025-08-19 12:46 Christian Brauner
2025-08-19 17:33 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-08-19 12:46 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few fixes for this cycle:
- Fix two memory leaks in pidfs.
- Prevent changing the idmapping of an already idmapped mount without
OPEN_TREE_CLONE through open_tree_attr().
- Don't fail listing extended attributes in kernfs when no extended
attributes are set.
- Fix the return value in coredump_parse().
- Fix the error handling for unbuffered writes in netfs.
- Fix broken data integrity guarantees for O_SYNC writes via iomap.
- Fix UAF in __mark_inode_dirty().
- Keep inode->i_blkbits constant in fuse.
- Fix coredump selftests.
- Fix get_unused_fd_flags() usage in do_handle_open().
- Rename EXPORT_SYMBOL_GPL_FOR_MODULES to EXPORT_SYMBOL_FOR_MODULES.
- Fix use-after-free in bh_read().
- Fix incorrect lflags value in the move_mount() syscall.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.17-rc3.fixes
for you to fetch changes up to a2c1f82618b0b65f1ef615aa9cfdac8122537d69:
signal: Fix memory leak for PIDFD_SELF* sentinels (2025-08-19 13:51:28 +0200)
Please consider pulling these changes from the signed vfs-6.17-rc3.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.17-rc3.fixes
----------------------------------------------------------------
Adrian Huang (Lenovo) (2):
pidfs: Fix memory leak in pidfd_info()
signal: Fix memory leak for PIDFD_SELF* sentinels
Aleksa Sarai (2):
open_tree_attr: do not allow id-mapping changes without OPEN_TREE_CLONE
selftests/mount_setattr: add smoke tests for open_tree_attr(2) bug
Christian Brauner (2):
Merge patch series "open_tree_attr: do not allow id-mapping changes without OPEN_TREE_CLONE"
kernfs: don't fail listing extended attributes
Dan Carpenter (1):
coredump: Fix return value in coredump_parse()
David Howells (1):
netfs: Fix unbuffered write error handling
Jan Kara (1):
iomap: Fix broken data integrity guarantees for O_SYNC writes
Jiufei Xue (1):
fs: writeback: fix use-after-free in __mark_inode_dirty()
Joanne Koong (1):
fuse: keep inode->i_blkbits constant
Nam Cao (1):
selftests/coredump: Remove the read() that fails the test
Thomas Bertschinger (1):
fhandle: do_handle_open() should get FD with user flags
Vlastimil Babka (1):
module: Rename EXPORT_SYMBOL_GPL_FOR_MODULES to EXPORT_SYMBOL_FOR_MODULES
Ye Bin (1):
fs/buffer: fix use-after-free when call bh_read() helper
Yuntao Wang (1):
fs: fix incorrect lflags value in the move_mount syscall
Documentation/core-api/symbol-namespaces.rst | 11 ++--
drivers/tty/serial/8250/8250_rsa.c | 8 +--
fs/anon_inodes.c | 2 +-
fs/buffer.c | 2 +-
fs/coredump.c | 2 +-
fs/fhandle.c | 2 +-
fs/fs-writeback.c | 9 +--
fs/fuse/inode.c | 5 --
fs/iomap/direct-io.c | 14 ++--
fs/kernfs/inode.c | 4 +-
fs/namespace.c | 35 ++++++----
fs/netfs/read_collect.c | 4 +-
fs/netfs/write_collect.c | 10 ++-
fs/netfs/write_issue.c | 4 +-
fs/pidfs.c | 2 +-
fs/splice.c | 3 +
include/linux/export.h | 2 +-
include/linux/netfs.h | 1 +
kernel/signal.c | 6 +-
tools/testing/selftests/coredump/stackdump_test.c | 3 -
.../selftests/mount_setattr/mount_setattr_test.c | 77 ++++++++++++++++++----
21 files changed, 138 insertions(+), 68 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-07-25 8:54 Christian Brauner
2025-07-25 15:39 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-07-25 8:54 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains two last-minute fixes for this cycle:
- Set afs vllist to NULL if addr parsing fails.
- Add a missing check for reaching the end of the string in afs.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 89be9a83ccf1f88522317ce02f854f30d6115c41:
Linux 6.16-rc7 (2025-07-20 15:18:33 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.16-rc8.fixes
for you to fetch changes up to 8b3c655fa2406b9853138142746a39b7615c54a2:
afs: Set vllist to NULL if addr parsing fails (2025-07-23 13:54:34 +0200)
Please consider pulling these changes from the signed vfs-6.16-rc8.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.16-rc8.fixes
----------------------------------------------------------------
Edward Adam Davis (1):
afs: Set vllist to NULL if addr parsing fails
Leo Stone (1):
afs: Fix check for NULL terminator
fs/afs/addr_prefs.c | 2 +-
fs/afs/cell.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-07-19 10:59 Christian Brauner
2025-07-19 18:29 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-07-19 10:59 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few fixes for this cycle:
- Fix a memory leak in fcntl_dirnotify().
- Raise SB_I_NOEXEC on secrement superblock instead of messing with
flags on the mount.
- Add fsdevel and block mailing lists to uio entry. We had a few
instances were very questionable stuff was added without either block
or the VFS being aware of it.
- Fix netfs copy-to-cache so that it performs collection with ceph+fscache.
- Fix netfs race between cache write completion and ALL_QUEUED being set.
- Verify the inode mode when loading entries from disk in isofs.
- Avoid state_lock in iomap_set_range_uptodate().
- Fix PIDFD_INFO_COREDUMP check in PIDFD_GET_INFO ioctl.
- Fix the incorrect return value in __cachefiles_write().
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit d7b8f8e20813f0179d8ef519541a3527e7661d3a:
Linux 6.16-rc5 (2025-07-06 14:10:26 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.16-rc7.fixes
for you to fetch changes up to a88cddaaa3bf7445357a79a5c351c6b6d6f95b7d:
MAINTAINERS: add block and fsdevel lists to iov_iter (2025-07-16 14:46:53 +0200)
Please consider pulling these changes from the signed vfs-6.16-rc7.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.16-rc7.fixes
----------------------------------------------------------------
Al Viro (1):
fix a leak in fcntl_dirnotify()
Christian Brauner (3):
secretmem: use SB_I_NOEXEC
Merge patch series "netfs: Fix use of fscache with ceph"
MAINTAINERS: add block and fsdevel lists to iov_iter
David Howells (2):
netfs: Fix copy-to-cache so that it performs collection with ceph+fscache
netfs: Fix race between cache write completion and ALL_QUEUED being set
Jan Kara (1):
isofs: Verify inode mode when loading from disk
Jinliang Zheng (1):
iomap: avoid unnecessary ifs_set_range_uptodate() with locks
Laura Brehm (1):
coredump: fix PIDFD_INFO_COREDUMP ioctl check
Zizhi Wo (1):
cachefiles: Fix the incorrect return value in __cachefiles_write()
MAINTAINERS | 2 ++
fs/cachefiles/io.c | 2 --
fs/cachefiles/ondemand.c | 4 +---
fs/iomap/buffered-io.c | 3 +++
fs/isofs/inode.c | 9 ++++++++-
fs/netfs/read_pgpriv2.c | 5 +++++
fs/notify/dnotify/dnotify.c | 8 ++++----
fs/pidfs.c | 2 +-
include/trace/events/netfs.h | 30 ++++++++++++++++++++++++++++++
mm/secretmem.c | 13 +++++++++----
10 files changed, 63 insertions(+), 15 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-07-04 8:36 Christian Brauner
2025-07-04 17:36 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-07-04 8:36 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
This includes a fix for a priority inversion in eventpoll. I did
consider it a fix and it is a single commit but it is a bit more code
than we would usually let through after -rc2. If you want me to delay
that until the merge window that's perfectly fine. You can either just
revert right after merging this or I can send you a new pull request
tomorrow.
/* Summary */
This contains another round of fixes for this cycle:
- Fix a regression caused by the anonymous inode rework. Making them
regular files causes various places in the kernel to tip over starting
with io_uring. Revert to the former status quo and port our assertion
to be based on checking the inode so we don't lose the valuable
VFS_*_ON_*() assertions that have already helped discover weird
behavior our outright bugs.
- Fix the the upper bound calculation in fuse_fill_write_pages().
- Fix priority inversion issues in the eventpoll code.
- Make secretmen use anon_inode_make_secure_inode() to avoid bypassing
the LSM layer.
- Fix a netfs hang due to missing case in final DIO read result
collection.
- Fix a double put of the netfs_io_request struct.
- Provide some helpers to abstract out NETFS_RREQ_IN_PROGRESS flag
wrangling.
- Fix infinite looping in netfs_wait_for_pause/request().
- Fix a netfs ref leak on an extra subrequest inserted into a request's
list of subreqs.
- Fix various cifs RPC callbacks to set NETFS_SREQ_NEED_RETRY if a
subrequest fails retriably.
- Fix a cifs warning in the workqueue code when reconnecting a channel.
- Fix the updating of i_size in netfs to avoid a race between testing if
we should have extended the file with a DIO write and changing i_size.
- Merge the places in netfs that update i_size on write.
- Fix coredump socket selftests.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit e04c78d86a9699d136910cfc0bdcf01087e3267e:
Linux 6.16-rc2 (2025-06-15 13:49:41 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.16-rc5.fixes
for you to fetch changes up to 1e7ab6f67824343ee3e96f100f0937c393749a8a:
anon_inode: rework assertions (2025-07-02 14:41:39 +0200)
Please consider pulling these changes from the signed vfs-6.16-rc5.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.16-rc5.fixes
----------------------------------------------------------------
Christian Brauner (2):
Merge patch series "netfs, cifs: Fixes to retry-related code"
anon_inode: rework assertions
David Howells (9):
netfs: Fix hang due to missing case in final DIO read result collection
netfs: Fix double put of request
netfs: Provide helpers to perform NETFS_RREQ_IN_PROGRESS flag wangling
netfs: Fix looping in wait functions
netfs: Fix ref leak on inserted extra subreq in write retry
netfs: Fix i_size updating
netfs: Merge i_size update functions
netfs: Renumber the NETFS_RREQ_* flags to make traces easier to read
netfs: Update tracepoints in a number of ways
Joanne Koong (1):
fuse: fix fuse_fill_write_pages() upper bound calculation
Nam Cao (2):
selftests/coredump: Fix "socket_detect_userspace_client" test failure
eventpoll: Fix priority inversion problem
Paulo Alcantara (3):
smb: client: set missing retry flag in smb2_writev_callback()
smb: client: set missing retry flag in cifs_readv_callback()
smb: client: set missing retry flag in cifs_writev_callback()
Shivank Garg (1):
fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass
fs/anon_inodes.c | 23 +-
fs/eventpoll.c | 458 +++++++---------------
fs/exec.c | 9 +-
fs/fuse/file.c | 5 +-
fs/libfs.c | 8 +-
fs/namei.c | 2 +-
fs/netfs/buffered_write.c | 38 +-
fs/netfs/direct_write.c | 16 -
fs/netfs/internal.h | 26 +-
fs/netfs/main.c | 6 +-
fs/netfs/misc.c | 50 ++-
fs/netfs/read_collect.c | 16 +-
fs/netfs/write_collect.c | 14 +-
fs/netfs/write_retry.c | 3 +-
fs/smb/client/cifssmb.c | 22 ++
fs/smb/client/smb2pdu.c | 27 +-
include/linux/fs.h | 2 +
include/linux/netfs.h | 21 +-
include/trace/events/netfs.h | 29 +-
mm/secretmem.c | 9 +-
tools/testing/selftests/coredump/stackdump_test.c | 5 +
21 files changed, 351 insertions(+), 438 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-06-16 8:20 Christian Brauner
2025-06-16 16:12 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-06-16 8:20 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains another round of fixes for this cycle:
- Fix a regression in overlayfs caused by reworking the lookup_one*()
set of helpers.
- Make sure that the name of the dentry is printed in
overlayfs' mkdir() helper.
- Add missing iocb values to TRACE_IOCB_STRINGS define.
- Unlock the superblock during iterate_supers_type().
This was an accidental internal api change.
- Drop a misleading assert in file_seek_cur_needs_f_lock() helper.
- Never refuse to return PIDFD_GET_INGO when parent pid is zero.
That can trivially happen in container scenarios where the parent
process might be located in an ancestor pid namespace.
- Don't revalidate in try_lookup_noperm() as that causes regression for
filesystems such as cifs.
- Fix simple_xattr_list() and reset the err variable after
security_inode_listsecurity() got called so as not to confuse
userspace about the length of the xattr.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 5abc7438f1e9d62e91ad775cc83c9594c48d2282:
Merge tag 'nfs-for-6.16-1' of git://git.linux-nfs.org/projects/anna/linux-nfs (2025-06-03 16:13:32 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.16-rc3.fixes
for you to fetch changes up to dd2d6b7f6f519d078a866a36a625b0297d81c5bc:
fs: drop assert in file_seek_cur_needs_f_lock (2025-06-16 09:59:24 +0200)
Please consider pulling these changes from the signed vfs-6.16-rc3.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.16-rc3.fixes
----------------------------------------------------------------
Amir Goldstein (2):
ovl: fix regression caused by lookup helpers API changes
ovl: fix debug print in case of mkdir error
Christoph Hellwig (1):
fs: add missing values to TRACE_IOCB_STRINGS
Darrick J. Wong (1):
fs: unlock the superblock during iterate_supers_type
Luis Henriques (1):
fs: drop assert in file_seek_cur_needs_f_lock
Mike Yuan (1):
pidfs: never refuse ppid == 0 in PIDFD_GET_INFO
NeilBrown (1):
VFS: change try_lookup_noperm() to skip revalidation
Stephen Smalley (1):
fs/xattr.c: fix simple_xattr_list()
fs/file.c | 8 ++++++--
fs/namei.c | 17 +++++++++++++----
fs/overlayfs/namei.c | 10 ++++++++--
fs/overlayfs/overlayfs.h | 8 +++++---
fs/pidfs.c | 2 +-
fs/super.c | 4 +++-
fs/xattr.c | 1 +
include/linux/fs.h | 4 +++-
8 files changed, 40 insertions(+), 14 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-06-02 9:02 Christian Brauner
2025-06-02 22:58 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-06-02 9:02 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a first round of fixes for this cycle:
- Fix the AT_HANDLE_CONNECTABLE option so filesystems that don't know
how to decode a connected non-dir dentry fail the request.
- Use repr(transparent) to ensure identical layout between the C and
Rust implementation of struct file.
- Add a missing xas_pause() into the dax code employing
wait_entry_unlocked_exclusive().
- Fix FOP_DONTCACHE which we disabled for v6.15. A folio could get
redirtied and/or scheduled for writeback after the initial dropbehind
test. Change the test accordingly to handle these cases so we can
re-enable FOP_DONTCACHE again.
This obviously will need backports to v6.15.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 015a99fa76650e7d6efa3e36f20c0f5b346fe9ce:
Merge tag 'nolibc-20250526-for-6.16-1' of git://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc (2025-05-27 11:27:09 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.16-rc2.fixes
for you to fetch changes up to 5402c4d4d2000a9baa30c1157c97152ec6383733:
exportfs: require ->fh_to_parent() to encode connectable file handles (2025-05-30 07:30:47 +0200)
Please consider pulling these changes from the signed vfs-6.16-rc2.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.16-rc2.fixes
----------------------------------------------------------------
Alistair Popple (1):
fs/dax: Fix "don't skip locked entries when scanning entries"
Amir Goldstein (1):
exportfs: require ->fh_to_parent() to encode connectable file handles
Christian Brauner (2):
Merge patch series "dropbehind fixes and cleanups"
Merge patch series "rust: file: mark `LocalFile` as `repr(transparent)`"
Jens Axboe (6):
mm/filemap: gate dropbehind invalidate on folio !dirty && !writeback
mm/filemap: use filemap_end_dropbehind() for read invalidation
Revert "Disable FOP_DONTCACHE for now due to bugs"
mm/filemap: unify read/write dropbehind naming
mm/filemap: unify dropbehind flag testing and clearing
iomap: don't lose folio dropbehind state for overwrites
Pekka Ristola (2):
rust: file: mark `LocalFile` as `repr(transparent)`
rust: file: improve safety comments
fs/dax.c | 2 +-
fs/iomap/buffered-io.c | 2 ++
fs/xfs/xfs_aops.c | 22 ++++++++++++++++++++--
include/linux/exportfs.h | 10 ++++++++++
include/linux/fs.h | 2 +-
include/linux/iomap.h | 5 ++++-
mm/filemap.c | 39 ++++++++++++++++++++++++---------------
rust/kernel/fs/file.rs | 10 ++++++----
8 files changed, 68 insertions(+), 24 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-05-23 10:26 Christian Brauner
2025-05-23 14:56 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-05-23 10:26 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a small set of fixes for the blocking buffer lookup
conversion done earlier this cycle. It adds a missing conversion in the
getblk slowpath and a few minor optimizations and cleanups.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit a5806cd506af5a7c19bcd596e4708b5c464bfd21:
Linux 6.15-rc7 (2025-05-18 13:57:29 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.15-rc8.fixes
for you to fetch changes up to 7e69dd62bcda256709895e82e1bb77511e2f844b:
Merge patch series "fs/buffer: misc optimizations" (2025-05-21 09:34:31 +0200)
Please consider pulling these changes from the signed vfs-6.15-rc8.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.15-rc8.fixes
----------------------------------------------------------------
Christian Brauner (1):
Merge patch series "fs/buffer: misc optimizations"
Davidlohr Bueso (4):
fs/buffer: use sleeping lookup in __getblk_slowpath()
fs/buffer: avoid redundant lookup in getblk slowpath
fs/buffer: remove superfluous statements
fs/buffer: optimize discard_buffer()
fs/buffer.c | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-05-12 11:01 Christian Brauner
2025-05-13 3:33 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-05-12 11:01 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains various fixes for this cycle:
* Ensure that simple_xattr_list() always includes security.* xattrs.
* Fix eventpoll busy loop optimization when combined with timeouts.
* Disable swapon() for devices with block sizes greater than page sizes.
* Done call errseq_set() twice during mark_buffer_write_io_error(). Just use
mapping_set_error() which takes care to not deference unconditionally.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit b4432656b36e5cc1d50a1f2dc15357543add530e:
Linux 6.15-rc4 (2025-04-27 15:19:23 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.15-rc7.fixes
for you to fetch changes up to 04679f3c27e132c1a2d3881de2f0c5d7128de7c1:
fs: Remove redundant errseq_set call in mark_buffer_write_io_error. (2025-05-09 12:31:57 +0200)
Please consider pulling these changes from the signed vfs-6.15-rc7.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.15-rc7.fixes
----------------------------------------------------------------
Jeremy Bongio (1):
fs: Remove redundant errseq_set call in mark_buffer_write_io_error.
Luis Chamberlain (1):
swapfile: disable swapon for bs > ps devices
Max Kellermann (1):
fs/eventpoll: fix endless busy loop after timeout has expired
Stephen Smalley (1):
fs/xattr.c: fix simple_xattr_list to always include security.* xattrs
fs/buffer.c | 4 +---
fs/eventpoll.c | 7 ++++---
fs/xattr.c | 24 ++++++++++++++++++++++++
mm/swapfile.c | 9 +++++++++
4 files changed, 38 insertions(+), 6 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-04-25 21:22 Christian Brauner
2025-04-25 23:35 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-04-25 21:22 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains various fixes for this cycle:
- For some reason we went from zero to three maintainers for HFS/HFS+ in
a matter of days. The lesson to learn from this might just be that we
need to threaten code removal more often!?
- Fix a regression introduced by enabling large folios for lage logical
block sizes. This has caused issues for noref migration with large
folios due to sleeping while in an atomic context.
New sleeping variants of pagecache lookup helpers are introduced.
These helpers take the folio lock instead of the mapping's private
spinlock. The problematic users are converted to the sleeping variants
and serialize against noref migration. Atomic users will bail on
seeing the new BH_Migrate flag.
This also shrinks the critical region of the mapping's private lock
and the new blocking callers reduce contention on the spinlock for
bdev mappings.
- Fix two bugs in do_move_mount() when with MOVE_MOUNT_BENEATH.
The first bug is using a mountpoint that is located on a mount we're
not holding a reference to. The second bug is putting the mountpoint
after we've called namespace_unlock() as it's no longer guaranteed
that it does stay a mountpoint.
- Remove a pointless call to vfs_getattr_nosec() in the devtmpfs code
just to query i_mode instead of simply querying the inode directly.
This also avoids lifetime issues for the dm code by an earlier bugfix
this cycle that moved bdev_statx() handling into vfs_getattr_nosec().
- Fix AT_FDCWD handling with getname_maybe_null() in the xattr code.
- Fix a performance regression for files when multiple callers issue a
close when it's not the last reference.
- Remove a duplicate noinline annotation from pipe_clear_nowait().
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit a33b5a08cbbdd7aadff95f40cbb45ab86841679e:
Merge tag 'sched_ext-for-6.15-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext (2025-04-21 19:16:29 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.15-rc4.fixes
for you to fetch changes up to f520bed25d17bb31c2d2d72b0a785b593a4e3179:
fs/xattr: Fix handling of AT_FDCWD in setxattrat(2) and getxattrat(2) (2025-04-25 12:11:56 +0200)
Please consider pulling these changes from the signed vfs-6.15-rc4.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.15-rc4.fixes
----------------------------------------------------------------
Al Viro (1):
fix a couple of races in MNT_TREE_BENEATH handling by do_move_mount()
Christian Brauner (1):
Merge patch series "fs/buffer: split pagecache lookups into atomic or blocking"
Christoph Hellwig (1):
devtmpfs: don't use vfs_getattr_nosec to query i_mode
Davidlohr Bueso (7):
fs/buffer: split locking for pagecache lookups
fs/buffer: introduce sleeping flavors for pagecache lookups
fs/buffer: use sleeping version of __find_get_block()
fs/ocfs2: use sleeping version of __find_get_block()
fs/jbd2: use sleeping version of __find_get_block()
fs/ext4: use sleeping version of sb_find_get_block()
mm/migrate: fix sleep in atomic for large folios and buffer heads
Jan Kara (1):
fs/xattr: Fix handling of AT_FDCWD in setxattrat(2) and getxattrat(2)
Mateusz Guzik (1):
fs: fall back to file_ref_put() for non-last reference
T.J. Mercier (1):
splice: remove duplicate noinline from pipe_clear_nowait
Viacheslav Dubeyko (1):
MAINTAINERS: add HFS/HFS+ maintainers
Yangtao Li (1):
MAINTAINERS: hfs/hfsplus: add myself as maintainer
MAINTAINERS | 10 +++++--
drivers/base/devtmpfs.c | 22 ++++++--------
fs/buffer.c | 73 +++++++++++++++++++++++++++++++++------------
fs/ext4/ialloc.c | 3 +-
fs/ext4/mballoc.c | 3 +-
fs/file.c | 2 +-
fs/jbd2/revoke.c | 15 ++++++----
fs/namespace.c | 69 ++++++++++++++++++++++--------------------
fs/ocfs2/journal.c | 2 +-
fs/splice.c | 2 +-
fs/xattr.c | 4 +--
include/linux/buffer_head.h | 9 ++++++
include/linux/file_ref.h | 19 ++++--------
mm/migrate.c | 8 +++--
14 files changed, 145 insertions(+), 96 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-04-19 21:04 Christian Brauner
2025-04-19 21:38 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-04-19 21:04 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains various fixes for this cycle:
* Revert the hfs{plus} deprecation warning that's also included in this
pull request. The commit introducing the deprecation warning resides
rather early in this branch. So simply dropping it would've rebased
all other commits which I decided to avoid. Hence the revert in the
same branch.
* Switch CONFIG_SYSFS_SYCALL default to n and decouple from CONFIG_EXPERT.
* Fix an audit bug caused by changes to our kernel path lookup
helpers this cycle. Audit needs the parent path even if the dentry it
tried to look up is negative.
* Ensure that the kernel path lookup helpers leave the passed in path
argument clean when they return an error. This is consistent with all
our other helpers.
* Ensure that vfs_getattr_nosec() calls bdev_statx() so the relevant
information is available to kernel consumers as well.
* Don't set a timer and call schedule() if the timer will expire
immediately in epoll.
* Make netfs lookup tables with __nonstring.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 834a4a689699090a406d1662b03affa8b155d025:
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma (2025-04-14 10:24:04 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.15-rc3.fixes.2
for you to fetch changes up to 408e4504f97c0aa510330f0a04b7ed028fdf3154:
Revert "hfs{plus}: add deprecation warning" (2025-04-19 22:48:59 +0200)
Please consider pulling these changes from the signed vfs-6.15-rc3.fixes.2 tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.15-rc3.fixes.2
----------------------------------------------------------------
Christian Brauner (5):
Kconfig: switch CONFIG_SYSFS_SYCALL default to n
hfs{plus}: add deprecation warning
fs: add kern_path_locked_negative()
fs: ensure that *path_locked*() helpers leave passed path pristine
Revert "hfs{plus}: add deprecation warning"
Christoph Hellwig (1):
fs: move the bdex_statx call to vfs_getattr_nosec
Joe Damato (1):
eventpoll: Set epoll timeout if it's in the future
Kees Cook (1):
netfs: Mark __nonstring lookup tables
block/bdev.c | 3 +-
fs/eventpoll.c | 10 +++++-
fs/namei.c | 81 +++++++++++++++++++++++++++++++++--------------
fs/netfs/fscache_cache.c | 2 +-
fs/netfs/fscache_cookie.c | 2 +-
fs/stat.c | 32 +++++++++++--------
include/linux/blkdev.h | 6 ++--
include/linux/namei.h | 1 +
init/Kconfig | 20 ++++++------
kernel/audit_watch.c | 16 ++++++----
10 files changed, 112 insertions(+), 61 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-04-14 10:44 Christian Brauner
2025-04-14 17:41 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-04-14 10:44 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains various fixes for this cycle:
* Fix NULL pointer dereference in virtiofs.
* Fix slab OOB access in hfs/hfsplus.
* Only create /proc/fs/netfs when CONFIG_PROC_FS is set.
* Fix getname_flags() to initialize pointer correctly.
* Convert dentry flags to enum.
* Don't allow datadir without lowerdir in overlayfs.
* Use namespace_{lock,unlock} helpers in dissolve_on_fput() instead of
plain namespace_sem so unmounted mounts are properly cleaned up.
* Skip unnecessary ifs_block_is_uptodate check in iomap.
* Remove an unused forward declaration in overlayfs.
* Fix devpts uid/gid handling after converting to the new mount api.
* Fix afs_dynroot_readdir() to not use the RCU read lock.
* Fix mount_setattr() and open_tree_attr() to not pointlessly do path
lookup or walk the mount tree if no mount option change has been
requested.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.15-rc3.fixes
for you to fetch changes up to e2aef868a8c39f411eb7bcee3c42e165a21d5cd6:
Merge tag 'ovl-fixes-6.15-rc2' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs (2025-04-11 16:41:48 +0200)
Please consider pulling these changes from the signed vfs-6.15-rc3.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.15-rc3.fixes
----------------------------------------------------------------
Christian Brauner (2):
mount: ensure we don't pointlessly walk the mount tree
Merge tag 'ovl-fixes-6.15-rc2' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs
David Howells (2):
devpts: Fix type for uid and gid params
afs: Fix afs_dynroot_readdir() to not use the RCU read lock
Giuseppe Scrivano (1):
ovl: remove unused forward declaration
Gou Hao (1):
iomap: skip unnecessary ifs_block_is_uptodate check
Jan Stancek (1):
fs: use namespace_{lock,unlock} in dissolve_on_fput()
Miklos Szeredi (1):
ovl: don't allow datadir only
Omar Sandoval (1):
dcache: convert dentry flag macros to enum
Song Liu (2):
netfs: Only create /proc/fs/netfs with CONFIG_PROC_FS
fs: Fix filename init after recent refactoring
Vasiliy Kovalev (1):
hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key
Xiangsheng Hou (1):
virtiofs: add filesystem context source name check
fs/afs/dynroot.c | 4 +-
fs/devpts/inode.c | 4 +-
fs/fuse/virtio_fs.c | 3 ++
fs/hfs/bnode.c | 6 +++
fs/hfsplus/bnode.c | 6 +++
fs/iomap/buffered-io.c | 2 +-
fs/namei.c | 8 ++--
fs/namespace.c | 34 +++++++++------
fs/netfs/main.c | 4 ++
fs/overlayfs/overlayfs.h | 2 -
fs/overlayfs/super.c | 5 +++
include/linux/dcache.h | 106 ++++++++++++++++++++++-------------------------
12 files changed, 104 insertions(+), 80 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-04-02 15:46 Christian Brauner
2025-04-03 0:11 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-04-02 15:46 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains various fixes for this cycle:
- Add a new maintainer for configfs.
- Fix exportfs module description.
- Place flexible array memeber at the end of an internal struct in the
mount code.
- Add new maintainer for netfslib as Jeff Layton is stepping down as
current co-maintainer.
- Fix error handling in cachefiles_get_directory().
- Cleanup do_notify_pidfd().
- Fix syscall number definitions in pidfd selftests.
- Fix racy usage of fs_struct->in exec during multi-threaded exec.
- Ensure correct exit code is reported when pidfs_exit() is called from
release_task() for a delayed thread-group leader exit.
- Fix conflicting iomap flag definitions.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-6)
Debian clang version 16.0.6 (27+b1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 2df0c02dab829dd89360d98a8a1abaa026ef5798:
x86 boot build: make git ignore stale 'tools' directory (2025-03-24 23:09:14 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.15-rc1.fixes
for you to fetch changes up to 923936efeb74b3f42e5ad283a0b9110bda102601:
iomap: Fix conflicting values of iomap flags (2025-03-28 10:45:00 +0100)
Please consider pulling these changes from the signed vfs-6.15-rc1.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.15-rc1.fixes
----------------------------------------------------------------
Andreas Hindborg (1):
MAINTAINERS: configfs: add Andreas Hindborg as maintainer
Arnd Bergmann (1):
exportfs: add module description
Gustavo A. R. Silva (1):
fs: namespace: Avoid -Wflex-array-member-not-at-end warning
Jeff Layton (1):
netfs: add Paulo as maintainer and remove myself as Reviewer
Marc Dionne (1):
cachefiles: Fix oops in vfs_mkdir from cachefiles_get_directory
Oleg Nesterov (4):
pidfs: cleanup the usage of do_notify_pidfd()
selftests/pidfd: fixes syscall number defines
exec: fix the racy usage of fs_struct->in_exec
exit: fix the usage of delay_group_leader->exit_code in do_notify_parent() and pidfs_exit()
Ritesh Harjani (IBM) (1):
iomap: Fix conflicting values of iomap flags
CREDITS | 4 ++++
MAINTAINERS | 7 ++++---
fs/cachefiles/namei.c | 7 ++++---
fs/exec.c | 15 +++++++++------
fs/exportfs/expfs.c | 1 +
fs/namespace.c | 4 +++-
include/linux/iomap.h | 15 +++++++--------
kernel/exit.c | 11 +++++------
kernel/signal.c | 8 +++-----
tools/testing/selftests/clone3/clone3_selftests.h | 2 +-
tools/testing/selftests/pidfd/pidfd.h | 8 ++++----
11 files changed, 45 insertions(+), 37 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-03-20 15:22 Christian Brauner
2025-03-20 21:21 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-03-20 15:22 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains a final set of fixes for this cycle:
VFS:
- Ensure that the stable offset api doesn't return duplicate directory
entries when userspace has to perform the getdents call multiple times
on large directories.
afs:
- Prevent invalid pointer dereference during get_link RCU pathwalk.
fuse:
- Fix deadlock caused by uninitialized rings when using io_uring with fuse.
- Handle race condition when using io_uring with fuse to prevent NULL dereference.
libnetfs:
- Ensure that invalidate_cache is only called if implemented.
- Fix collection of results during pause when collection is offloaded.
- Ensure rolling_buffer_load_from_ra() doesn't clear mark bits.
- Make netfs_unbuffered_read() return ssize_t rather than int.
/* Testing */
gcc version (Debian 14.2.0-8) 14.2.0
Debian clang version 19.1.4 (1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 4701f33a10702d5fc577c32434eb62adde0a1ae1:
Linux 6.14-rc7 (2025-03-16 12:55:17 -1000)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.14-final.fixes
for you to fetch changes up to f70681e9e6066ab7b102e6b46a336a8ed67812ae:
libfs: Fix duplicate directory entry in offset_dir_lookup (2025-03-20 14:28:18 +0100)
Please consider pulling these changes from the signed vfs-6.14-final.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.14-final.fixes
----------------------------------------------------------------
Christian Brauner (1):
Merge patch series "netfs: Miscellaneous fixes"
David Howells (4):
afs: Fix afs_atcell_get_link() to check if ws_cell is unset first
netfs: Fix collection of results during pause when collection offloaded
netfs: Fix rolling_buffer_load_from_ra() to not clear mark bits
netfs: Fix netfs_unbuffered_read() to return ssize_t rather than int
Joanne Koong (1):
fuse: fix uring race condition for null dereference of fc
Luis Henriques (1):
fuse: fix possible deadlock if rings are never initialized
Max Kellermann (1):
netfs: Call `invalidate_cache` only if implemented
Yongjian Sun (1):
libfs: Fix duplicate directory entry in offset_dir_lookup
fs/afs/dynroot.c | 6 +++---
fs/fuse/dev.c | 2 +-
fs/fuse/dev_uring.c | 4 ++--
fs/libfs.c | 2 +-
fs/netfs/direct_read.c | 6 +++---
fs/netfs/read_collect.c | 18 ++++++++++--------
fs/netfs/rolling_buffer.c | 4 ----
fs/netfs/write_collect.c | 3 ++-
8 files changed, 22 insertions(+), 23 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-03-13 9:13 Christian Brauner
2025-03-13 19:04 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-03-13 9:13 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains various fixes for this cycle:
- Bring in an RCU pathwalk fix for afs. This is brought in as a merge
from the vfs-6.15.shared.afs branch that needs this commit and other
trees already depend on it.
- Fix vboxfs unterminated string handling.
/* Testing */
gcc version (Debian 14.2.0-8) 14.2.0
Debian clang version 19.1.4 (1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 00a7d39898c8010bfd5ff62af31ca5db34421b38:
fs/pipe: add simpler helpers for common cases (2025-03-06 18:25:35 -1000)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.14-rc7.fixes
for you to fetch changes up to 986a6f5eacb900ea0f6036ef724b26e76be40f65:
vboxsf: Add __nonstring annotations for unterminated strings (2025-03-11 13:06:39 +0100)
Please consider pulling these changes from the signed vfs-6.14-rc7.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.14-rc7.fixes
----------------------------------------------------------------
Christian Brauner (1):
Merge afs RCU pathwalk fix
David Howells (1):
afs: Fix afs_atcell_get_link() to handle RCU pathwalk
Kees Cook (1):
vboxsf: Add __nonstring annotations for unterminated strings
fs/afs/cell.c | 11 ++++++-----
fs/afs/dynroot.c | 15 +++++++++++++--
fs/afs/internal.h | 2 +-
fs/afs/proc.c | 4 ++--
fs/vboxsf/super.c | 3 +--
5 files changed, 23 insertions(+), 12 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-03-06 10:13 Christian Brauner
2025-03-06 18:20 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-03-06 10:13 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains various fixes for this cycle:
- Fix spelling mistakes in idmappings.rst.
- Fix RCU warnings in override_creds()/revert_creds().
- Create new pid namespaces with default limit now that pid_max is namespaced.
/* Testing */
gcc version (Debian 14.2.0-8) 14.2.0
Debian clang version 19.1.4 (1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit d082ecbc71e9e0bf49883ee4afd435a77a5101b6:
Linux 6.14-rc4 (2025-02-23 12:32:57 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.14-rc6.fixes
for you to fetch changes up to d385c8bceb14665e935419334aa3d3fac2f10456:
pid: Do not set pid_max in new pid namespaces (2025-03-06 10:18:36 +0100)
Please consider pulling these changes from the signed vfs-6.14-rc6.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.14-rc6.fixes
----------------------------------------------------------------
Aiden Ma (1):
doc: correcting two prefix errors in idmappings.rst
Herbert Xu (1):
cred: Fix RCU warnings in override/revert_creds
Michal Koutný (1):
pid: Do not set pid_max in new pid namespaces
Documentation/filesystems/idmappings.rst | 4 ++--
include/linux/cred.h | 10 ++--------
kernel/pid_namespace.c | 2 +-
3 files changed, 5 insertions(+), 11 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-02-25 11:51 Christian Brauner
2025-02-25 17:52 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-02-25 11:51 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains various fixes for this cycle:
- Use __readahead_folio() in fuse again to fix a UAF issue when using splice.
- Remove d_op->d_delete method from pidfs.
- Remove d_op->d_delete method from nsfs.
- Simplify iomap_dio_bio_iter().
- Fix a UAF in ovl_dentry_update_reval.
- Fix a miscalulated file range for filemap_fdatawrite_range_kick()
- Don't skip skip dirty page in folio_unmap_invalidate().
/* Testing */
gcc version (Debian 14.2.0-8) 14.2.0
Debian clang version 19.1.4 (1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 2408a807bfc3f738850ef5ad5e3fd59d66168996:
Merge tag 'vfs-6.14-rc4.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs (2025-02-17 10:38:25 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.14-rc5.fixes
for you to fetch changes up to b5799106b44e1df594f4696500dbbc3b326bba18:
iomap: Minor code simplification in iomap_dio_bio_iter() (2025-02-25 11:55:26 +0100)
Please consider pulling these changes from the signed vfs-6.14-rc5.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.14-rc5.fixes
----------------------------------------------------------------
Christian Brauner (4):
Merge tag 'fuse-fixes-6.14-rc4' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse
Merge patch series "fixes for uncached IO"
pidfs: remove d_op->d_delete
nsfs: remove d_op->d_delete
Jingbo Xu (2):
mm/filemap: fix miscalculated file range for filemap_fdatawrite_range_kick()
mm/truncate: don't skip dirty page in folio_unmap_invalidate()
Joanne Koong (1):
fuse: revert back to __readahead_folio() for readahead
John Garry (1):
iomap: Minor code simplification in iomap_dio_bio_iter()
Miklos Szeredi (1):
fuse: don't truncate cached, mutated symlink
Vasiliy Kovalev (1):
ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up
fs/fuse/dev.c | 6 ++++++
fs/fuse/dir.c | 2 +-
fs/fuse/file.c | 13 +++++++++++--
fs/iomap/direct-io.c | 8 +++-----
fs/namei.c | 24 +++++++++++++++++++-----
fs/nsfs.c | 1 -
fs/overlayfs/copy_up.c | 2 +-
fs/pidfs.c | 1 -
include/linux/fs.h | 6 ++++--
mm/filemap.c | 2 +-
mm/truncate.c | 2 --
11 files changed, 46 insertions(+), 21 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-02-17 10:37 Christian Brauner
2025-02-17 18:44 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-02-17 10:37 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains various fixes for this cycle:
- It was reported that the acct(2) system call can be used to trigger a
NULL deref in cases where it is set to write to a file that triggers
an internal lookup.
This can e.g., happen when pointing acct(2) to /sys/power/resume. At
the point the where the write to this file happens the calling task
has already exited and called exit_fs() but an internal lookup might
be triggered through lookup_bdev(). This may trigger a NULL-deref when
accessing current->fs.
Reorganize the code so that the the final write happens from the
workqueue but with the caller's credentials. This preserves the
(strange) permission model and has almost no regression risk.
Also block access to kernel internal filesystems as well as procfs and
sysfs in the first place.
- Various fixes for netfslib:
- Fix a number of read-retry hangs, including:
- Incorrect getting/putting of references on subreqs as we
retry them.
- Failure to track whether a last old subrequest in a retried
set is superfluous.
- Inconsistency in the usage of wait queues used for subrequests
(ie. using clear_and_wake_up_bit() whilst waiting on a private
waitqueue).
- Add stats counters for retries and publish in /proc/fs/netfs/stats.
This is not a fix per se, but is useful in debugging and shouldn't
otherwise change the operation of the code.
- Fix the ordering of queuing subrequests with respect to setting the
request flag that says we've now queued them all.
/* Testing */
gcc version (Debian 14.2.0-8) 14.2.0
Debian clang version 19.1.4 (1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit a64dcfb451e254085a7daee5fe51bf22959d52d3:
Linux 6.14-rc2 (2025-02-09 12:45:03 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.14-rc4.fixes
for you to fetch changes up to a33f72554adf4552e53af3784cebfc4f2886c396:
Merge patch series "netfs: Miscellaneous fixes" (2025-02-13 16:00:53 +0100)
Please consider pulling these changes from the signed vfs-6.14-rc4.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.14-rc4.fixes
----------------------------------------------------------------
Christian Brauner (4):
acct: perform last write from workqueue
acct: block access to kernel internal filesystems
Merge patch series "acct: don't allow access to internal filesystems"
Merge patch series "netfs: Miscellaneous fixes"
David Howells (3):
netfs: Fix a number of read-retry hangs
netfs: Add retry stat counters
netfs: Fix setting NETFS_RREQ_ALL_QUEUED to be after all subreqs queued
fs/netfs/buffered_read.c | 19 ++++--
fs/netfs/internal.h | 4 ++
fs/netfs/read_collect.c | 6 +-
fs/netfs/read_retry.c | 43 ++++++++++----
fs/netfs/stats.c | 9 +++
fs/netfs/write_issue.c | 1 +
fs/netfs/write_retry.c | 2 +
include/linux/netfs.h | 2 +-
include/trace/events/netfs.h | 4 +-
kernel/acct.c | 134 +++++++++++++++++++++++++++----------------
10 files changed, 154 insertions(+), 70 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-02-07 10:52 Christian Brauner
2025-02-07 22:25 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-02-07 10:52 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains various fixes for this cycle:
- Fix fsnotify FMODE_NONOTIFY* handling.
This also disables fsnotify on all pseudo files by default apart from
very selection exceptions. This carries a regression risk so we need
to watch out and adapt accordingly. However, it is overall a
significant improvement over the current status quo where every rando
file can get fsnotify enabled.
- Cleanup and simplify lockref_init() after recent lockref changes.
- Fix vboxfs build with gcc-15.
- Add an assert into inode_set_cached_link() to catch corrupt links.
- Allow users to also use an empty string check to detect whether a
given mount option string was empty or not.
- Fix how security options were appended to statmount()'s ->mnt_opt field.
- Fix statmount() selftests to always check the returned mask.
- Fix uninitialized value in vfs_statx_path().
- Fix pidfs_ioctl() sanity checks to guard against ioctl() overloading
and preserve extensibility.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-6)
Debian clang version 16.0.6 (27+b1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.14-rc2.fixes
for you to fetch changes up to 37d11cfc63604b3886308e2111d845d148ced8bc:
vfs: sanity check the length passed to inode_set_cached_link() (2025-02-07 10:29:59 +0100)
Please consider pulling these changes from the signed vfs-6.14-rc2.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.14-rc2.fixes
----------------------------------------------------------------
Amir Goldstein (3):
fsnotify: use accessor to set FMODE_NONOTIFY_*
fsnotify: disable notification by default for all pseudo files
fsnotify: disable pre-content and permission events by default
Andreas Gruenbacher (3):
gfs2: use lockref_init for gl_lockref
gfs2: switch to lockref_init(..., 1)
lockref: remove count argument of lockref_init
Brahmajit Das (1):
vboxsf: fix building with GCC 15
Christian Brauner (3):
Merge patch series "further lockref cleanups"
Merge patch series "Fix for huge faults regression"
pidfs: improve ioctl handling
Mateusz Guzik (1):
vfs: sanity check the length passed to inode_set_cached_link()
Miklos Szeredi (3):
statmount: let unset strings be empty
fs: fix adding security options to statmount.mnt_opt
selftests: always check mask returned by statmount(2)
Su Hui (1):
fs/stat.c: avoid harmless garbage value problem in vfs_statx_path()
drivers/tty/pty.c | 2 +-
fs/dcache.c | 2 +-
fs/erofs/zdata.c | 2 +-
fs/file_table.c | 16 +++++++
fs/gfs2/glock.c | 2 +-
fs/gfs2/main.c | 1 -
fs/gfs2/quota.c | 4 +-
fs/namespace.c | 54 ++++++++++++----------
fs/notify/fsnotify.c | 18 +++++---
fs/open.c | 11 +++--
fs/pidfs.c | 12 ++++-
fs/pipe.c | 6 +++
fs/stat.c | 4 +-
fs/vboxsf/super.c | 3 +-
include/linux/fs.h | 20 +++++++-
include/linux/fsnotify.h | 4 +-
include/linux/lockref.h | 7 +--
net/socket.c | 5 ++
.../filesystems/statmount/statmount_test.c | 22 ++++++++-
19 files changed, 143 insertions(+), 52 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-01-10 15:16 Christian Brauner
2025-01-10 18:12 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-01-10 15:16 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
The following fixes are contained in this pull request:
afs:
- Fix the maximum cell name length.
- Fix merge preference rule failure condition.
fuse:
- Fix fuse_get_user_pages() so it doesn't risk misleading the caller to
think pages have been allocated when they actually haven't.
- Fix direct-io folio offset and length calculation.
netfs:
- Fix async direct-io handling.
- Fix read-retry for filesystems that don't provide a ->prepare_read()
method.
vfs:
- Prevent truncating 64-bit offsets to 32-bits in iomap.
- Fix memory barrier interactions when polling.
- Remove MNT_ONRB to fix concurrent modification of @mnt->mnt_flags
leading to MNT_ONRB to not be raised and invalid access to a list
member. See commit message for details.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-6)
Debian clang version 16.0.6 (27+b1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit fbfd64d25c7af3b8695201ebc85efe90be28c5a3:
Merge tag 'vfs-6.13-rc7.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs (2025-01-06 10:26:39 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.13-rc7.fixes.2
for you to fetch changes up to 1623bc27a85a93e82194c8d077eccc464efa67db:
Merge branch 'vfs-6.14.poll' into vfs.fixes (2025-01-10 12:01:21 +0100)
Please consider pulling these changes from the signed vfs-6.13-rc7.fixes.2 tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.13-rc7.fixes.2
----------------------------------------------------------------
Bernd Schubert (1):
fuse: Set *nbytesp=0 in fuse_get_user_pages on allocation failure
Christian Brauner (5):
Merge tag 'fuse-fixes-6.13-rc7' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse
fs: kill MNT_ONRB
Merge tag 'vfs-6.14-rc7.mount.fixes'
Merge patch series "poll_wait: add mb() to fix theoretical race between waitqueue_active() and .poll()"
Merge branch 'vfs-6.14.poll' into vfs.fixes
David Howells (3):
afs: Fix the maximum cell name length
netfs: Fix kernel async DIO
netfs: Fix read-retry for fs with no ->prepare_read()
Joanne Koong (1):
fuse: fix direct io folio offset and length calculation
Lizhi Xu (1):
afs: Fix merge preference rule failure condition
Marco Nelissen (1):
iomap: avoid avoid truncating 64-bit offset to 32 bits
Oleg Nesterov (5):
poll_wait: add mb() to fix theoretical race between waitqueue_active() and .poll()
poll_wait: kill the obsolete wait_address check
io_uring_poll: kill the no longer necessary barrier after poll_wait()
sock_poll_wait: kill the no longer necessary barrier after poll_wait()
poll: kill poll_does_not_wait()
fs/afs/addr_prefs.c | 6 ++++--
fs/afs/afs.h | 2 +-
fs/afs/afs_vl.h | 1 +
fs/afs/vl_alias.c | 8 ++++++--
fs/afs/vlclient.c | 2 +-
fs/fuse/file.c | 31 +++++++++++++++++++------------
fs/iomap/buffered-io.c | 2 +-
fs/mount.h | 15 +++++++++------
fs/namespace.c | 14 ++++++--------
fs/netfs/direct_write.c | 7 ++++++-
fs/netfs/read_retry.c | 3 ++-
include/linux/mount.h | 3 +--
include/linux/poll.h | 26 ++++++++++++--------------
include/net/sock.h | 17 +++++++----------
io_uring/io_uring.c | 9 ++++-----
15 files changed, 80 insertions(+), 66 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2025-01-06 15:32 Christian Brauner
2025-01-06 18:40 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2025-01-06 15:32 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
slowly resurrecting from the holidays... What year is it? And have we
already started generating pull requests with AI?
/* Summary */
This contains various fixes for this cycle:
- Relax assertions on failure to encode file handles.
The ->encode_fh() method can fail for various reasons. None of them
warrant a WARN_ON().
- Fix overlayfs file handle encoding by allowing encoding an fid from an
inode without an alias.
- Make sure fuse_dir_open() handles FOPEN_KEEP_CACHE. If it's not
specified fuse needs to invaludate the directory inode page cache.
- Fix qnx6 so it builds with gcc-15.
- Various fixes for netfslib and ceph and nfs filesystems:
- Ignore silly rename files from afs and nfs when building header archives.
- Fix read result collection in netfslib with multiple subrequests.
- Handle ENOMEM for netfslib buffered reads.
- Fix oops in nfs_netfs_init_request().
- Parse the secctx command immediately in cachefiles.
- Remove a redundant smp_rmb() in netfslib.
- Handle recursion in read retry in netfslib.
- Fix clearing of folio_queue.
- Fix missing cancellation of copy-to_cache when the cache for a file
is temporarly disabled in netfslib.
- Sanity check the hfs root record.
- Fix zero padding data issues in concurrent write scenarios.
- Fix is_mnt_ns_file() after converting nsfs to path_from_stashed().
- Fix missing declaration of init_files.
- Increase I/O priority when writing revoke records in jbd2.
- Flush filesystem device before updating tail sequence in jbd2.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-6)
Debian clang version 16.0.6 (27+b1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
- There will be a small merge conflict with mainline. The conflict
resolution should like this:
diff --cc fs/smb/client/smb2pdu.c
index 959359301250,458b53d1f9cb..000000000000
--- a/fs/smb/client/smb2pdu.c
+++ b/fs/smb/client/smb2pdu.c
@@@ -4840,12 -4841,12 +4841,14 @@@ smb2_writev_callback(struct mid_q_entr
if (written > wdata->subreq.len)
written &= 0xFFFF;
+ cifs_stats_bytes_written(tcon, written);
+
- if (written < wdata->subreq.len)
+ if (written < wdata->subreq.len) {
wdata->result = -ENOSPC;
- else
+ } else if (written > 0) {
wdata->subreq.len = written;
+ __set_bit(NETFS_SREQ_MADE_PROGRESS, &wdata->subreq.flags);
+ }
break;
case MID_REQUEST_SUBMITTED:
case MID_RETRY_NEEDED:
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.13-rc7.fixes
for you to fetch changes up to 368fcc5d3f8bf645a630a44e65f5eb008aba7082:
Merge patch series "Fix encoding overlayfs fid for fanotify delete events" (2025-01-06 15:43:58 +0100)
Please consider pulling these changes from the signed vfs-6.13-rc7.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.13-rc7.fixes
----------------------------------------------------------------
Amir Goldstein (4):
fs: relax assertions on failure to encode file handles
fuse: respect FOPEN_KEEP_CACHE on opendir
ovl: pass realinode to ovl_encode_real_fh() instead of realdentry
ovl: support encoding fid from inode with no alias
Brahmajit Das (1):
fs/qnx6: Fix building with GCC 15
Christian Brauner (4):
Merge patch series "jbd2: two straightforward fixes"
Merge patch series "iomap: fix zero padding data issue in concurrent append writes"
Merge patch series "netfs, ceph, nfs, cachefiles: Miscellaneous fixes/changes"
Merge patch series "Fix encoding overlayfs fid for fanotify delete events"
David Howells (9):
kheaders: Ignore silly-rename files
netfs: Fix non-contiguous donation between completed reads
netfs: Fix enomem handling in buffered reads
nfs: Fix oops in nfs_netfs_init_request() when copying to cache
netfs: Fix missing barriers by using clear_and_wake_up_bit()
netfs: Work around recursion by abandoning retry if nothing read
netfs: Fix ceph copy to cache on write-begin
netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled
netfs: Fix is-caching check in read-retry
Leo Stone (1):
hfs: Sanity check the root record
Long Li (2):
iomap: pass byte granular end position to iomap_add_to_ioend
iomap: fix zero padding data issue in concurrent append writes
Max Kellermann (1):
cachefiles: Parse the "secctx" immediately
Miklos Szeredi (1):
fs: fix is_mnt_ns_file()
Zhang Kunbo (1):
fs: fix missing declaration of init_files
Zhang Yi (2):
jbd2: increase IO priority for writing revoke records
jbd2: flush filesystem device before updating tail sequence
Zilin Guan (1):
netfs: Remove redundant use of smp_rmb()
fs/9p/vfs_addr.c | 6 ++++-
fs/afs/write.c | 5 +++-
fs/cachefiles/daemon.c | 14 +++++-----
fs/cachefiles/internal.h | 3 ++-
fs/cachefiles/security.c | 6 ++---
fs/file.c | 1 +
fs/fuse/dir.c | 2 ++
fs/hfs/super.c | 4 ++-
fs/iomap/buffered-io.c | 66 +++++++++++++++++++++++++++++++++++++++++-------
fs/jbd2/commit.c | 4 +--
fs/jbd2/revoke.c | 2 +-
fs/namespace.c | 10 ++++++--
fs/netfs/buffered_read.c | 28 +++++++++++---------
fs/netfs/direct_write.c | 1 -
fs/netfs/read_collect.c | 33 ++++++++++++++----------
fs/netfs/read_pgpriv2.c | 4 +++
fs/netfs/read_retry.c | 8 +++---
fs/netfs/write_collect.c | 14 ++++------
fs/netfs/write_issue.c | 2 ++
fs/nfs/fscache.c | 9 ++++++-
fs/notify/fdinfo.c | 4 +--
fs/overlayfs/copy_up.c | 16 ++++++------
fs/overlayfs/export.c | 49 +++++++++++++++++++----------------
fs/overlayfs/namei.c | 4 +--
fs/overlayfs/overlayfs.h | 2 +-
fs/qnx6/inode.c | 11 +++-----
fs/smb/client/cifssmb.c | 13 +++++++---
fs/smb/client/smb2pdu.c | 9 ++++---
include/linux/iomap.h | 2 +-
include/linux/netfs.h | 7 +++--
kernel/gen_kheaders.sh | 1 +
31 files changed, 217 insertions(+), 123 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-11-27 15:41 Christian Brauner
2024-11-27 16:14 ` Linus Torvalds
2024-11-27 16:15 ` pr-tracker-bot
0 siblings, 2 replies; 188+ messages in thread
From: Christian Brauner @ 2024-11-27 15:41 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
I was sent a bug fix for the backing file rework that relied on the
overlayfs pull request. The vfs.fixes branch used an earlier mainline
commit as base. So I thought how to resolve this and my solution was to
create a new ovl.fixes branch which contained the overlayfs changes for
v6.13 and then apply the fix on top of it. That branch was then merged
into vfs.fixes with an explanation why. Let me know if I should do this
differently next time.
/* Summary */
This contains various fixes for this cycle:
- Fix a few iomap bugs.
- Fix a wrong argument in backing file callback.
- Fix security mount option retrieval in statmount().
- Cleanup how statmount() handles unescaped options.
- Add a missing inode_owner_or_capable() check for setting write hints.
- Clear the return value in read_kcore_iter() after a successful
iov_iter_zero().
- Fix a mount_setattr() selftest.
- Fix function signature in mount api documentation.
- Remove duplicate include header in the fscache code.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-6)
Debian clang version 16.0.6 (27+b1)
All patches have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit e7675238b9bf4db0b872d5dbcd53efa31914c98f:
Merge tag 'ovl-update-6.13' of git://git.kernel.org/pub/scm/linux/kernel/git/overlayfs/vfs (2024-11-22 20:55:42 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.13-rc1.fixes
for you to fetch changes up to cf87766dd6f9ddcceaa8ee26e3cbd7538e42dd19:
Merge branch 'ovl.fixes' (2024-11-26 18:15:06 +0100)
Please consider pulling these changes from the signed vfs-6.13-rc1.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.13-rc1.fixes
----------------------------------------------------------------
Amir Goldstein (1):
fs/backing_file: fix wrong argument in callback
Brian Foster (4):
iomap: warn on zero range of a post-eof folio
iomap: reset per-iter state on non-error iter advances
iomap: lift zeroed mapping handling into iomap_zero_range()
iomap: elide flush from partial eof zero range
Christian Brauner (3):
Merge patch series "iomap: zero range flush fixes"
statmount: fix security option retrieval
Merge branch 'ovl.fixes'
Christoph Hellwig (1):
fs: require inode_owner_or_capable for F_SET_RW_HINT
Jiri Olsa (1):
fs/proc/kcore.c: Clear ret value in read_kcore_iter after successful iov_iter_zero
Michael Ellerman (1):
selftests/mount_setattr: Fix failures on 64K PAGE_SIZE kernels
Miklos Szeredi (1):
statmount: clean up unescaped option handling
Randy Dunlap (1):
fs_parser: update mount_api doc to match function signature
Thorsten Blum (1):
fscache: Remove duplicate included header
Documentation/filesystems/mount_api.rst | 3 +-
fs/backing-file.c | 3 +-
fs/fcntl.c | 3 +
fs/iomap/buffered-io.c | 90 +++++++++++-----------
fs/iomap/iter.c | 11 ++-
fs/namespace.c | 46 +++++------
fs/netfs/fscache_io.c | 1 -
fs/proc/kcore.c | 1 +
.../selftests/mount_setattr/mount_setattr_test.c | 2 +-
9 files changed, 81 insertions(+), 79 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2024-11-27 15:41 Christian Brauner
@ 2024-11-27 16:14 ` Linus Torvalds
2024-11-27 16:15 ` pr-tracker-bot
1 sibling, 0 replies; 188+ messages in thread
From: Linus Torvalds @ 2024-11-27 16:14 UTC (permalink / raw)
To: Christian Brauner; +Cc: linux-fsdevel, linux-kernel
On Wed, 27 Nov 2024 at 07:41, Christian Brauner <brauner@kernel.org> wrote:
>
> I was sent a bug fix for the backing file rework that relied on the
> overlayfs pull request. The vfs.fixes branch used an earlier mainline
> commit as base. So I thought how to resolve this and my solution was to
> create a new ovl.fixes branch which contained the overlayfs changes for
> v6.13 and then apply the fix on top of it. That branch was then merged
> into vfs.fixes with an explanation why. Let me know if I should do this
> differently next time.
Thanks, this looks good - exactly like I think it should have been done.
Pulled,
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2024-11-27 15:41 Christian Brauner
2024-11-27 16:14 ` Linus Torvalds
@ 2024-11-27 16:15 ` pr-tracker-bot
1 sibling, 0 replies; 188+ messages in thread
From: pr-tracker-bot @ 2024-11-27 16:15 UTC (permalink / raw)
To: Christian Brauner
Cc: Linus Torvalds, Christian Brauner, linux-fsdevel, linux-kernel
The pull request you sent on Wed, 27 Nov 2024 16:41:03 +0100:
> git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.13-rc1.fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7d4050728c83aa63828494ad0f4d0eb4faf5f97a
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
^ permalink raw reply [flat|nested] 188+ messages in thread
* [GIT PULL] vfs fixes
@ 2024-11-01 12:43 Christian Brauner
2024-11-01 17:48 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-11-01 12:43 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few fixes:
VFS:
- Fix copy_page_from_iter_atomic() if KMAP_LOCAL_FORCE_MAP=y is set.
- Add a get_tree_bdev_flags() helper that allows to modify e.g., whether
errors are logged into the filesystem context during superblock
creation. This is used by erofs to fix a userspace regression where an
error is currently logged when its used on a regular file which is an
new allowed mode in erofs.
netfs:
- Fix the sysfs debug path in the documentation.
- Fix iov_iter_get_pages*() for folio queues by skipping the page
extracation if we're at the end of a folio.
afs:
- Fix moving subdirectories to different parent directory.
autofs:
- Fix handling of AUTOFS_DEV_IOCTL_TIMEOUT_CMD ioctl in
validate_dev_ioctl(). The actual ioctl number, not the ioctl command
needs to be checked for autofs.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-3)
Debian clang version 16.0.6 (27+b1)
All patches are based on v6.11-rc4 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 42f7652d3eb527d03665b09edac47f85fb600924:
Linux 6.12-rc4 (2024-10-20 15:19:38 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.12-rc6.fixes
for you to fetch changes up to c749d9b7ebbc5716af7a95f7768634b30d9446ec:
iov_iter: fix copy_page_from_iter_atomic() if KMAP_LOCAL_FORCE_MAP (2024-10-28 13:39:35 +0100)
(Note, I'm still not fully recovered so currently with a little reduced
activity.)
Please consider pulling these changes from the signed vfs-6.12-rc6.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.12-rc6.fixes
----------------------------------------------------------------
Christian Brauner (1):
Merge patch series "fs/super.c: introduce get_tree_bdev_flags()"
David Howells (2):
afs: Fix missing subdir edit when renamed between parent dirs
iov_iter: Fix iov_iter_get_pages*() for folio_queue
Gao Xiang (2):
fs/super.c: introduce get_tree_bdev_flags()
erofs: use get_tree_bdev_flags() to avoid misleading messages
Hongbo Li (1):
doc: correcting the debug path for cachefiles
Hugh Dickins (1):
iov_iter: fix copy_page_from_iter_atomic() if KMAP_LOCAL_FORCE_MAP
Ian Kent (1):
autofs: fix thinko in validate_dev_ioctl()
Documentation/filesystems/caching/cachefiles.rst | 2 +-
fs/afs/dir.c | 25 +++++++
fs/afs/dir_edit.c | 91 +++++++++++++++++++++++-
fs/afs/internal.h | 2 +
fs/autofs/dev-ioctl.c | 5 +-
fs/erofs/super.c | 4 +-
fs/super.c | 26 +++++--
include/linux/fs_context.h | 6 ++
include/trace/events/afs.h | 7 +-
lib/iov_iter.c | 25 ++++---
10 files changed, 169 insertions(+), 24 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-10-21 11:46 Christian Brauner
2024-10-21 18:27 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-10-21 11:46 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few fixes:
afs:
- Fix a lock recursion in afs_wake_up_async_call() on ->notify_lock.
netfs:
- Drop the references to a folio immediately after the folio has been
extracted to prevent races with future I/O collection.
- Fix a documenation build error.
- Downgrade the i_rwsem for buffered writes to fix a cifs reported
performance regression when switching to netfslib.
vfs:
- Explicitly return -E2BIG from openat2() if the specified size is
unexpectedly large. This aligns openat2() with other extensible struct
based system calls.
- When copying a mount namespace ensure that we only try to remove the
new copy from the mount namespace rbtree if it has already been added
to it.
nilfs:
- Clear the buffer delay flag when clearing the buffer state clags when
a buffer head is discarded to prevent a kernel OOPs.
ocfs2:
- Fix an unitialized value warning in ocfs2_setattr().
proc:
- Fix a kernel doc warning.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-3)
Debian clang version 16.0.6 (27+b1)
All patches are based on v6.11-rc2 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b:
Linux 6.12-rc2 (2024-10-06 15:32:27 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.12-rc5.fixes
for you to fetch changes up to 197231da7f6a2e9884f84a4a463f53f9f491d920:
proc: Fix W=1 build kernel-doc warning (2024-10-18 13:02:47 +0200)
Please consider pulling these changes from the signed vfs-6.12-rc5.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.12-rc5.fixes
----------------------------------------------------------------
Aleksa Sarai (1):
openat2: explicitly return -E2BIG for (usize > PAGE_SIZE)
Alessandro Zanni (1):
fs: Fix uninitialized value issue in from_kuid and from_kgid
Christian Brauner (1):
fs: don't try and remove empty rbtree node
David Howells (3):
netfs: In readahead, put the folio refs as soon extracted
netfs: Downgrade i_rwsem for a buffered write
afs: Fix lock recursion
Jonathan Corbet (1):
netfs: fix documentation build error
Ryusuke Konishi (1):
nilfs2: fix kernel bug due to missing clearing of buffer delay flag
Thorsten Blum (1):
proc: Fix W=1 build kernel-doc warning
Documentation/filesystems/netfs_library.rst | 1 -
fs/afs/internal.h | 2 +
fs/afs/rxrpc.c | 83 ++++++++++++++++++++---------
fs/namespace.c | 4 +-
fs/netfs/buffered_read.c | 47 +++++-----------
fs/netfs/locking.c | 3 +-
fs/netfs/read_collect.c | 2 +
fs/nilfs2/page.c | 6 ++-
fs/ocfs2/file.c | 9 ++--
fs/open.c | 2 +
fs/proc/fd.c | 2 +-
include/trace/events/netfs.h | 1 -
12 files changed, 95 insertions(+), 67 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-10-03 9:00 Christian Brauner
2024-10-03 16:53 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-10-03 9:00 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains fixes for this merge window:
vfs:
- Ensure that iter_folioq_get_pages() advances to the next slot otherwise it
will end up using the same folio with an out-of-bound offset.
iomap:
- Dont unshare delalloc extents which can't be reflinked, and thus can't be shared.
- Constrain the file range passed to iomap_file_unshare() directly in iomap
instead of requiring the callers to do it.
netfs:
- Use folioq_count instead of folioq_nr_slot to prevent an unitialized value
warning in netfs_clear_buffer().
- Fix missing wakeup after issuing writes by scheduling the write collector
only if all the subrequest queues are empty and thus no writes are pending.
- Fix two minor documentation bugs.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-3)
Debian clang version 16.0.6 (27+b1)
/* Conflicts */
No known conflicts.
The following changes since commit e32cde8d2bd7d251a8f9b434143977ddf13dcec6:
Merge tag 'sched_ext-for-6.12-rc1-fixes-1' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext (2024-09-30 12:58:17 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.12-rc2.fixes.2
for you to fetch changes up to a311a08a4237241fb5b9d219d3e33346de6e83e0:
iomap: constrain the file range passed to iomap_file_unshare (2024-10-03 10:22:28 +0200)
Please consider pulling these changes from the signed vfs-6.12-rc2.fixes.2 tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.12-rc2.fixes.2
----------------------------------------------------------------
Chang Yu (1):
netfs: Fix a KMSAN uninit-value error in netfs_clear_buffer
Christian Brauner (2):
folio_queue: fix documentation
Documentation: add missing folio_queue entry
Darrick J. Wong (2):
iomap: don't bother unsharing delalloc extents
iomap: constrain the file range passed to iomap_file_unshare
David Howells (1):
netfs: Fix missing wakeup after issuing writes
Omar Sandoval (1):
iov_iter: fix advancing slot in iter_folioq_get_pages()
Documentation/core-api/index.rst | 1 +
fs/dax.c | 6 +++++-
fs/iomap/buffered-io.c | 9 +++++++--
fs/netfs/misc.c | 2 +-
fs/netfs/write_issue.c | 42 ++++++++++++++++++++++++++--------------
include/linux/folio_queue.h | 2 +-
lib/iov_iter.c | 2 +-
7 files changed, 43 insertions(+), 21 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-09-30 13:46 Christian Brauner
2024-09-30 20:21 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-09-30 13:46 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains fixes for this merge window:
afs:
- Fix setting of the server responding flag.
- Remove unused struct afs_address_list and afs_put_address_list() function.
- Fix infinite loop because of unresponsive servers.
- Ensure that afs_retry_request() function is correctly added to the
afs_req_ops netfs operations table.
netfs:
- Fix netfs_folio tracepoint handling to handle NULL mappings.
- Add a missing folio_queue API documentation.
- Ensure that netfs_write_folio() correctly advances the iterator via
iov_iter_advance().
- Fix a dentry leak during concurrent cull and cookie lookup operations in
cachefiles.
pidfs:
- Correctly handle accessing another task's pid namespace.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-3)
Debian clang version 16.0.6 (27+b1)
/* Conflicts */
No known conflicts.
The following changes since commit 075dbe9f6e3c21596c5245826a4ee1f1c1676eb8:
Merge tag 'soc-ep93xx-dt-6.12' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc (2024-09-26 12:00:25 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.12-rc2.fixes
for you to fetch changes up to f801850bc263d7fa0a4e6d9a36cddf4966c79c14:
netfs: Fix the netfs_folio tracepoint to handle NULL mapping (2024-09-30 14:11:05 +0200)
Please consider pulling these changes from the signed vfs-6.12-rc2.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.12-rc2.fixes
----------------------------------------------------------------
Baokun Li (1):
cachefiles: fix dentry leak in cachefiles_open_file()
Christian Brauner (1):
pidfs: check for valid pid namespace
David Howells (5):
afs: Fix missing wire-up of afs_retry_request()
afs: Fix the setting of the server responding flag
netfs: Advance iterator correctly rather than jumping it
netfs: Add folio_queue API documentation
netfs: Fix the netfs_folio tracepoint to handle NULL mapping
Marc Dionne (1):
afs: Fix possible infinite loop with unresponsive servers
Thorsten Blum (1):
afs: Remove unused struct and function prototype
Documentation/core-api/folio_queue.rst | 212 +++++++++++++++++++++++++++++++++
fs/afs/afs_vl.h | 9 --
fs/afs/file.c | 1 +
fs/afs/fs_operation.c | 2 +-
fs/afs/fs_probe.c | 4 +-
fs/afs/rotate.c | 11 +-
fs/cachefiles/namei.c | 7 +-
fs/netfs/write_issue.c | 12 +-
fs/pidfs.c | 5 +-
include/linux/folio_queue.h | 168 ++++++++++++++++++++++++++
include/trace/events/netfs.h | 3 +-
11 files changed, 410 insertions(+), 24 deletions(-)
create mode 100644 Documentation/core-api/folio_queue.rst
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-09-04 12:03 Christian Brauner
2024-09-04 16:46 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-09-04 12:03 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains two fixes for this merge window:
netfs:
- Ensure that fscache_cookie_lru_time is deleted when the fscache module is
removed to prevent UAF.
- Fix filemap_invalidate_inode() to use invalidate_inode_pages2_range(). Before
it used truncate_inode_pages_partial() which causes copy_file_range() to fail
on cifs.
/* Testing */
Debian clang version 16.0.6 (27+b1)
gcc (Debian 14.2.0-1) 14.2.0
/* Conflicts */
No known conflicts.
The following changes since commit 5be63fc19fcaa4c236b307420483578a56986a37:
Linux 6.11-rc5 (2024-08-25 19:07:11 +1200)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.11-rc7.fixes
for you to fetch changes up to 72a6e22c604c95ddb3b10b5d3bb85b6ff4dbc34f:
fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF (2024-09-01 10:30:25 +0200)
Please consider pulling these changes from the signed vfs-6.11-rc7.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.11-rc7.fixes
----------------------------------------------------------------
Baokun Li (1):
fscache: delete fscache_cookie_lru_timer when fscache exits to avoid UAF
David Howells (1):
mm: Fix filemap_invalidate_inode() to use invalidate_inode_pages2_range()
fs/netfs/fscache_main.c | 1 +
mm/filemap.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-08-26 15:25 Christian Brauner
2024-08-27 5:04 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-08-26 15:25 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains fixes for this merge window:
VFS:
- Ensure that backing files uses file->f_ops->splice_write() for splice.
netfs:
- Revert the removal of PG_private_2 from netfs_release_folio() as cephfs still
relies on this.
- When AS_RELEASE_ALWAYS is set on a mapping the folio needs to always be
invalidated during truncation.
- Fix losing untruncated data in a folio by making letting
netfs_release_folio() return false if the folio is dirty.
- Fix trimming of streaming-write folios in netfs_inval_folio() .
- Reset iterator before retrying a short read.
- Fix interaction of streaming writes with zero-point tracker
afs:
- During truncation afs currently calls truncate_setsize() which sets i_size,
expands the pagecache and truncates it. The first two operations aren't
needed because they will have already been done. So call truncate_pagecache()
instead and skip the redundant parts.
overlayfs:
- Fix checking of the number of allowed lower layers so 500 layers can actually
be used instead of just 499
- Add missing '\n' to pr_err() output.
- Pass string to ovl_parse_layer() and thus allow it to be used for
Opt_lowerdir as well.
pidfd:
- Revert blocking the creation of pidfds for kthread as apparently userspace
relies on this. Specifically, it breaks systemd during shutdown.
romfs:
- Fix romfs_read_folio() to use the correct offset with folio_zero_tail().
/* Testing */
Debian clang version 16.0.6 (27+b1)
gcc (Debian 14.2.0-1) 14.2.0
/* Conflicts */
No known conflicts.
The following changes since commit 47ac09b91befbb6a235ab620c32af719f8208399:
Linux 6.11-rc4 (2024-08-18 13:17:27 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.11-rc6.fixes
for you to fetch changes up to e00e99ba6c6b8e5239e75cd6684a6827d93c39a2:
netfs: Fix interaction of streaming writes with zero-point tracker (2024-08-24 16:09:17 +0200)
Please consider pulling these changes from the signed vfs-6.11-rc6.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.11-rc6.fixes
----------------------------------------------------------------
Christian Brauner (4):
romfs: fix romfs_read_folio()
Revert "pidfd: prevent creation of pidfds for kthreads"
ovl: pass string to ovl_parse_layer()
Merge patch series "ovl: simplify ovl_parse_param_lowerdir()"
David Howells (7):
netfs, ceph: Partially revert "netfs: Replace PG_fscache by setting folio->private and marking dirty"
mm: Fix missing folio invalidation calls during truncation
afs: Fix post-setattr file edit to do truncation correctly
netfs: Fix netfs_release_folio() to say no if folio dirty
netfs: Fix trimming of streaming-write folios in netfs_inval_folio()
netfs: Fix missing iterator reset on retry of short read
netfs: Fix interaction of streaming writes with zero-point tracker
Ed Tsai (1):
backing-file: convert to using fops->splice_write
Zhihao Cheng (2):
ovl: fix wrong lowerdir number check for parameter Opt_lowerdir
ovl: ovl_parse_param_lowerdir: Add missed '\n' for pr_err
fs/afs/inode.c | 11 ++++++---
fs/backing-file.c | 5 +++-
fs/ceph/inode.c | 1 +
fs/netfs/io.c | 1 +
fs/netfs/misc.c | 60 ++++++++++++++++++++++++++++++++++++------------
fs/netfs/write_collect.c | 7 ++++++
fs/overlayfs/params.c | 51 ++++++++++------------------------------
fs/romfs/super.c | 2 +-
kernel/fork.c | 25 +++-----------------
mm/truncate.c | 4 ++--
10 files changed, 84 insertions(+), 83 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-08-14 13:29 Christian Brauner
2024-08-14 16:28 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-08-14 13:29 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains fixes for this merge window:
VFS:
- Fix the name of file lease slab cache. When file leases were split out of
file locks the name of the file lock slab cache was used for the file leases
slab cache as well.
- Fix a type in take_fd() helper.
- Fix infinite directory iteration for stable offsets in tmpfs.
- When the icache is pruned all reclaimable inodes are marked with I_FREEING
and other processes that try to lookup such inodes will block.
But some filesystems like ext4 can trigger lookups in their inode evict
callback causing deadlocks. Ext4 does such lookups if the ea_inode feature is
used whereby a separate inode may be used to store xattrs.
Introduce I_LRU_ISOLATING which pins the inode while its pages are
reclaimed. This avoids inode deletion during inode_lru_isolate() avoiding the
deadlock and evict is made to wait until I_LRU_ISOLATING is done.
netfs:
- Fault in smaller chunks for non-large folio mappings for filesystems that
haven't been converted to large folios yet.
- Fix the CONFIG_NETFS_DEBUG config option. The config option was renamed a
short while ago and that introduced two minor issues. First, it depended on
CONFIG_NETFS whereas it wants to depend on CONFIG_NETFS_SUPPORT. The former
doesn't exist, while the latter does. Second, the documentation for the
config option wasn't fixed up.
- Revert the removal of the PG_private_2 writeback flag as ceph is using it and
fix how that flag is handled in netfs.
- Fix DIO reads on 9p. A program watching a file on a 9p mount wouldn't see any
changes in the size of the file being exported by the server if the file was
changed directly in the source filesystem. Fix this by attempting to read the
full size specified when a DIO read is requested.
- Fix a NULL pointer dereference bug due to a data race where a cachefiles
cookies was retired even though it was still in use. Check the cookie's
n_accesses counter before discarding it.
nsfs:
- Fix ioctl declaration for NS_GET_MNTNS_ID from _IO() to _IOR() as the kernel
is writing to userspace.
pidfs:
- Prevent the creation of pidfds for kthreads until we have a use-case for it
and we know the semantics we want. It also confuses userspace why they can
get pidfds for kthreads.
squashfs:
- Fix an unitialized value bug reported by KMSAN caused by a corrupted symbolic
link size read from disk. Check that the symbolic link size is not larger
than expected.
The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.11-rc4.fixes
for you to fetch changes up to 810ee43d9cd245d138a2733d87a24858a23f577d:
Squashfs: sanity check symbolic link size (2024-08-13 13:56:46 +0200)
----------------------------------------------------------------
vfs-6.11-rc4.fixes
----------------------------------------------------------------
Christian Brauner (2):
nsfs: fix ioctl declaration
pidfd: prevent creation of pidfds for kthreads
David Howells (2):
netfs, ceph: Revert "netfs: Remove deprecated use of PG_private_2 as a second writeback flag"
netfs: Fix handling of USE_PGPRIV2 and WRITE_TO_CACHE flags
Dominique Martinet (1):
9p: Fix DIO read through netfs
Lukas Bulwahn (1):
netfs: clean up after renaming FSCACHE_DEBUG config
Mathias Krause (1):
file: fix typo in take_fd() comment
Matthew Wilcox (Oracle) (1):
netfs: Fault in smaller chunks for non-large folio mappings
Max Kellermann (1):
fs/netfs/fscache_cookie: add missing "n_accesses" check
Omar Sandoval (1):
filelock: fix name of file_lease slab cache
Phillip Lougher (1):
Squashfs: sanity check symbolic link size
Zhihao Cheng (1):
vfs: Don't evict inode under the inode lru traversing context
yangerkun (1):
libfs: fix infinite directory reads for offset dir
Documentation/filesystems/caching/fscache.rst | 8 +-
fs/9p/vfs_addr.c | 3 +-
fs/afs/file.c | 3 +-
fs/ceph/addr.c | 28 ++++-
fs/ceph/inode.c | 2 -
fs/inode.c | 39 ++++++-
fs/libfs.c | 35 ++++--
fs/locks.c | 2 +-
fs/netfs/Kconfig | 2 +-
fs/netfs/buffered_read.c | 123 +++++++++++++++++---
fs/netfs/buffered_write.c | 2 +-
fs/netfs/fscache_cookie.c | 4 +
fs/netfs/io.c | 161 +++++++++++++++++++++++++-
fs/netfs/objects.c | 10 --
fs/netfs/write_issue.c | 4 +-
fs/nfs/fscache.c | 5 +-
fs/nfs/fscache.h | 2 -
fs/smb/client/file.c | 3 +-
fs/squashfs/inode.c | 7 +-
include/linux/file.h | 2 +-
include/linux/fs.h | 5 +
include/linux/netfs.h | 3 -
include/trace/events/netfs.h | 2 +
include/uapi/linux/nsfs.h | 3 +-
kernel/fork.c | 25 +++-
25 files changed, 412 insertions(+), 71 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-07-27 9:05 Christian Brauner
2024-07-27 22:37 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-07-27 9:05 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains two fixes for this merge window:
VFS:
- I noticed that it is possible for a privileged user to mount most filesystems
with a non-initial user namespace in sb->s_user_ns. When fsopen() is called
in a non-init namespace the caller's namespace is recorded in
fs_context->user_ns. If the returned file descriptor is then passed to a
process privileged in init_user_ns, that process can call
fsconfig(fd_fs, FSCONFIG_CMD_CREATE*), creating a new superblock with
sb->s_user_ns set to the namespace of the process which called fsopen().
This is problematic as only filesystems that raise FS_USERNS_MOUNT are known
to be able to support a non-initial s_user_ns. Others may suffer security
issues, on-disk corruption or outright crash the kernel. Prevent that by
restricting such delegation to filesystems that allow FS_USERNS_MOUNT.
Note, that this delegation requires a privileged process to actually create
the superblock so either the privileged process is cooperaing or someone must
have tricked a privileged process into operating on a fscontext file
descriptor whose origin it doesn't know (a stupid idea).
The bug dates back to about 5 years afaict.
misc:
- Fix hostfs parsing when the mount request comes in via the legacy mount api.
In the legacy mount api hostfs allows to specify the host directory mount
without any key. Restore that behavior.
/* Testing */
clang: Debian clang version 16.0.6 (27)
gcc: (Debian 13.2.0-25) 13.2.0
/* Conflicts */
No known conflicts.
The following changes since commit c33ffdb70cc6df4105160f991288e7d2567d7ffa:
Merge tag 'phy-for-6.11' of git://git.kernel.org/pub/scm/linux/kernel/git/phy/linux-phy (2024-07-24 13:11:28 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.11-rc1.fixes.3
for you to fetch changes up to ef9ca17ca458ac7253ae71b552e601e49311fc48:
hostfs: fix the host directory parse when mounting. (2024-07-27 09:56:33 +0200)
Please consider pulling these changes from the signed vfs-6.11-rc1.fixes.3 tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.11-rc1.fixes.3
----------------------------------------------------------------
Hongbo Li (1):
hostfs: fix the host directory parse when mounting.
Seth Forshee (DigitalOcean) (1):
fs: don't allow non-init s_user_ns for filesystems without FS_USERNS_MOUNT
fs/hostfs/hostfs_kern.c | 65 +++++++++++++++++++++++++++++++++++++++++--------
fs/super.c | 11 +++++++++
2 files changed, 66 insertions(+), 10 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-07-24 9:19 Christian Brauner
2024-07-24 17:19 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-07-24 9:19 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains fixes for this merge window:
VFS:
- The new 64bit mount ids start after the old mount id, i.e., at the first
non-32 bit value. However, we started counting one id too late and thus lost
4294967296 as the first valid id. Fix that.
- Update a few comments on some vfs_*() creation helpers.
- Move copying of the xattr name out from the locks required to start a
filesystem write.
- Extend the filelock lock UAF fix to the compat code as well.
- Now that we added the ability to look up an inode under RCU it's possible
that lockless hash lookup can find and lock an inode after it gets I_FREEING
set. It then waits until inode teardown in evict() is finished.
The flag however is still set after evict() has woken up all waiters. If the
inode lock is taken late enough on the waiting side after hash removal and
wakeup happened the waiting thread will never be woken.
Before RCU based lookup this was synchronized via the inode_hash_lock. But
since unhashing requires the inode lock as well we can check whether the
inode is unhashed while holding inode lock even without holding
inode_hash_lock.
pidfd:
- The nsproxy structure contains nearly all of the namespaces associated with a
task. When a namespace type isn't supported nsproxy might contain a NULL
pointer or always point to the initial namespace type. The logic isn't
consistent. So when deriving namespace fds we need to ensure that the
namespace type is supported.
First, so that we don't risk dereferncing NULL pointers. The correct bigger
fix would be to change all namespaces to always set a valid namespace pointer
in struct nsproxy independent of whether or not it is compiled in. But that
requires quite a few changes.
Second, so that we don't allow deriving namespace fds when the namespace type
doesn't exist and thus when they couldn't also be derived via /proc/self/ns/.
- Add missing selftests for the new pidfd ioctls to derive namespace fds. This
simply extends the already existing testsuite.
netfs:
- Fix debug logging and fix kconfig variable name so it actually works.
- Fix writeback that goes both to the server and cache. The streams are only
activated once a subreq is added. When a server write happens the subreq
doesn't need to have finished by the time the cache write is started. If the
server write has already finished by the time the cache write is about to
start the cache write will operate on a folio that might already have been
reused. Fix this by preactivating the cache write.
- Limit cachefiles subreq size for cache writes to MAX_RW_COUNT.
The following changes since commit 933069701c1b507825b514317d4edd5d3fd9d417:
Merge tag '6.11-rc-smb3-server-fixes' of git://git.samba.org/ksmbd (2024-07-21 20:50:39 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.11-rc1.fixes.2
for you to fetch changes up to f5e5e97c719d289025afce07050effcf1f7373ef:
inode: clarify what's locked (2024-07-24 11:11:40 +0200)
Please consider pulling these changes from the signed vfs-6.11-rc1.fixes.2 tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.11-rc1.fixes.2
----------------------------------------------------------------
Christian Brauner (4):
pidfs: handle kernels without namespaces cleanly
pidfs: add selftests for new namespace ioctls
fs: use all available ids
inode: clarify what's locked
Congjie Zhou (1):
vfs: correct the comments of vfs_*() helpers
David Howells (5):
netfs: Revert "netfs: Switch debug logging to pr_debug()"
netfs: Rename CONFIG_FSCACHE_DEBUG to CONFIG_NETFS_DEBUG
netfs: Fix writeback that needs to go to both server and cache
cachefiles: Set the max subreq size for cache writes to MAX_RW_COUNT
vfs: Fix potential circular locking through setxattr() and removexattr()
Edward Adam Davis (1):
pidfs: when time ns disabled add check for ioctl
Jann Horn (1):
filelock: Fix fcntl/close race recovery compat path
Mateusz Guzik (1):
vfs: handle __wait_on_freeing_inode() and evict() race
fs/cachefiles/io.c | 2 +-
fs/inode.c | 40 +++-
fs/locks.c | 9 +-
fs/namei.c | 26 +--
fs/namespace.c | 2 +-
fs/netfs/Kconfig | 18 +-
fs/netfs/buffered_read.c | 14 +-
fs/netfs/buffered_write.c | 12 +-
fs/netfs/direct_read.c | 2 +-
fs/netfs/direct_write.c | 8 +-
fs/netfs/fscache_cache.c | 4 +-
fs/netfs/fscache_cookie.c | 28 +--
fs/netfs/fscache_io.c | 12 +-
fs/netfs/fscache_main.c | 2 +-
fs/netfs/fscache_volume.c | 4 +-
fs/netfs/internal.h | 33 ++-
fs/netfs/io.c | 12 +-
fs/netfs/main.c | 4 +
fs/netfs/misc.c | 4 +-
fs/netfs/write_collect.c | 16 +-
fs/netfs/write_issue.c | 37 ++--
fs/pidfs.c | 63 ++++--
fs/xattr.c | 91 ++++----
tools/testing/selftests/pidfd/pidfd_setns_test.c | 258 ++++++++++++++++++++---
24 files changed, 488 insertions(+), 213 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-07-18 9:01 Christian Brauner
2024-07-19 1:04 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-07-18 9:01 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains fixes for this merge window:
- Fix a missing rcu_read_unlock() in nsfs by switching to a cleanup guard.
- Add missing module descriptor for adfs.
/* Testing */
clang: Debian clang version 16.0.6 (27)
gcc: (Debian 13.2.0-25) 13.2.0
/* Conflicts */
No known conflicts.
The following changes since commit b1bc554e009e3aeed7e4cfd2e717c7a34a98c683:
Merge tag 'media/v6.11-1' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media (2024-07-17 18:30:10 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.11-rc1.fixes
for you to fetch changes up to 280e36f0d5b997173d014c07484c03a7f7750668:
nsfs: use cleanup guard (2024-07-18 09:50:08 +0200)
Please consider pulling these changes from the signed vfs-6.11-rc1.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.11-rc1.fixes
----------------------------------------------------------------
Christian Brauner (1):
nsfs: use cleanup guard
Jeff Johnson (1):
fs/adfs: add MODULE_DESCRIPTION
fs/adfs/super.c | 1 +
fs/nsfs.c | 6 +++---
2 files changed, 4 insertions(+), 3 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-07-11 5:09 Christian Brauner
2024-07-11 19:24 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-07-11 5:09 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
/* Summary */
This contains fixes for this merge window:
cachefiles:
- Export an existing and add a new cachefile helper to be used in filesystems
to fix reference count bugs.
- Use the newly added fscache_ty_get_volume() helper to get a reference count
on an fscache_volume to handle volumes that are about to be removed cleanly.
- After withdrawing a fscache_cache via FSCACHE_CACHE_IS_WITHDRAWN wait for all
ongoing cookie lookups to complete and for the object count to reach zero.
- Propagate errors from vfs_getxattr() to avoid an infinite loop in
cachefiles_check_volume_xattr() because it keeps seeing ESTALE.
- Don't send new requests when an object is dropped by raising
CACHEFILES_ONDEMAND_OJBSTATE_DROPPING.
- Cancel all requests for an object that is about to be dropped.
- Wait for the ondemand_boject_worker to finish before dropping a cachefiles
object to prevent use-after-free.
- Use cyclic allocation for message ids to better handle id recycling.
- Add missing lock protection when iterating through the xarray when polling.
netfs:
- Use standard logging helpers for debug logging.
VFS:
- Fix potential use-after-free in file locks during trace_posix_lock_inode().
The tracepoint could fire while another task raced it and freed the lock that
was requested to be traced.
- Only increment the nr_dentry_negative counter for dentries that are present
on the superblock LRU. Currently, DCACHE_LRU_LIST list is used to detect this
case. However, the flag is also raised in combination with DCACHE_SHRINK_LIST
to indicate that dentry->d_lru is used. So checking only DCACHE_LRU_LIST will
lead to wrong nr_dentry_negative count. Fix the check to not count dentries
that are on a shrink related list.
Misc:
- hfsplus: fix an uninitialized value issue in copy_name.
- minix: fix minixfs_rename with HIGHMEM. It still uses kunmap() even though we
switched it to kmap_local_page() a while ago.
/* Testing */
clang: Debian clang version 16.0.6 (27)
gcc: (Debian 13.2.0-25) 13.2.0
All patches are based on v6.10-rc6. No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 22a40d14b572deb80c0648557f4bd502d7e83826:
Linux 6.10-rc6 (2024-06-30 14:40:44 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.10-rc8.fixes
for you to fetch changes up to 3d1bec293378700dddc087d4d862306702276c23:
minixfs: Fix minixfs_rename with HIGHMEM (2024-07-10 07:15:36 +0200)
Please consider pulling these changes from the signed vfs-6.10-rc8.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.10-rc8.fixes
----------------------------------------------------------------
Baokun Li (7):
netfs, fscache: export fscache_put_volume() and add fscache_try_get_volume()
cachefiles: fix slab-use-after-free in fscache_withdraw_volume()
cachefiles: fix slab-use-after-free in cachefiles_withdraw_cookie()
cachefiles: propagate errors from vfs_getxattr() to avoid infinite loop
cachefiles: stop sending new request when dropping object
cachefiles: cancel all requests for the object that is being dropped
cachefiles: cyclic allocation of msg_id to avoid reuse
Brian Foster (1):
vfs: don't mod negative dentry count when on shrinker list
Christian Brauner (1):
Merge patch series "cachefiles: random bugfixes"
Edward Adam Davis (1):
hfsplus: fix uninit-value in copy_name
Hou Tao (1):
cachefiles: wait for ondemand_object_worker to finish when dropping object
Jeff Layton (1):
filelock: fix potential use-after-free in posix_lock_inode
Jingbo Xu (1):
cachefiles: add missing lock protection when polling
Matthew Wilcox (Oracle) (1):
minixfs: Fix minixfs_rename with HIGHMEM
Uwe Kleine-König (1):
netfs: Switch debug logging to pr_debug()
fs/cachefiles/cache.c | 45 +++++++++++++++++++++++++++++++++++-
fs/cachefiles/daemon.c | 4 ++--
fs/cachefiles/internal.h | 3 +++
fs/cachefiles/ondemand.c | 52 +++++++++++++++++++++++++++++++++++++-----
fs/cachefiles/volume.c | 1 -
fs/cachefiles/xattr.c | 5 +++-
fs/dcache.c | 12 +++++++---
fs/hfsplus/xattr.c | 2 +-
fs/locks.c | 2 +-
fs/minix/namei.c | 3 +--
fs/netfs/buffered_read.c | 14 ++++++------
fs/netfs/buffered_write.c | 12 +++++-----
fs/netfs/direct_read.c | 2 +-
fs/netfs/direct_write.c | 8 +++----
fs/netfs/fscache_cache.c | 4 ++--
fs/netfs/fscache_cookie.c | 28 +++++++++++------------
fs/netfs/fscache_io.c | 12 +++++-----
fs/netfs/fscache_main.c | 2 +-
fs/netfs/fscache_volume.c | 18 +++++++++++++--
fs/netfs/internal.h | 35 +---------------------------
fs/netfs/io.c | 12 +++++-----
fs/netfs/main.c | 4 ----
fs/netfs/misc.c | 4 ++--
fs/netfs/write_collect.c | 16 ++++++-------
fs/netfs/write_issue.c | 36 ++++++++++++++---------------
include/linux/fscache-cache.h | 6 +++++
include/trace/events/fscache.h | 4 ++++
27 files changed, 213 insertions(+), 133 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-07-02 19:44 Christian Brauner
2024-07-02 20:56 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-07-02 19:44 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains three fixes:
VFS:
- Improve handling of deep ancestor chains in is_subdir().
- Release locks cleanly when fctnl_setlk() races with close().
When setting a file lock fails the VFS tries to cleanup the already
created lock. The helper used for this calls back into the LSM layer
which may cause it to fail, leaving the lock accessible via
/proc/locks.
AFS:
- Fix a comma/semicolon typo.
/* Testing */
clang: Debian clang version 16.0.6 (27)
gcc: (Debian 13.2.0-25) 13.2.0
All patches are based on v6.10-rc6. No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 22a40d14b572deb80c0648557f4bd502d7e83826:
Linux 6.10-rc6 (2024-06-30 14:40:44 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.10-rc7.fixes.2
for you to fetch changes up to 655593a40efc577edc651f1d5c5dfde83367c477:
afs: Convert comma to semicolon (2024-07-02 21:23:00 +0200)
Please consider pulling these changes from the signed vfs-6.10-rc7.fixes.2 tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.10-rc7.fixes.2
----------------------------------------------------------------
Chen Ni (1):
afs: Convert comma to semicolon
Christian Brauner (1):
fs: better handle deep ancestor chains in is_subdir()
Jann Horn (1):
filelock: Remove locks reliably when fcntl/close race is detected
fs/afs/inode.c | 4 ++--
fs/dcache.c | 31 ++++++++++++++-----------------
fs/locks.c | 9 ++++-----
3 files changed, 20 insertions(+), 24 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-07-01 11:53 Christian Brauner
2024-07-01 16:49 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-07-01 11:53 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains fixes for this merge window:
Misc:
- Don't misleadingly warn during filesystem thaw operations. It's possible that
a block device which was frozen before it was mounted can cause a failing
thaw operation if someone concurrently tried to mount it while that thaw
operation was issued and the device had already been temporarily claimed for
the mount (The mount will of course be aborted because the device is frozen).
netfs:
- Fix io_uring based write-through. Make sure that the total request length is
correctly set.
- Fix partial writes to folio tail.
- Remove some xarray helpers that were intended for bounce buffers which got
defered to a later patch series.
- Make netfs_page_mkwrite() whether folio->mapping is vallid after acquiring
the folio lock.
- Make netfs_page_mkrite() flush conflicting data instead of waiting.
fsnotify:
- Ensure that fsnotify creation events are generated before fsnotify open
events when a file is created via ->atomic_open(). The ordering was broken
before.
- Ensure that no fsnotify events are generated for O_PATH file descriptors.
While no fsnotify open events were generated, fsnotify close events were.
Make it consistent and don't produce any.
/* Testing */
clang: Debian clang version 16.0.6 (27)
gcc: (Debian 13.2.0-25) 13.2.0
All patches are based on v6.10-rc3. No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 83a7eefedc9b56fe7bfeff13b6c7356688ffa670:
Linux 6.10-rc3 (2024-06-09 14:19:43 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.10-rc7.fixes
for you to fetch changes up to 9d66154f73b7c7007c3be1113dfb50b99b791f8f:
netfs: Fix netfs_page_mkwrite() to flush conflicting data, not wait (2024-06-26 14:19:08 +0200)
Please consider pulling these changes from the signed vfs-6.10-rc7.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.10-rc7.fixes
----------------------------------------------------------------
Christian Brauner (1):
fs: don't misleadingly warn during thaw operations
David Howells (5):
netfs: Fix io_uring based write-through
netfs: Fix early issue of write op on partial write to folio tail
netfs: Delete some xarray-wangling functions that aren't used
netfs: Fix netfs_page_mkwrite() to check folio->mapping is valid
netfs: Fix netfs_page_mkwrite() to flush conflicting data, not wait
Jan Kara (1):
fsnotify: Do not generate events for O_PATH file descriptors
NeilBrown (1):
vfs: generate FS_CREATE before FS_OPEN when ->atomic_open used.
fs/namei.c | 10 ++++--
fs/netfs/buffered_write.c | 12 +++++--
fs/netfs/direct_write.c | 3 +-
fs/netfs/internal.h | 9 ------
fs/netfs/misc.c | 81 -----------------------------------------------
fs/netfs/write_issue.c | 2 +-
fs/open.c | 22 +++++++++----
fs/super.c | 11 ++++++-
include/linux/fsnotify.h | 8 ++++-
9 files changed, 52 insertions(+), 106 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-06-10 14:09 Christian Brauner
2024-06-11 19:15 ` Linus Torvalds
2024-06-11 23:42 ` pr-tracker-bot
0 siblings, 2 replies; 188+ messages in thread
From: Christian Brauner @ 2024-06-10 14:09 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains fixes for this merge window:
* Restore debugfs behavior of ignoring unknown mount options.
* Fix kernel doc for netfs_wait_for_oustanding_io().
* Remove unneeded fdtable.h include in cachefiles.
* Fix struct statx comment after new addition for this cycle.
* Fix data zeroing behavior when an extent spans the block that contains i_size.
* Restore i_size increasing in iomap_write_end() for now to avoid stale data
exposure on xfs with a realtime device.
* Fix a check in find_next_fd().
* Improve trace output for cachefiles_obj_{get,put}_ondemand_fd().
* Remove requests from the request list in cachefiles to prevent accessing
already freed requests.
* Fix UAF when issuing restore command while the daemon is still alive by
adding an additional reference count to cachefile requests.
* Fix UAF in cachefiles by grabbing a reference during xarray lookup with
xa_lock() held.
* Simplify error handling in cachefiles_ondemand_daemon_read().
* Add consistency checks to cachefiles read and open requests to avoid crashes.
* Add a spinlock to protect ondemand_id variable which is used to determine
whether an anonymous cachefiles fd has already been closed.
* Make on-demand reads for cachefiles killable allowing to handle broken
cachefiles daemon better.
* Flush all requests after the kernel has been marked dead via CACHEFILES_DEAD
to avoid hung-tasks.
* Ensure that closed requests are marked as such to avoid reusing them with a
reopen request.
* Defer fd_install() until after copy_to_user() succeeded in cachefiles and
thereby get rid of having to use close_fd().
* Ensure that anonymous cachefiles on-demand fds are reused while they are
valid to avoid pinning already freed cookies.
/* Testing */
clang: Debian clang version 16.0.6 (27)
gcc: (Debian 13.2.0-25) 13.2.0
All patches are based on mainline. No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 2bfcfd584ff5ccc8bb7acde19b42570414bf880b:
Merge tag 'pmdomain-v6.10-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/linux-pm (2024-05-27 08:18:31 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.10-rc4.fixes
for you to fetch changes up to f5ceb1bbc98c69536d4673a97315e8427e67de1b:
iomap: Fix iomap_adjust_read_range for plen calculation (2024-06-05 17:27:03 +0200)
Please consider pulling these changes from the signed vfs-6.10-rc4.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.10-rc4.fixes
----------------------------------------------------------------
Baokun Li (11):
cachefiles: add output string to cachefiles_obj_[get|put]_ondemand_fd
cachefiles: remove requests from xarray during flushing requests
cachefiles: fix slab-use-after-free in cachefiles_ondemand_get_fd()
cachefiles: fix slab-use-after-free in cachefiles_ondemand_daemon_read()
cachefiles: remove err_put_fd label in cachefiles_ondemand_daemon_read()
cachefiles: add consistency check for copen/cread
cachefiles: add spin_lock for cachefiles_ondemand_info
cachefiles: never get a new anonymous fd if ondemand_id is valid
cachefiles: defer exposing anon_fd until after copy_to_user() succeeds
cachefiles: flush all requests after setting CACHEFILES_DEAD
cachefiles: make on-demand read killable
Christian Brauner (3):
debugfs: continue to ignore unknown mount options
netfs: fix kernel doc for nets_wait_for_outstanding_io()
Merge patch series "cachefiles: some bugfixes and cleanups for ondemand requests"
Gao Xiang (1):
cachefiles: remove unneeded include of <linux/fdtable.h>
John Garry (1):
statx: Update offset commentary for struct statx
Ritesh Harjani (IBM) (1):
iomap: Fix iomap_adjust_read_range for plen calculation
Yuntao Wang (1):
fs/file: fix the check in find_next_fd()
Zhang Yi (1):
iomap: keep on increasing i_size in iomap_write_end()
Zizhi Wo (1):
cachefiles: Set object to close if ondemand_id < 0 in copen
fs/cachefiles/daemon.c | 3 +-
fs/cachefiles/internal.h | 5 +
fs/cachefiles/ondemand.c | 218 ++++++++++++++++++++++++++++----------
fs/debugfs/inode.c | 10 +-
fs/file.c | 4 +-
fs/iomap/buffered-io.c | 56 +++++-----
include/linux/netfs.h | 2 +-
include/trace/events/cachefiles.h | 8 +-
include/uapi/linux/stat.h | 2 +-
9 files changed, 215 insertions(+), 93 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2024-06-10 14:09 Christian Brauner
@ 2024-06-11 19:15 ` Linus Torvalds
2024-06-12 11:30 ` Christian Brauner
2024-06-11 23:42 ` pr-tracker-bot
1 sibling, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2024-06-11 19:15 UTC (permalink / raw)
To: Christian Brauner; +Cc: linux-fsdevel, linux-kernel
On Mon, 10 Jun 2024 at 07:10, Christian Brauner <brauner@kernel.org> wrote:
>
> This contains fixes for this merge window:
>
> * Restore debugfs behavior of ignoring unknown mount options.
[...]
Note: I organized this a bit differently to make it more obvious what
areas the fixes were to.
I tried to be careful, but I may have gotten it wrong.
I do like being able to read the merge messages and get more of a
"toplevel feel" for what changed, though, which is why I did it (as
opposed to it being a "list of details").
I'm mentioning this in the hopes that your generally excellent
summaries would be even more excellent in the future in case you agree
with my changed merge log.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2024-06-11 19:15 ` Linus Torvalds
@ 2024-06-12 11:30 ` Christian Brauner
0 siblings, 0 replies; 188+ messages in thread
From: Christian Brauner @ 2024-06-12 11:30 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-fsdevel, linux-kernel
On Tue, Jun 11, 2024 at 12:15:36PM -0700, Linus Torvalds wrote:
> On Mon, 10 Jun 2024 at 07:10, Christian Brauner <brauner@kernel.org> wrote:
> >
> > This contains fixes for this merge window:
> >
> > * Restore debugfs behavior of ignoring unknown mount options.
> [...]
>
> Note: I organized this a bit differently to make it more obvious what
> areas the fixes were to.
>
> I tried to be careful, but I may have gotten it wrong.
Everything looks good to me!
>
> I do like being able to read the merge messages and get more of a
> "toplevel feel" for what changed, though, which is why I did it (as
> opposed to it being a "list of details").
>
> I'm mentioning this in the hopes that your generally excellent
> summaries would be even more excellent in the future in case you agree
> with my changed merge log.
Noted! I'll do that going forward!
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [GIT PULL] vfs fixes
2024-06-10 14:09 Christian Brauner
2024-06-11 19:15 ` Linus Torvalds
@ 2024-06-11 23:42 ` pr-tracker-bot
1 sibling, 0 replies; 188+ messages in thread
From: pr-tracker-bot @ 2024-06-11 23:42 UTC (permalink / raw)
To: Christian Brauner
Cc: Linus Torvalds, Christian Brauner, linux-fsdevel, linux-kernel
The pull request you sent on Mon, 10 Jun 2024 16:09:10 +0200:
> git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.10-rc4.fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2ef5971ff345d3c000873725db555085e0131961
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
^ permalink raw reply [flat|nested] 188+ messages in thread
* [GIT PULL] vfs fixes
@ 2024-05-27 11:55 Christian Brauner
2024-05-27 15:30 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-05-27 11:55 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few small fixes for this merge window:
* Fix io_uring based write-through after converting cifs to use the netfs
library.
* Fix aio error handling when doing write-through via netfs library.
* Fix performance regression in iomap when used with non-large folio mappings.
* Fix signalfd error code.
* Remove obsolete comment in signalfd code.
* Fix async request indication in netfs_perform_write() by raising BDP_ASYNC
when IOCB_NOWAIT is set.
* Yield swap device immediately to prevent spurious EBUSY errors.
* Don't cross a .backup mountpoint from backup volumes in afs to avoid infinite
loops.
* Fix a race between umount and async request completion in 9p after 9p was
converted to use the netfs library.
/* Testing */
clang: Debian clang version 16.0.6 (27)
gcc: (Debian 13.2.0-25) 13.2.0
All patches are based on mainline. No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 8f6a15f095a63a83b096d9b29aaff4f0fbe6f6e6:
Merge tag 'cocci-for-6.10' of git://git.kernel.org/pub/scm/linux/kernel/git/jlawall/linux (2024-05-20 16:00:04 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.10-rc2.fixes
for you to fetch changes up to f89ea63f1c65d3e93b255f14f9d9e05df87955fa:
netfs, 9p: Fix race between umount and async request completion (2024-05-27 13:12:13 +0200)
Please consider pulling these changes from the signed vfs-6.10-rc2.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.10-rc2.fixes
----------------------------------------------------------------
Christian Brauner (1):
swap: yield device immediately
David Howells (4):
netfs: Fix io_uring based write-through
netfs: Fix AIO error handling when doing write-through
netfs: Fix setting of BDP_ASYNC from iocb flags
netfs, 9p: Fix race between umount and async request completion
Fedor Pchelkin (2):
signalfd: fix error return code
signalfd: drop an obsolete comment
Marc Dionne (1):
afs: Don't cross .backup mountpoint from backup volume
Xu Yang (2):
filemap: add helper mapping_max_folio_size()
iomap: fault in smaller chunks for non-large folio mappings
fs/9p/vfs_inode.c | 1 +
fs/afs/inode.c | 1 +
fs/afs/mntpt.c | 5 +++++
fs/iomap/buffered-io.c | 2 +-
fs/netfs/buffered_write.c | 2 +-
fs/netfs/direct_write.c | 2 +-
fs/netfs/objects.c | 5 +++++
fs/netfs/write_collect.c | 7 ++++---
fs/netfs/write_issue.c | 9 +++++++--
fs/signalfd.c | 6 +-----
fs/smb/client/cifsfs.c | 1 +
include/linux/netfs.h | 18 ++++++++++++++++++
include/linux/pagemap.h | 34 +++++++++++++++++++++-------------
kernel/power/swap.c | 2 +-
14 files changed, 68 insertions(+), 27 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-04-26 14:59 Christian Brauner
2024-04-26 18:09 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-04-26 14:59 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few small fixes for this merge window and the attempt to handle
the ntfs removal regression that was reported a little while ago:
* After the removal of the legacy ntfs driver we received reports about
regressions for some people that do mount "ntfs" explicitly and expect the
driver to be available. Since ntfs3 is a drop-in for legacy ntfs we alias
legacy ntfs to ntfs3 just like ext3 is aliased to ext4.
We also enforce legacy ntfs is always mounted read-only and give it custom
file operations to ensure that ioctl()'s can't be abused to perform write
operations.
* Fix an unbalanced module_get() in bdev_open().
* Two smaller fixes for the netfs work done earlier in this cycle.
* Fix the errno returned from the new FS_IOC_GETUUID and FS_IOC_GETFSSYSFSPATH
ioctls. Both commands just pull information out of the superblock so there's
no need to call into the actual ioctl handlers.
So instead of returning ENOIOCTLCMD to indicate to fallback we just return
ENOTTY directly avoiding that indirection.
/* Testing */
clang: Debian clang version 16.0.6 (19)
gcc: (Debian 13.2.0-7) 13.2.0
All patches are based on v6.9-rc3. No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit fec50db7033ea478773b159e0e2efb135270e3b7:
Linux 6.9-rc3 (2024-04-07 13:22:46 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.9-rc6.fixes
for you to fetch changes up to c97f59e276d4e93480f29a70accbd0d7273cf3f5:
netfs: Fix the pre-flush when appending to a file in writethrough mode (2024-04-26 14:56:18 +0200)
Please consider pulling these changes from the signed vfs-6.9-rc6.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.9-rc6.fixes
----------------------------------------------------------------
Christian Brauner (3):
ntfs3: serve as alias for the legacy ntfs driver
ntfs3: enforce read-only when used as legacy ntfs driver
ntfs3: add legacy ntfs file operations
David Howells (2):
netfs: Fix writethrough-mode error handling
netfs: Fix the pre-flush when appending to a file in writethrough mode
Günther Noack (1):
fs: Return ENOTTY directly if FS_IOC_GETUUID or FS_IOC_GETFSSYSFSPATH fail
Yu Kuai (1):
block: fix module reference leakage from bdev_open_by_dev error path
block/bdev.c | 2 +-
fs/ioctl.c | 4 +--
fs/netfs/buffered_write.c | 23 +++++++++--------
fs/ntfs3/Kconfig | 9 +++++++
fs/ntfs3/dir.c | 7 +++++
fs/ntfs3/file.c | 8 ++++++
fs/ntfs3/inode.c | 20 ++++++++++++---
fs/ntfs3/ntfs_fs.h | 4 +++
fs/ntfs3/super.c | 65 ++++++++++++++++++++++++++++++++++++++++++++---
9 files changed, 121 insertions(+), 21 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-04-05 11:22 Christian Brauner
2024-04-05 17:09 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-04-05 11:22 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few small fixes. This comes with some delay because I
wanted to wait on people running their reproducers and the Easter
Holidays meant that those replies came in a little later than usual:
* Fix handling of preventing writes to mounted block devices.
Since last kernel we allow to prevent writing to mounted block devices
provided CONFIG_BLK_DEV_WRITE_MOUNTED isn't set and the block device
is opened with restricted writes. When we switched to opening block
devices as files we altered the mechanism by which we recognize when a
block device has been opened with write restrictions. The detection
logic assumed that only read-write mounted filesystems would apply
write restrictions to their block devices from other openers. That of
course is not true since it also makes sense to apply write
restrictions for filesystems that are read-only.
Fix the detection logic using an FMODE_* bit. We still have a few left
since we freed up a couple a while ago. I also picked up a patch to
free up four additional FMODE_* bits scheduled for the next merge window.
* Fix counting the number of writers to a block device. This just
changes the logic to be consistent.
* Fix a bug in aio causing a NULL pointer derefernce after we
implemented batched processing in aio.
* Finally, add the changes we discussed that allows to yield block
devices early even though file closing itself is deferred. This also
allows us to remove two holder operations to get and release the
holder to align lifetime of file and holder of the block device.
/* Testing */
clang: Debian clang version 16.0.6 (19)
gcc: (Debian 13.2.0-7) 13.2.0
All patches are based on v6.9-rc1 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.9-rc3.fixes
for you to fetch changes up to caeb4b0a11b3393e43f7fa8e0a5a18462acc66bd:
aio: Fix null ptr deref in aio_complete() wakeup (2024-04-05 11:20:28 +0200)
Please consider pulling these changes from the signed vfs-6.9-rc3.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.9-rc3.fixes
----------------------------------------------------------------
Christian Brauner (3):
block: handle BLK_OPEN_RESTRICT_WRITES correctly
block: count BLK_OPEN_RESTRICT_WRITES openers
fs,block: yield devices early
Kent Overstreet (1):
aio: Fix null ptr deref in aio_complete() wakeup
block/bdev.c | 84 ++++++++++++++++++++++++++++++++---------
drivers/mtd/devices/block2mtd.c | 2 +-
fs/aio.c | 2 +-
fs/bcachefs/super-io.c | 2 +-
fs/cramfs/inode.c | 2 +-
fs/ext4/super.c | 8 ++--
fs/f2fs/super.c | 2 +-
fs/jfs/jfs_logmgr.c | 4 +-
fs/reiserfs/journal.c | 2 +-
fs/romfs/super.c | 2 +-
fs/super.c | 24 ++----------
fs/xfs/xfs_buf.c | 2 +-
fs/xfs/xfs_super.c | 6 +--
include/linux/blkdev.h | 11 +-----
include/linux/fs.h | 2 +
15 files changed, 89 insertions(+), 66 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-03-18 12:19 Christian Brauner
2024-03-18 16:48 ` pr-tracker-bot
2024-03-18 19:14 ` Linus Torvalds
0 siblings, 2 replies; 188+ messages in thread
From: Christian Brauner @ 2024-03-18 12:19 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few small fixes for this merge window:
* Undo the hiding of silly-rename files in afs. If they're hidden they
can't be deleted by rm manually anymore causing regressions.
* Avoid caching the preferred address for an afs server to avoid
accidently overriding an explicitly specified preferred server address.
* Fix bad stat() and rmdir() interaction in afs.
* Take a passive reference on the superblock when opening a block device
so the holder is available to concurrent callers from the block layer.
* Clear private data pointer in fscache_begin_operation() to avoid it
being falsely treated as valid.
/* Testing */
clang: Debian clang version 16.0.6 (19)
gcc: (Debian 13.2.0-7) 13.2.0
All patches are based on mainline and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 480e035fc4c714fb5536e64ab9db04fedc89e910:
Merge tag 'drm-next-2024-03-13' of https://gitlab.freedesktop.org/drm/kernel (2024-03-13 18:34:05 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.9-rc1.fixes
for you to fetch changes up to 449ac5514631dd9b9b66dd708dd5beb1428e2812:
fscache: Fix error handling in fscache_begin_operation() (2024-03-18 10:33:48 +0100)
Please consider pulling these changes from the signed vfs-6.9-rc1.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.9-rc1.fixes
----------------------------------------------------------------
Christian Brauner (1):
fs,block: get holder during claim
David Howells (4):
afs: Revert "afs: Hide silly-rename files from userspace"
afs: Don't cache preferred address
afs: Fix occasional rmdir-then-VNOVNODE with generic/011
fscache: Fix error handling in fscache_begin_operation()
block/bdev.c | 7 +++++++
fs/afs/dir.c | 10 ----------
fs/afs/rotate.c | 21 ++++-----------------
fs/afs/validation.c | 16 +++++++++-------
fs/netfs/fscache_io.c | 4 +++-
fs/super.c | 18 ++++++++++++++++++
include/linux/blkdev.h | 10 ++++++++++
7 files changed, 51 insertions(+), 35 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2024-03-18 12:19 Christian Brauner
@ 2024-03-18 16:48 ` pr-tracker-bot
2024-03-18 19:14 ` Linus Torvalds
1 sibling, 0 replies; 188+ messages in thread
From: pr-tracker-bot @ 2024-03-18 16:48 UTC (permalink / raw)
To: Christian Brauner
Cc: Linus Torvalds, Christian Brauner, linux-fsdevel, linux-kernel
The pull request you sent on Mon, 18 Mar 2024 13:19:54 +0100:
> git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.9-rc1.fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0a7b0acecea273c8816f4f5b0e189989470404cf
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [GIT PULL] vfs fixes
2024-03-18 12:19 Christian Brauner
2024-03-18 16:48 ` pr-tracker-bot
@ 2024-03-18 19:14 ` Linus Torvalds
2024-03-18 19:41 ` Linus Torvalds
1 sibling, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2024-03-18 19:14 UTC (permalink / raw)
To: Christian Brauner; +Cc: linux-fsdevel, linux-kernel
On Mon, 18 Mar 2024 at 05:20, Christian Brauner <brauner@kernel.org> wrote:
>
> * Take a passive reference on the superblock when opening a block device
> so the holder is available to concurrent callers from the block layer.
So I've pulled this, but I have to admit that I hate it.
The bdev "holder" logic is an abomination. And "struct blk_holder_ops"
is horrendous.
Afaik, we have exactly two cases of "struct blk_holder_ops" in the
whole kernel, and you edited one of them.
And the other one is in bcachefs, and is a completely empty one with
no actual ops, so I think that one shouldn't exist.
In other words, we have only *one* actual set of "holder ops". That
makes me suspicious in the first place.
Now, let's then look at that new "holder->put_holder" use. It has
_one_ single user too, which is bd_end_claim(), which is called from
one place, which is bdev_release(). Which in turn is called from
exactly one place, which is blkdev_release(). Which is the release
function for def_blk_fops. Which is called from __fput() on the last
release of the file.
Fine, fine, fine. So let's chase down *who* actually uses that single
"blk_holder_ops". And it turns out that it's used in three places:
fs/super.c, fs/ext4/super.c, and fs/xfs/xfs_super.c.
So in those three cases, it would be absolutely *wrong* if the
'holder' was anything but the super-block (because that's what the new
get/put functions require for any of this to work.
This all smells horribly bad to me. The code looks and acts like it is
some generic interface, but in reality it really isn't. Yes, bcachefs
seems to make up some random holder (it's a one-byte kmalloc that
isn't actually used), and a random holder op structure (it's empty, as
mentioned), but none of this makes any sense at all.
I get the feeling that the "get/put" operations should just be done in
the three places that currently use that 'fs_holder_ops'.
IOW, isn't the 'get()' always basically paired with the mounting? And
the 'put()' would probably be best done iin kill_block_super()?
I don't know. Maybe I missed something really important, but this
smells like a specific case that simply shouldn't have gotten this
kind of "generic infrastructure" solution.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2024-03-18 19:14 ` Linus Torvalds
@ 2024-03-18 19:41 ` Linus Torvalds
2024-03-19 6:58 ` Christian Brauner
0 siblings, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2024-03-18 19:41 UTC (permalink / raw)
To: Christian Brauner; +Cc: linux-fsdevel, linux-kernel
On Mon, 18 Mar 2024 at 12:14, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> IOW, isn't the 'get()' always basically paired with the mounting? And
> the 'put()' would probably be best done iin kill_block_super()?
.. or alternative handwavy approach:
The fundamental _reason_ for the ->get/put seems to be to make the
'holder' lifetime be at least as long as the 'struct file' it is
associated with. No?
So how about we just make the 'holder' always *be* a 'struct file *'? That
(a) gets rid of the typeless 'void *' part
(b) is already what it is for normal cases (ie O_EXCL file opens).
wouldn't it be lovely if we just made the rule be that 'holder' *is*
the file pointer, and got rid of a lot of typeless WTF code?
Again, this comment (and the previous email) is more based on "this
does not feel right to me" than anything else.
That code just makes my skin itch. I can't say it's _wrong_, but it
just FeelsWrongToMe(tm).
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2024-03-18 19:41 ` Linus Torvalds
@ 2024-03-19 6:58 ` Christian Brauner
2024-03-20 10:21 ` Christian Brauner
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-03-19 6:58 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-fsdevel, linux-kernel
On Mon, Mar 18, 2024 at 12:41:49PM -0700, Linus Torvalds wrote:
> On Mon, 18 Mar 2024 at 12:14, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > IOW, isn't the 'get()' always basically paired with the mounting? And
> > the 'put()' would probably be best done iin kill_block_super()?
>
> .. or alternative handwavy approach:
>
> The fundamental _reason_ for the ->get/put seems to be to make the
> 'holder' lifetime be at least as long as the 'struct file' it is
> associated with. No?
>
> So how about we just make the 'holder' always *be* a 'struct file *'? That
>
> (a) gets rid of the typeless 'void *' part
>
> (b) is already what it is for normal cases (ie O_EXCL file opens).
>
> wouldn't it be lovely if we just made the rule be that 'holder' *is*
> the file pointer, and got rid of a lot of typeless WTF code?
>
> Again, this comment (and the previous email) is more based on "this
> does not feel right to me" than anything else.
>
> That code just makes my skin itch. I can't say it's _wrong_, but it
> just FeelsWrongToMe(tm).
So, initially I think the holder ops were intended to be generic by
Christoph but I agree that it's probably not needed. I just didn't
massage that code yet. Now on my todo for this cycle!
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [GIT PULL] vfs fixes
2024-03-19 6:58 ` Christian Brauner
@ 2024-03-20 10:21 ` Christian Brauner
0 siblings, 0 replies; 188+ messages in thread
From: Christian Brauner @ 2024-03-20 10:21 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-fsdevel, linux-kernel
> > Again, this comment (and the previous email) is more based on "this
> > does not feel right to me" than anything else.
> >
> > That code just makes my skin itch. I can't say it's _wrong_, but it
> > just FeelsWrongToMe(tm).
>
> So, initially I think the holder ops were intended to be generic by
> Christoph but I agree that it's probably not needed. I just didn't
> massage that code yet. Now on my todo for this cycle!
So, the block holder ops will gain additional implementers in the block
layer that will implement their own separate ops. So I trust the block
layer with this.
The holder is used to determine whether a block device can be reopened.
So both for internal (mounting, log device initialization) or userspace
opens we compare the holders of the block device. We do have allowed for
quite some time to open the same block device exclusively with different
flags. So there are multiple files open to the same block device and the
holder is used as proof that it can be reopened. So always using the
file as the holder would still mean that we have to compare
file->private_data to determine whether the block device can be
reopened. So it won't get us as much as we'd want.
The reason for the holder to remain valid is that the block layer does
have ioctl operations such as removal of a device in the case of nbd,
suspend and resume used in stuff like cryptsetup. In all such cases we
go from arbitrary block device to arbitrary holder and then inform them
about the operation calling the appropriate callback. So we would still
have to guarantee the validity of the holder in file->private_data.
There are also two internal codepaths where the block device is
temporarly marked as being in the process of being claimed. This will
cause actual openers to wait until bd_holder is really set or aborted
but not fail the actual open. This has traditionally been the case in
the loop code and during user initiated and internally triggered
partition scanning. That could be reworked but would be pretty ugly.
We'll continue considering additional cleanups and latest next merge
window I'll give you a detailed write up what happened.
^ permalink raw reply [flat|nested] 188+ messages in thread
* [GIT PULL] vfs fixes
@ 2024-03-06 15:45 Christian Brauner
2024-03-06 16:33 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-03-06 15:45 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains three fixes:
* Get rid of copy_mc flag in iov_iter which really only makes sense for
the core dumping code so move it out of the generic iov iter code and
make it coredump's problem. See the detailed commit description.
* Revert fs/aio: Make io_cancel() generate completions again
The initial fix here was predicated on the assumption that calling
ki_cancel() didn't complete aio requests. However, that turned out to
be wrong since the two drivers that actually make use of this set
a cancellation function that performs the cancellation correctly.
So revert this change.
* Ensure that the test for IOCB_AIO_RW always happens before the read
from ki_ctx.
/* Testing */
clang: Debian clang version 16.0.6 (19)
gcc: (Debian 13.2.0-7) 13.2.0
All patches are based on v6.8-rc7 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit 90d35da658da8cff0d4ecbb5113f5fac9d00eb72:
Linux 6.8-rc7 (2024-03-03 13:02:52 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.8-release.fixes
for you to fetch changes up to a50026bdb867c8caf9d29e18f9fe9e1390312619:
iov_iter: get rid of 'copy_mc' flag (2024-03-06 10:52:12 +0100)
Please consider pulling these changes from the signed vfs-6.8-release.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.8-release.fixes
----------------------------------------------------------------
Bart Van Assche (2):
Revert "fs/aio: Make io_cancel() generate completions again"
fs/aio: Check IOCB_AIO_RW before the struct aio_kiocb conversion
Linus Torvalds (1):
iov_iter: get rid of 'copy_mc' flag
fs/aio.c | 35 ++++++++++++++++++++++-------------
fs/coredump.c | 45 ++++++++++++++++++++++++++++++++++++++++++---
include/linux/uio.h | 16 ----------------
lib/iov_iter.c | 23 -----------------------
4 files changed, 64 insertions(+), 55 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-03-01 12:45 Christian Brauner
2024-03-01 20:37 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-03-01 12:45 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains two small fixes:
* Fix an endless loop during afs directory iteration caused by not skipping
silly-rename files correctly.
* Fix reporting of completion events for aio causing leaks in userspace.
This is based on the fix last week as it's now possible to recognize
aio events submitted through the old aio interface.
/* Testing */
clang: Debian clang version 16.0.6 (19)
gcc: (Debian 13.2.0-7) 13.2.0
All patches are based on v6.8-rc6 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit d206a76d7d2726f3b096037f2079ce0bd3ba329b:
Linux 6.8-rc6 (2024-02-25 15:46:06 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.8-rc7.fixes
for you to fetch changes up to 54cbc058d86beca3515c994039b5c0f0a34f53dd:
fs/aio: Make io_cancel() generate completions again (2024-02-27 11:20:44 +0100)
----------------------------------------------------------------
vfs-6.8-rc7.fixes
----------------------------------------------------------------
Bart Van Assche (1):
fs/aio: Make io_cancel() generate completions again
David Howells (1):
afs: Fix endless loop in directory parsing
fs/afs/dir.c | 4 +++-
fs/aio.c | 27 +++++++++++----------------
2 files changed, 14 insertions(+), 17 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-02-22 14:03 Christian Brauner
2024-02-22 18:18 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-02-22 14:03 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few fixes:
* Fix a memory leak in cachefiles.
* Restrict aio cancellations to I/O submitted through the aio interfaces as
this is otherwise causing issues for I/O submitted via io_uring.
* Increase buffer for afs volume status to avoid overflow.
* Fix a missing zero-length check in unbuffered writes in the netfs library.
If generic_write_checks() returns zero make netfs_unbuffered_write_iter()
return right away.
* Prevent a leak in i_dio_count caused by netfs_begin_read() operaing pas
i_size. It will return early and leave i_dio_count incremented.
* Account for ipv4 addresses as well ass ipv6 addresses when processing
incoming callbacks in afs.
/* Testing */
clang: Debian clang version 16.0.6 (19)
gcc: (Debian 13.2.0-7) 13.2.0
All patches are based on v6.8-rc2 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:
Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.8-rc6.fixes
for you to fetch changes up to b820de741ae48ccf50dd95e297889c286ff4f760:
fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio (2024-02-21 16:31:49 +0100)
Please consider pulling these changes from the signed vfs-6.8-rc6.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.8-rc6.fixes
----------------------------------------------------------------
Baokun Li (1):
cachefiles: fix memory leak in cachefiles_add_cache()
Bart Van Assche (1):
fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio
Daniil Dulov (1):
afs: Increase buffer size in afs_update_volume_status()
David Howells (1):
netfs: Fix missing zero-length check in unbuffered write
Marc Dionne (2):
netfs: Fix i_dio_count leak on DIO read past i_size
afs: Fix ignored callbacks over ipv4
fs/afs/internal.h | 6 ++----
fs/afs/main.c | 3 +--
fs/afs/server.c | 14 +++++---------
fs/afs/volume.c | 4 ++--
fs/aio.c | 9 ++++++++-
fs/cachefiles/cache.c | 2 ++
fs/cachefiles/daemon.c | 1 +
fs/netfs/buffered_write.c | 3 +++
fs/netfs/direct_write.c | 5 ++++-
fs/netfs/io.c | 2 ++
include/linux/fs.h | 2 ++
11 files changed, 32 insertions(+), 19 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-02-12 13:00 Christian Brauner
2024-02-12 17:03 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-02-12 13:00 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains two small fixes:
* Fix performance regression introduced by moving the security permission hook
out of do_clone_file_range() and into its caller vfs_clone_file_range(). This
causes the security hook to be called in situation were it wasn't called
before as the fast permission checks were left in do_clone_file_range(). Fix
this by merging the two implementations back together and restoring the old
ordering: fast permission checks first, expensive ones later.
* Tweak mount_setattr() permission checking so that mount properties on the
real rootfs can be changed.
When we added mount_setattr() we added additional checks compared to legacy
mount(2). If the mouna had a parent then verify that the caller and the mount
namespace the mount is attached to match and if not make sure that it's an
anonymous mount.
But the real rootfs falls into neither category. It is neither an anoymous
mount because it is obviously attached to the initial mount namespace but it
also obviously doesn't have a parent mount. So that means legacy mount(2)
allows changing mount properties on the real rootfs but mount_setattr(2)
blocks this. This causes regressions (See the commit for details).
Fix this by relaxing the check. If the mount has a parent or if it isn't a
detached mount, verify that the mount namespaces of the caller and the mount
are the same. Technically, we could probably write this even simpler and
check that the mount namespaces match if it isn't a detached mount. But the
slightly longer check makes it clearer what conditions one needs to think
about.
/* Testing */
clang: Debian clang version 16.0.6 (19)
gcc: (Debian 13.2.0-7) 13.2.0
All patches are based on v6.8-rc1 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.8-rc5.fixes
for you to fetch changes up to 46f5ab762d048dad224436978315cbc2fa79c630:
fs: relax mount_setattr() permission checks (2024-02-07 21:16:29 +0100)
Please consider pulling these changes from the signed vfs-6.8-rc5.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.8-rc5.fixes
----------------------------------------------------------------
Amir Goldstein (1):
remap_range: merge do_clone_file_range() into vfs_clone_file_range()
Christian Brauner (1):
fs: relax mount_setattr() permission checks
fs/namespace.c | 11 ++++++++---
fs/overlayfs/copy_up.c | 14 ++++++--------
fs/remap_range.c | 31 +++++++++----------------------
include/linux/fs.h | 3 ---
4 files changed, 23 insertions(+), 36 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2024-01-13 12:31 Christian Brauner
2024-01-17 20:03 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2024-01-13 12:31 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains two fixes for the current merge window. The listmount changes
that you requested and a fix for a fsnotify performance regression:
* The proposed listmount changes are currently under my authorship. I wasn't
sure whether you'd wanted to be author as the patch wasn't signed off. If you
do I'm happy if you just apply your own patch.
I've tested the patch with my sh4 cross-build setup. And confirmed that a)
the build failure with sh on current upstream is reproducible and that b) the
proposed patch fixes the build failure. That should only leave the task of
fixing put_user on sh.
* The fsnotify regression was caused by moving one of the hooks out of the
security hook in preparation for other fsnotify work. This meant that
CONFIG_SECURITY would have compiled out the fsnotify hook before but didn't
do so now. That lead to up to 6% performance regression in some io_uring
workloads that compile all fsnotify and security checks out. Fix this by
making sure that the relevant hooks are covered by the already existing
CONFIG_FANOTIFY_ACCESS_PERMISSIONS where the relevant hook belongs.
/* Testing */
clang: Debian clang version 16.0.6 (19)
gcc: (Debian 13.2.0-7) 13.2.0
All patches are based on mainline as of yesterday. No build failures or
warnings were observed. I've successfully tested the changes to listmount with
the selftests we added.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit 70d201a40823acba23899342d62bc2644051ad2e:
Merge tag 'f2fs-for-6.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs (2024-01-11 20:39:15 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.8-rc1.fixes
for you to fetch changes up to ba5afb9a84df2e6b26a1b6389b98849cd16ea757:
fs: rework listmount() implementation (2024-01-13 13:06:25 +0100)
Please consider pulling these changes from the signed vfs-6.8-rc1.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.8-rc1.fixes
----------------------------------------------------------------
Amir Goldstein (1):
fsnotify: compile out fsnotify permission hooks if !FANOTIFY_ACCESS_PERMISSIONS
Christian Brauner (1):
fs: rework listmount() implementation
fs/namespace.c | 50 +++++++++++++++++++++++++++---------------------
include/linux/fsnotify.h | 19 ++++++++++++++++++
include/linux/syscalls.h | 2 +-
3 files changed, 48 insertions(+), 23 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2023-11-24 10:27 Christian Brauner
2023-11-24 18:25 ` Linus Torvalds
2023-11-24 18:26 ` pr-tracker-bot
0 siblings, 2 replies; 188+ messages in thread
From: Christian Brauner @ 2023-11-24 10:27 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains the usual miscellaneous fixes:
* Avoid calling back into LSMs from vfs_getattr_nosec() calls.
IMA used to query inode properties accessing raw inode fields without
dedicated helpers. That was finally fixed a few releases ago by
forcing IMA to use vfs_getattr_nosec() helpers.
The goal of the vfs_getattr_nosec() helper is to query for attributes
without calling into the LSM layer which would be quite problematic
because incredibly IMA is called from __fput()...
__fput()
-> ima_file_free()
What it does is to call back into the filesystem to update the file's
IMA xattr. Querying the inode without using vfs_getattr_nosec() meant
that IMA didn't handle stacking filesystems such as overlayfs
correctly. So the switch to vfs_getattr_nosec() is quite correct. But
the switch to vfs_getattr_nosec() revealed another bug when used on
stacking filesystems:
__fput()
-> ima_file_free()
-> vfs_getattr_nosec()
-> i_op->getattr::ovl_getattr()
-> vfs_getattr()
-> i_op->getattr::$WHATEVER_UNDERLYING_FS_getattr()
-> security_inode_getattr() # calls back into LSMs
Now, if that __fput() happens from task_work_run() of an exiting task
current->fs and various other pointer could already be NULL. So
anything in the LSM layer relying on that not being NULL would be
quite surprised.
Fix that by passing the information that this is a security request
through to the stacking filesystem by adding a new internal
ATT_GETATTR_NOSEC flag. Now the callchain becomes:
__fput()
-> ima_file_free()
-> vfs_getattr_nosec()
-> i_op->getattr::ovl_getattr()
-> if (AT_GETATTR_NOSEC)
vfs_getattr_nosec()
else
vfs_getattr()
-> i_op->getattr::$WHATEVER_UNDERLYING_FS_getattr()
* Fix a bug introduced with the iov_iter rework from last cycle.
This broke /proc/kcore by copying too much and without the correct
offset.
* Add a missing NULL check when allocating the root inode in
autofs_fill_super().
* Fix stable writes for multi-device filesystems (xfs, btrfs etc) and
the block device pseudo filesystem.
Stable writes used to be a superblock flag only, making it a per
filesystem property. Add an additional AS_STABLE_WRITES mapping flag
to allow for fine-grained control.
* Ensure that offset_iterate_dir() returns 0 after reaching the end of a
directory so it adheres to getdents() convention.
/* Testing */
clang: Debian clang version 16.0.6 (16)
gcc: gcc (Debian 13.2.0-5) 13.2.0
All patches are based on v6.7-rc1 and have been sitting in linux-next.
No build failures or warnings were observed. Passes xfstests.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.7-rc3.fixes
for you to fetch changes up to 796432efab1e372d404e7a71cc6891a53f105051:
libfs: getdents() should return 0 after reaching EOD (2023-11-20 15:34:22 +0100)
Please consider pulling these changes from the signed vfs-6.7-rc3.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.7-rc3.fixes
----------------------------------------------------------------
Christoph Hellwig (4):
filemap: add a per-mapping stable writes flag
block: update the stable_writes flag in bdev_add
xfs: clean up FS_XFLAG_REALTIME handling in xfs_ioctl_setattr_xflags
xfs: respect the stable writes flag on the RT device
Chuck Lever (1):
libfs: getdents() should return 0 after reaching EOD
Ian Kent (1):
autofs: add: new_inode check in autofs_fill_super()
Omar Sandoval (1):
iov_iter: fix copy_page_to_iter_nofault()
Stefan Berger (1):
fs: Pass AT_GETATTR_NOSEC flag to getattr interface function
block/bdev.c | 2 ++
fs/autofs/inode.c | 56 +++++++++++++++++-----------------------------
fs/ecryptfs/inode.c | 12 ++++++++--
fs/inode.c | 2 ++
fs/libfs.c | 14 +++++++++---
fs/overlayfs/inode.c | 10 ++++-----
fs/overlayfs/overlayfs.h | 8 +++++++
fs/stat.c | 6 ++++-
fs/xfs/xfs_inode.h | 8 +++++++
fs/xfs/xfs_ioctl.c | 30 ++++++++++++++++---------
fs/xfs/xfs_iops.c | 7 ++++++
include/linux/pagemap.h | 17 ++++++++++++++
include/uapi/linux/fcntl.h | 3 +++
lib/iov_iter.c | 2 +-
mm/page-writeback.c | 2 +-
15 files changed, 121 insertions(+), 58 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2023-11-24 10:27 Christian Brauner
@ 2023-11-24 18:25 ` Linus Torvalds
2023-11-24 18:52 ` Linus Torvalds
2023-11-25 13:10 ` Christian Brauner
2023-11-24 18:26 ` pr-tracker-bot
1 sibling, 2 replies; 188+ messages in thread
From: Linus Torvalds @ 2023-11-24 18:25 UTC (permalink / raw)
To: Christian Brauner, Omar Sandoval, David Howells
Cc: linux-fsdevel, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 2661 bytes --]
On Fri, 24 Nov 2023 at 02:28, Christian Brauner <brauner@kernel.org> wrote:
>
> * Fix a bug introduced with the iov_iter rework from last cycle.
>
> This broke /proc/kcore by copying too much and without the correct
> offset.
Ugh. I think the whole /proc/kcore vmalloc handling is just COMPLETELY broken.
It does this:
/*
* vmalloc uses spinlocks, so we optimistically try to
* read memory. If this fails, fault pages in and try
* again until we are done.
*/
while (true) {
read += vread_iter(iter, src, left);
if (read == tsz)
break;
src += read;
left -= read;
if (fault_in_iov_iter_writeable(iter, left)) {
ret = -EFAULT;
goto out;
}
}
and that is just broken beyond words for two totally independent reasons:
(a) vread_iter() looks like it can fail because of not having a
source, and return 0 (I dunno - it seems to try to avoid that, but it
all looks pretty dodgy)
At that point fault_in_iov_iter_writeable() will try to fault
in the destination, which may work just fine, but if the source was
the problem, you'd have an endless loop.
(b) That "read += X" is completely broken anyway. It should be just a
"=". So that whole loop is crazy broken, and only works for the case
where you get it all in one go. This code is crap.
Now, I think it all works in practice for one simple reason: I doubt
anybody uses this (and it looks like the callees in the while loop try
very hard to always fill the whole area - maybe people noticed the
first bug and tried to work around it that way).
I guess there is at least one test program, but it presumably doesn't
trigger or care about the bugs here.
But I think we can get rid of this all, and just deal with the
KCORE_VMALLOC case exactly the same way we already deal with VMEMMAP
and TEXT: by just doing copy_from_kernel_nofault() into a bounce
buffer, and then doing a regular _copy_to_iter() or whatever.
NOTE! I looked at the code, and threw up in my mouth a little, and
maybe I missed something. Maybe it all works fine. But Omar - since
you found the original problem, may I implore you to test this
attached patch?
I just like how the patch looks:
6 files changed, 1 insertion(+), 368 deletions(-)
and those 350+ deleted lines really looked disgusting to me.
This patch is on top of the pull I did, because obviously the fix in
that pull was correct, I just think we should go further and get rid
of this whole mess entirely.
Linus
[-- Attachment #2: patch.diff --]
[-- Type: text/x-patch, Size: 11981 bytes --]
fs/proc/kcore.c | 26 +----
include/linux/uio.h | 3 -
include/linux/vmalloc.h | 3 -
lib/iov_iter.c | 33 ------
mm/nommu.c | 9 --
mm/vmalloc.c | 295 ------------------------------------------------
6 files changed, 1 insertion(+), 368 deletions(-)
diff --git a/fs/proc/kcore.c b/fs/proc/kcore.c
index 6422e569b080..83a39f4d1ddc 100644
--- a/fs/proc/kcore.c
+++ b/fs/proc/kcore.c
@@ -504,31 +504,6 @@ static ssize_t read_kcore_iter(struct kiocb *iocb, struct iov_iter *iter)
}
switch (m->type) {
- case KCORE_VMALLOC:
- {
- const char *src = (char *)start;
- size_t read = 0, left = tsz;
-
- /*
- * vmalloc uses spinlocks, so we optimistically try to
- * read memory. If this fails, fault pages in and try
- * again until we are done.
- */
- while (true) {
- read += vread_iter(iter, src, left);
- if (read == tsz)
- break;
-
- src += read;
- left -= read;
-
- if (fault_in_iov_iter_writeable(iter, left)) {
- ret = -EFAULT;
- goto out;
- }
- }
- break;
- }
case KCORE_USER:
/* User page is handled prior to normal kernel page: */
if (copy_to_iter((char *)start, tsz, iter) != tsz) {
@@ -555,6 +530,7 @@ static ssize_t read_kcore_iter(struct kiocb *iocb, struct iov_iter *iter)
break;
}
fallthrough;
+ case KCORE_VMALLOC:
case KCORE_VMEMMAP:
case KCORE_TEXT:
/*
diff --git a/include/linux/uio.h b/include/linux/uio.h
index b6214cbf2a43..993a6bd8bdd3 100644
--- a/include/linux/uio.h
+++ b/include/linux/uio.h
@@ -187,9 +187,6 @@ static inline size_t copy_folio_from_iter_atomic(struct folio *folio,
return copy_page_from_iter_atomic(&folio->page, offset, bytes, i);
}
-size_t copy_page_to_iter_nofault(struct page *page, unsigned offset,
- size_t bytes, struct iov_iter *i);
-
static __always_inline __must_check
size_t copy_to_iter(const void *addr, size_t bytes, struct iov_iter *i)
{
diff --git a/include/linux/vmalloc.h b/include/linux/vmalloc.h
index c720be70c8dd..f8885045f4d2 100644
--- a/include/linux/vmalloc.h
+++ b/include/linux/vmalloc.h
@@ -247,9 +247,6 @@ static inline void set_vm_flush_reset_perms(void *addr)
}
#endif
-/* for /proc/kcore */
-extern long vread_iter(struct iov_iter *iter, const char *addr, size_t count);
-
/*
* Internals. Don't use..
*/
diff --git a/lib/iov_iter.c b/lib/iov_iter.c
index 8ff6824a1005..6d2b79973622 100644
--- a/lib/iov_iter.c
+++ b/lib/iov_iter.c
@@ -394,39 +394,6 @@ size_t copy_page_to_iter(struct page *page, size_t offset, size_t bytes,
}
EXPORT_SYMBOL(copy_page_to_iter);
-size_t copy_page_to_iter_nofault(struct page *page, unsigned offset, size_t bytes,
- struct iov_iter *i)
-{
- size_t res = 0;
-
- if (!page_copy_sane(page, offset, bytes))
- return 0;
- if (WARN_ON_ONCE(i->data_source))
- return 0;
- page += offset / PAGE_SIZE; // first subpage
- offset %= PAGE_SIZE;
- while (1) {
- void *kaddr = kmap_local_page(page);
- size_t n = min(bytes, (size_t)PAGE_SIZE - offset);
-
- n = iterate_and_advance(i, n, kaddr + offset,
- copy_to_user_iter_nofault,
- memcpy_to_iter);
- kunmap_local(kaddr);
- res += n;
- bytes -= n;
- if (!bytes || !n)
- break;
- offset += n;
- if (offset == PAGE_SIZE) {
- page++;
- offset = 0;
- }
- }
- return res;
-}
-EXPORT_SYMBOL(copy_page_to_iter_nofault);
-
size_t copy_page_from_iter(struct page *page, size_t offset, size_t bytes,
struct iov_iter *i)
{
diff --git a/mm/nommu.c b/mm/nommu.c
index b6dc558d3144..1612b3a601fd 100644
--- a/mm/nommu.c
+++ b/mm/nommu.c
@@ -199,15 +199,6 @@ unsigned long vmalloc_to_pfn(const void *addr)
}
EXPORT_SYMBOL(vmalloc_to_pfn);
-long vread_iter(struct iov_iter *iter, const char *addr, size_t count)
-{
- /* Don't allow overflow */
- if ((unsigned long) addr + count < count)
- count = -(unsigned long) addr;
-
- return copy_to_iter(addr, count, iter);
-}
-
/*
* vmalloc - allocate virtually contiguous memory
*
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index d12a17fc0c17..79889a10e18d 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -802,31 +802,6 @@ unsigned long vmalloc_nr_pages(void)
return atomic_long_read(&nr_vmalloc_pages);
}
-/* Look up the first VA which satisfies addr < va_end, NULL if none. */
-static struct vmap_area *find_vmap_area_exceed_addr(unsigned long addr)
-{
- struct vmap_area *va = NULL;
- struct rb_node *n = vmap_area_root.rb_node;
-
- addr = (unsigned long)kasan_reset_tag((void *)addr);
-
- while (n) {
- struct vmap_area *tmp;
-
- tmp = rb_entry(n, struct vmap_area, rb_node);
- if (tmp->va_end > addr) {
- va = tmp;
- if (tmp->va_start <= addr)
- break;
-
- n = n->rb_left;
- } else
- n = n->rb_right;
- }
-
- return va;
-}
-
static struct vmap_area *__find_vmap_area(unsigned long addr, struct rb_root *root)
{
struct rb_node *n = root->rb_node;
@@ -3562,276 +3537,6 @@ void *vmalloc_32_user(unsigned long size)
}
EXPORT_SYMBOL(vmalloc_32_user);
-/*
- * Atomically zero bytes in the iterator.
- *
- * Returns the number of zeroed bytes.
- */
-static size_t zero_iter(struct iov_iter *iter, size_t count)
-{
- size_t remains = count;
-
- while (remains > 0) {
- size_t num, copied;
-
- num = min_t(size_t, remains, PAGE_SIZE);
- copied = copy_page_to_iter_nofault(ZERO_PAGE(0), 0, num, iter);
- remains -= copied;
-
- if (copied < num)
- break;
- }
-
- return count - remains;
-}
-
-/*
- * small helper routine, copy contents to iter from addr.
- * If the page is not present, fill zero.
- *
- * Returns the number of copied bytes.
- */
-static size_t aligned_vread_iter(struct iov_iter *iter,
- const char *addr, size_t count)
-{
- size_t remains = count;
- struct page *page;
-
- while (remains > 0) {
- unsigned long offset, length;
- size_t copied = 0;
-
- offset = offset_in_page(addr);
- length = PAGE_SIZE - offset;
- if (length > remains)
- length = remains;
- page = vmalloc_to_page(addr);
- /*
- * To do safe access to this _mapped_ area, we need lock. But
- * adding lock here means that we need to add overhead of
- * vmalloc()/vfree() calls for this _debug_ interface, rarely
- * used. Instead of that, we'll use an local mapping via
- * copy_page_to_iter_nofault() and accept a small overhead in
- * this access function.
- */
- if (page)
- copied = copy_page_to_iter_nofault(page, offset,
- length, iter);
- else
- copied = zero_iter(iter, length);
-
- addr += copied;
- remains -= copied;
-
- if (copied != length)
- break;
- }
-
- return count - remains;
-}
-
-/*
- * Read from a vm_map_ram region of memory.
- *
- * Returns the number of copied bytes.
- */
-static size_t vmap_ram_vread_iter(struct iov_iter *iter, const char *addr,
- size_t count, unsigned long flags)
-{
- char *start;
- struct vmap_block *vb;
- struct xarray *xa;
- unsigned long offset;
- unsigned int rs, re;
- size_t remains, n;
-
- /*
- * If it's area created by vm_map_ram() interface directly, but
- * not further subdividing and delegating management to vmap_block,
- * handle it here.
- */
- if (!(flags & VMAP_BLOCK))
- return aligned_vread_iter(iter, addr, count);
-
- remains = count;
-
- /*
- * Area is split into regions and tracked with vmap_block, read out
- * each region and zero fill the hole between regions.
- */
- xa = addr_to_vb_xa((unsigned long) addr);
- vb = xa_load(xa, addr_to_vb_idx((unsigned long)addr));
- if (!vb)
- goto finished_zero;
-
- spin_lock(&vb->lock);
- if (bitmap_empty(vb->used_map, VMAP_BBMAP_BITS)) {
- spin_unlock(&vb->lock);
- goto finished_zero;
- }
-
- for_each_set_bitrange(rs, re, vb->used_map, VMAP_BBMAP_BITS) {
- size_t copied;
-
- if (remains == 0)
- goto finished;
-
- start = vmap_block_vaddr(vb->va->va_start, rs);
-
- if (addr < start) {
- size_t to_zero = min_t(size_t, start - addr, remains);
- size_t zeroed = zero_iter(iter, to_zero);
-
- addr += zeroed;
- remains -= zeroed;
-
- if (remains == 0 || zeroed != to_zero)
- goto finished;
- }
-
- /*it could start reading from the middle of used region*/
- offset = offset_in_page(addr);
- n = ((re - rs + 1) << PAGE_SHIFT) - offset;
- if (n > remains)
- n = remains;
-
- copied = aligned_vread_iter(iter, start + offset, n);
-
- addr += copied;
- remains -= copied;
-
- if (copied != n)
- goto finished;
- }
-
- spin_unlock(&vb->lock);
-
-finished_zero:
- /* zero-fill the left dirty or free regions */
- return count - remains + zero_iter(iter, remains);
-finished:
- /* We couldn't copy/zero everything */
- spin_unlock(&vb->lock);
- return count - remains;
-}
-
-/**
- * vread_iter() - read vmalloc area in a safe way to an iterator.
- * @iter: the iterator to which data should be written.
- * @addr: vm address.
- * @count: number of bytes to be read.
- *
- * This function checks that addr is a valid vmalloc'ed area, and
- * copy data from that area to a given buffer. If the given memory range
- * of [addr...addr+count) includes some valid address, data is copied to
- * proper area of @buf. If there are memory holes, they'll be zero-filled.
- * IOREMAP area is treated as memory hole and no copy is done.
- *
- * If [addr...addr+count) doesn't includes any intersects with alive
- * vm_struct area, returns 0. @buf should be kernel's buffer.
- *
- * Note: In usual ops, vread() is never necessary because the caller
- * should know vmalloc() area is valid and can use memcpy().
- * This is for routines which have to access vmalloc area without
- * any information, as /proc/kcore.
- *
- * Return: number of bytes for which addr and buf should be increased
- * (same number as @count) or %0 if [addr...addr+count) doesn't
- * include any intersection with valid vmalloc area
- */
-long vread_iter(struct iov_iter *iter, const char *addr, size_t count)
-{
- struct vmap_area *va;
- struct vm_struct *vm;
- char *vaddr;
- size_t n, size, flags, remains;
-
- addr = kasan_reset_tag(addr);
-
- /* Don't allow overflow */
- if ((unsigned long) addr + count < count)
- count = -(unsigned long) addr;
-
- remains = count;
-
- spin_lock(&vmap_area_lock);
- va = find_vmap_area_exceed_addr((unsigned long)addr);
- if (!va)
- goto finished_zero;
-
- /* no intersects with alive vmap_area */
- if ((unsigned long)addr + remains <= va->va_start)
- goto finished_zero;
-
- list_for_each_entry_from(va, &vmap_area_list, list) {
- size_t copied;
-
- if (remains == 0)
- goto finished;
-
- vm = va->vm;
- flags = va->flags & VMAP_FLAGS_MASK;
- /*
- * VMAP_BLOCK indicates a sub-type of vm_map_ram area, need
- * be set together with VMAP_RAM.
- */
- WARN_ON(flags == VMAP_BLOCK);
-
- if (!vm && !flags)
- continue;
-
- if (vm && (vm->flags & VM_UNINITIALIZED))
- continue;
-
- /* Pair with smp_wmb() in clear_vm_uninitialized_flag() */
- smp_rmb();
-
- vaddr = (char *) va->va_start;
- size = vm ? get_vm_area_size(vm) : va_size(va);
-
- if (addr >= vaddr + size)
- continue;
-
- if (addr < vaddr) {
- size_t to_zero = min_t(size_t, vaddr - addr, remains);
- size_t zeroed = zero_iter(iter, to_zero);
-
- addr += zeroed;
- remains -= zeroed;
-
- if (remains == 0 || zeroed != to_zero)
- goto finished;
- }
-
- n = vaddr + size - addr;
- if (n > remains)
- n = remains;
-
- if (flags & VMAP_RAM)
- copied = vmap_ram_vread_iter(iter, addr, n, flags);
- else if (!(vm && (vm->flags & VM_IOREMAP)))
- copied = aligned_vread_iter(iter, addr, n);
- else /* IOREMAP area is treated as memory hole */
- copied = zero_iter(iter, n);
-
- addr += copied;
- remains -= copied;
-
- if (copied != n)
- goto finished;
- }
-
-finished_zero:
- spin_unlock(&vmap_area_lock);
- /* zero-fill memory holes */
- return count - remains + zero_iter(iter, remains);
-finished:
- /* Nothing remains, or We couldn't copy/zero everything. */
- spin_unlock(&vmap_area_lock);
-
- return count - remains;
-}
-
/**
* remap_vmalloc_range_partial - map vmalloc pages to userspace
* @vma: vma to cover
^ permalink raw reply related [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2023-11-24 18:25 ` Linus Torvalds
@ 2023-11-24 18:52 ` Linus Torvalds
2023-11-24 20:12 ` Linus Torvalds
2023-11-25 13:10 ` Christian Brauner
1 sibling, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2023-11-24 18:52 UTC (permalink / raw)
To: Christian Brauner, Omar Sandoval, David Howells
Cc: linux-fsdevel, linux-kernel
On Fri, 24 Nov 2023 at 10:25, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> I just like how the patch looks:
>
> 6 files changed, 1 insertion(+), 368 deletions(-)
>
> and those 350+ deleted lines really looked disgusting to me.
Gaah. I guess it's the VM_IOREMAP case that is the cause of all this horridness.
So we'd have to know not to mess with IO mappings. Annoying.
But I think my patch could still act as a starting point, except that
case KCORE_VMALLOC:
would have to have some kind of "if this is not a regular vmalloc,
just skip it" logic.
So I guess we can't remove all those lines, but we *could* replace all
the vread_iter() code with a "bool can_I_vread_this()" instead. So the
fallback would still be to just do the bounce buffer copy.
Or something.
Oh well.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2023-11-24 18:52 ` Linus Torvalds
@ 2023-11-24 20:12 ` Linus Torvalds
2023-11-25 13:05 ` Christian Brauner
0 siblings, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2023-11-24 20:12 UTC (permalink / raw)
To: Christian Brauner, Omar Sandoval, David Howells
Cc: linux-fsdevel, linux-kernel
On Fri, 24 Nov 2023 at 10:52, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Gaah. I guess it's the VM_IOREMAP case that is the cause of all this horridness.
>
> So we'd have to know not to mess with IO mappings. Annoying.
Doing a debian code search, I see a number of programs that do a
"stat()" on the kcore file, to get some notion of "system memory
size". I don't think it's valid, but whatever. We probably shouldn't
change it.
I also see some programs that actually read the ELF notes and sections
for dumping purposes.
But does anybody actually run gdb on that thing or similar? That's the
original model for that file, but it was always more of a gimmick than
anything else.
Because we could just say "read zeroes from KCORE_VMALLOC" and be done
with it that way.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [GIT PULL] vfs fixes
2023-11-24 18:25 ` Linus Torvalds
2023-11-24 18:52 ` Linus Torvalds
@ 2023-11-25 13:10 ` Christian Brauner
2023-11-25 13:28 ` Omar Sandoval
1 sibling, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2023-11-25 13:10 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Omar Sandoval, David Howells, linux-fsdevel, linux-kernel
On Fri, Nov 24, 2023 at 10:25:15AM -0800, Linus Torvalds wrote:
> On Fri, 24 Nov 2023 at 02:28, Christian Brauner <brauner@kernel.org> wrote:
> >
> > * Fix a bug introduced with the iov_iter rework from last cycle.
> >
> > This broke /proc/kcore by copying too much and without the correct
> > offset.
>
> Ugh. I think the whole /proc/kcore vmalloc handling is just COMPLETELY broken.
Ugh, I didn't even look at that closely because the fix was obviously
correct for that helper alone. Let's try and just return zeroed memory
like you suggested in your last mail before we bother fixing any of
this.
Long-term plan, it'd be nice to just get distros to start turning
/proc/kcore off. Maybe I underestimate legitimate users but this
requires CAP_SYS_RAW_IO so it really can only be useful to pretty
privileged stuff anyway.
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [GIT PULL] vfs fixes
2023-11-25 13:10 ` Christian Brauner
@ 2023-11-25 13:28 ` Omar Sandoval
2023-11-25 14:04 ` Christian Brauner
0 siblings, 1 reply; 188+ messages in thread
From: Omar Sandoval @ 2023-11-25 13:28 UTC (permalink / raw)
To: Christian Brauner
Cc: Linus Torvalds, Omar Sandoval, David Howells, linux-fsdevel,
linux-kernel
On Sat, Nov 25, 2023 at 02:10:52PM +0100, Christian Brauner wrote:
> On Fri, Nov 24, 2023 at 10:25:15AM -0800, Linus Torvalds wrote:
> > On Fri, 24 Nov 2023 at 02:28, Christian Brauner <brauner@kernel.org> wrote:
> > >
> > > * Fix a bug introduced with the iov_iter rework from last cycle.
> > >
> > > This broke /proc/kcore by copying too much and without the correct
> > > offset.
> >
> > Ugh. I think the whole /proc/kcore vmalloc handling is just COMPLETELY broken.
>
> Ugh, I didn't even look at that closely because the fix was obviously
> correct for that helper alone. Let's try and just return zeroed memory
> like you suggested in your last mail before we bother fixing any of
> this.
>
> Long-term plan, it'd be nice to just get distros to start turning
> /proc/kcore off. Maybe I underestimate legitimate users but this
> requires CAP_SYS_RAW_IO so it really can only be useful to pretty
> privileged stuff anyway.
drgn needs /proc/kcore for debugging the live kernel, which is a very
important use case for lots of our users. And it does in fact read from
KCORE_VMALLOC segments, which is why I found and fixed this bug. I'm
happy to clean up this code, although it's a holiday weekend here so I
won't get to it immediately of course. But please don't rip this out.
Omar
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [GIT PULL] vfs fixes
2023-11-25 13:28 ` Omar Sandoval
@ 2023-11-25 14:04 ` Christian Brauner
0 siblings, 0 replies; 188+ messages in thread
From: Christian Brauner @ 2023-11-25 14:04 UTC (permalink / raw)
To: Omar Sandoval
Cc: Linus Torvalds, Omar Sandoval, David Howells, linux-fsdevel,
linux-kernel
On Sat, Nov 25, 2023 at 05:28:49AM -0800, Omar Sandoval wrote:
> On Sat, Nov 25, 2023 at 02:10:52PM +0100, Christian Brauner wrote:
> > On Fri, Nov 24, 2023 at 10:25:15AM -0800, Linus Torvalds wrote:
> > > On Fri, 24 Nov 2023 at 02:28, Christian Brauner <brauner@kernel.org> wrote:
> > > >
> > > > * Fix a bug introduced with the iov_iter rework from last cycle.
> > > >
> > > > This broke /proc/kcore by copying too much and without the correct
> > > > offset.
> > >
> > > Ugh. I think the whole /proc/kcore vmalloc handling is just COMPLETELY broken.
> >
> > Ugh, I didn't even look at that closely because the fix was obviously
> > correct for that helper alone. Let's try and just return zeroed memory
> > like you suggested in your last mail before we bother fixing any of
> > this.
> >
> > Long-term plan, it'd be nice to just get distros to start turning
> > /proc/kcore off. Maybe I underestimate legitimate users but this
> > requires CAP_SYS_RAW_IO so it really can only be useful to pretty
> > privileged stuff anyway.
>
> drgn needs /proc/kcore for debugging the live kernel, which is a very
> important use case for lots of our users. And it does in fact read from
> KCORE_VMALLOC segments, which is why I found and fixed this bug. I'm
> happy to clean up this code, although it's a holiday weekend here so I
> won't get to it immediately of course. But please don't rip this out.
Ugh, I see. I just grepped through the drgn repo. I didn't realize that
you were actively using it and not just testing it. If this is actively
used then we won't break you ofc.
And yeah, if you would fix it that would be great. Given that you're the
main active user who happens to have kernel experience you might even
want to be made responsible for this file in the future. ;)
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [GIT PULL] vfs fixes
2023-11-24 10:27 Christian Brauner
2023-11-24 18:25 ` Linus Torvalds
@ 2023-11-24 18:26 ` pr-tracker-bot
1 sibling, 0 replies; 188+ messages in thread
From: pr-tracker-bot @ 2023-11-24 18:26 UTC (permalink / raw)
To: Christian Brauner
Cc: Linus Torvalds, Christian Brauner, linux-fsdevel, linux-kernel
The pull request you sent on Fri, 24 Nov 2023 11:27:28 +0100:
> git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.7-rc3.fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fa2b906f5148883e2d0be8952767469c2e3de274
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
^ permalink raw reply [flat|nested] 188+ messages in thread
* [GIT PULL] vfs fixes
@ 2023-10-19 10:07 Christian Brauner
2023-10-19 16:37 ` Linus Torvalds
2023-10-19 18:36 ` pr-tracker-bot
0 siblings, 2 replies; 188+ messages in thread
From: Christian Brauner @ 2023-10-19 10:07 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
An openat() call from io_uring triggering an audit call can apparently
cause the refcount of struct filename to be incremented from multiple
threads concurrently during async execution, triggering a refcount
underflow and hitting a BUG_ON(). That bug has been lurking around since
at least v5.16 apparently.
Switch to an atomic counter to fix that. The underflow check is
downgraded from a BUG_ON() to a WARN_ON_ONCE() but we could easily
remove that check altogether tbh and not waste an additional atomic. So
if you feel that extra check isn't needed you could just remove in case
you're pulling.
/* Testing */
clang: Ubuntu clang version 15.0.7
gcc: (Ubuntu 12.2.0-3ubuntu1) 12.2.0
All patches are based on v6.6-rc6 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit 94f6f0550c625fab1f373bb86a6669b45e9748b3:
Linux 6.6-rc5 (2023-10-08 13:49:43 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/v6.6-rc7.vfs.fixes
for you to fetch changes up to 03adc61edad49e1bbecfb53f7ea5d78f398fe368:
audit,io_uring: io_uring openat triggers audit reference count underflow (2023-10-13 18:34:46 +0200)
Please consider pulling these changes from the signed v6.6-rc7.vfs.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
v6.6-rc7.vfs.fixes
----------------------------------------------------------------
Dan Clash (1):
audit,io_uring: io_uring openat triggers audit reference count underflow
fs/namei.c | 9 +++++----
include/linux/fs.h | 2 +-
kernel/auditsc.c | 8 ++++----
3 files changed, 10 insertions(+), 9 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2023-10-19 10:07 Christian Brauner
@ 2023-10-19 16:37 ` Linus Torvalds
2023-10-20 11:14 ` Christian Brauner
2023-10-19 18:36 ` pr-tracker-bot
1 sibling, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2023-10-19 16:37 UTC (permalink / raw)
To: Christian Brauner; +Cc: linux-fsdevel, linux-kernel
On Thu, 19 Oct 2023 at 03:09, Christian Brauner <brauner@kernel.org> wrote:
>
> An openat() call from io_uring triggering an audit call can apparently
> cause the refcount of struct filename to be incremented from multiple
> threads concurrently during async execution, triggering a refcount
> underflow and hitting a BUG_ON(). That bug has been lurking around since
> at least v5.16 apparently.
Ouch. That filename ref by audit was always supposed to be
thread-local in a "for this system call" kind of sense.
But yes, looks like the io_uring stuff ended up making it no longer
thread-local.
That said, using atomics for reference counting is our default
behavior and should be normal, so the patch isn't wrong, it's just
annoying since getname/putname is very much in the critical path of
filename handling.
That said, the extra atomics are hopefully not really noticeable.
Some people might want to use the non-refcounted version (ie we have
getname/putname used by ksmbd too, for example), if they really care.
It already exists, as __getname/__putname.
But the normal open/stat/etc system call paths are obviously now going
to hit those extra atomics. Not lovely, but I guess it's the best we
can do.
> Switch to an atomic counter to fix that. The underflow check is
> downgraded from a BUG_ON() to a WARN_ON_ONCE() but we could easily
> remove that check altogether tbh and not waste an additional atomic. So
> if you feel that extra check isn't needed you could just remove in case
> you're pulling.
Well, the atomic *read* is cheap - the expensive part is the
atomic_dec_and_test() (and the atomic_inc in the audit code.
I'm not sure why you made it check just for zero in the WARN_ON_ONCE,
rather than <= 0 as it used to, but that check is racy regardless, so
it doesn't matter. It would miss two concurrent decrements coming in
with a count of 1.
We don't have the ternary test of atomic decrement results (positive,
zero or negative), so it is what it is.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [GIT PULL] vfs fixes
2023-10-19 16:37 ` Linus Torvalds
@ 2023-10-20 11:14 ` Christian Brauner
0 siblings, 0 replies; 188+ messages in thread
From: Christian Brauner @ 2023-10-20 11:14 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-fsdevel, linux-kernel
> Ouch. That filename ref by audit was always supposed to be
> thread-local in a "for this system call" kind of sense.
Yeah, I wasn't happy when that bug showed up.
> That said, using atomics for reference counting is our default
> behavior and should be normal, so the patch isn't wrong, it's just
> annoying since getname/putname is very much in the critical path of
> filename handling.
Yeah.
> That said, the extra atomics are hopefully not really noticeable.
>
> Some people might want to use the non-refcounted version (ie we have
> getname/putname used by ksmbd too, for example), if they really care.
>
> It already exists, as __getname/__putname.
>
> But the normal open/stat/etc system call paths are obviously now going
> to hit those extra atomics. Not lovely, but I guess it's the best we
> can do.
I didn't spend too much time on this issue because it's -rc7 and the
straightforward seemed ok, if annoying.
But if we really really really really cared we could probably do a
deranged thing and massage both audit and io_uring to allows us to
separate the regular system call getname from the io_uring getname. But
I think that would be ugly and likely error prone.
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [GIT PULL] vfs fixes
2023-10-19 10:07 Christian Brauner
2023-10-19 16:37 ` Linus Torvalds
@ 2023-10-19 18:36 ` pr-tracker-bot
1 sibling, 0 replies; 188+ messages in thread
From: pr-tracker-bot @ 2023-10-19 18:36 UTC (permalink / raw)
To: Christian Brauner
Cc: Linus Torvalds, Christian Brauner, linux-fsdevel, linux-kernel
The pull request you sent on Thu, 19 Oct 2023 12:07:08 +0200:
> git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/v6.6-rc7.vfs.fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ea1cc20cd4ce55dd920a87a317c43da03ccea192
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
^ permalink raw reply [flat|nested] 188+ messages in thread
* [GIT PULL] vfs fixes
@ 2023-09-26 10:39 Christian Brauner
2023-09-26 16:14 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2023-09-26 10:39 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains the usual miscellaneous fixes and cleanups for vfs and
individual fses:
Fixes
=====
* Revert ki_pos on error from buffered writes for direct io fallback
* Add missing documentation for block device and superblock handling
for changes merged this cycle.
* Fix reiserfs flexible array usage
* Ensure that overlayfs sets ctime when setting mtime and atime.
* Disable deferred caller completions with overlayfs writes until proper
support exists.
Cleanups
========
* Remove duplicate initialization in pipe code.
* Annotate aio kioctx_table with __counted_by.
/* Testing */
clang: Ubuntu clang version 15.0.7
gcc: (Ubuntu 12.2.0-3ubuntu1) 12.2.0
All patches are based on v6.5-rc1 and have been sitting in linux-next.
No build failures or warnings were observed. xfstests pass without
regressions.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/v6.6-rc4.vfs.fixes
for you to fetch changes up to 03dbab3bba5f009d053635c729d1244f2c8bad38:
overlayfs: set ctime when setting mtime and atime (2023-09-25 14:53:54 +0200)
Please consider pulling these changes from the signed v6.6-rc4.vfs.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
v6.6-rc4.vfs.fixes
----------------------------------------------------------------
Al Viro (1):
direct_write_fallback(): on error revert the ->ki_pos update from buffered write
Christian Brauner (3):
porting: document new block device opening order
porting: document superblock as block device holder
ntfs3: put resources during ntfs_fill_super()
Chunhai Guo (1):
fs-writeback: do not requeue a clean inode having skipped pages
Jeff Layton (1):
overlayfs: set ctime when setting mtime and atime
Jens Axboe (1):
ovl: disable IOCB_DIO_CALLER_COMP
Kees Cook (1):
aio: Annotate struct kioctx_table with __counted_by
Max Kellermann (1):
fs/pipe: remove duplicate "offset" initializer
Shigeru Yoshida (1):
reiserfs: Replace 1-element array with C99 style flex-array
Documentation/filesystems/porting.rst | 96 +++++++++++++++++++++++++++++++++++
fs/aio.c | 2 +-
fs/fs-writeback.c | 11 ++--
fs/libfs.c | 1 +
fs/ntfs3/super.c | 1 +
fs/overlayfs/copy_up.c | 2 +-
fs/overlayfs/file.c | 6 +++
fs/pipe.c | 1 -
fs/reiserfs/reiserfs.h | 6 +--
9 files changed, 117 insertions(+), 9 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2023-07-06 11:52 Christian Brauner
2023-07-07 2:27 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2023-07-06 11:52 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains two minor fixes for Jan's rename locking work:
(1) Unlocking the source inode was guarded by a check whether source was
non-NULL. This doesn't make sense because source must be non-NULL
and the commit message explains in detail why.
(2) The lock_two_nondirectories() helper called WARN_ON_ONCE() and
dereferenced the inodes unconditionally but the underlying
lock_two_inodes() helper and the kernel documentation for that
function are clear that it is valid to pass NULL arguments. So here
a non-NULL check is needed. No caller does pass non-NULL arguments
but let's not knowingly leave landmines around.
/* Testing */
clang: Ubuntu clang version 15.0.7
gcc: (Ubuntu 12.2.0-3ubuntu1) 12.2.0
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
All patches are based on current mainline. No build failures or warnings
were observed. All old and new tests in fstests, selftests, and LTP pass
without regressions.
The following changes since commit 24be4d0b46bb0c3c1dc7bacd30957d6144a70dfc:
arch/arm64/mm/fault: Fix undeclared variable error in do_page_fault() (2023-07-03 19:04:32 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/v6.5/vfs.fixes.2
for you to fetch changes up to 33ab231f83cc12d0157711bbf84e180c3be7d7bc:
fs: don't assume arguments are non-NULL (2023-07-04 10:21:11 +0200)
Please consider pulling these changes from the signed v6.5/vfs.fixes.2 tag.
Thanks!
Christian
----------------------------------------------------------------
v6.5/vfs.fixes.2
----------------------------------------------------------------
Christian Brauner (1):
fs: don't assume arguments are non-NULL
Jan Kara (1):
fs: no need to check source
fs/inode.c | 6 ++++--
fs/namei.c | 3 +--
2 files changed, 5 insertions(+), 4 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2023-07-02 11:28 Christian Brauner
2023-07-02 18:53 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2023-07-02 11:28 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a fix for the backing file work from this cycle. When
init_file() failed it would call file_free_rcu() on the file allocated
by the caller of init_file(). It naively assumed that the correct
cleanup operation would be called depending on whether it is a regular
file or a backing file. However, that presupposes that the FMODE_BACKING
flag would already be set which it won't be as that is done in the
caller of init_file().
Fix that bug by moving the cleanup of the allocated file into the caller
where it belongs in the first place. There's no good reason for
init_file() to consume resources it didn't allocate. This is a mainline
only fix and was reported by syzbot. The fix was validated by syzbot
against the provided reproducer.
/* Testing */
clang: Ubuntu clang version 15.0.7
gcc: (Ubuntu 12.2.0-3ubuntu1) 12.2.0
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
All patches are based on current mainline. No build failures or warnings
were observed. All old and new tests in fstests, selftests, and LTP pass
without regressions.
The following changes since commit 995b406c7e972fab181a4bb57f3b95e59b8e5bf3:
Merge tag 'csky-for-linus-6.5' of https://github.com/c-sky/csky-linux (2023-07-01 21:12:32 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/v6.5/vfs.fixes
for you to fetch changes up to dff745c1221a402b4921d54f292288373cff500c:
fs: move cleanup from init_file() into its callers (2023-07-02 13:15:49 +0200)
Please consider pulling these changes from the signed v6.5/vfs.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
v6.5/vfs.fixes
----------------------------------------------------------------
Amir Goldstein (1):
fs: move cleanup from init_file() into its callers
fs/file_table.c | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2023-05-25 12:22 Christian Brauner
2023-05-25 18:18 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2023-05-25 12:22 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a small set of fixes:
* During the acl rework we merged this cycle the generic_listxattr()
helper had to be modified in a way that in principle it would allow
for POSIX ACLs to be reported. At least that was the impression we had
initially. Because before the acl rework POSIX ACLs would be reported
if the filesystem did have POSIX ACL xattr handlers in sb->s_xattr.
That logic changed and now we can simply check whether the superblock
has SB_POSIXACL set and if the inode has inode->i_{default_}acl set
report the appropriate POSIX ACL name.
However, we didn't realize that generic_listxattr() was only ever used
by two filesystems. Both of them don't support POSIX ACLs via
sb->s_xattr handlers and so never reported POSIX ACLs via
generic_listxattr() even if they raised SB_POSIXACL and did contain
inodes which had acls set. The example here is nfs4. So
generic_listxattr() suddenly started reporting POSIX ACLs when it
wouldn't have before.
Since SB_POSIXACL implies that the umask isn't stripped in the VFS
nfs4 can't just drop SB_POSIXACL from the superblock as it would also
alter umask handling for them. So just have generic_listxattr() not
report POSIX ACLs as it never did anyway. It's documented as such.
* Our SB_* flags currently use a signed integer and we shift the last
bit causing UBSAN to complain about undefined behavior. Switch to
using unsigned. While the original patch used an explicit unsigned
bitshift it's now pretty common to rely on the BIT() macro in a lot of
headers nowadays. So the patch has been adjusted to use that.
* Add Namjae as ntfs reviewer. They're already active this cycle so
let's make it explicit right now.
/* Testing */
clang: Ubuntu clang version 15.0.7
gcc: (Ubuntu 12.2.0-3ubuntu1) 12.2.0
All patches are based on 6.4-rc2 and have been sitting in linux-next.
No build failures or warnings were observed. All old and new tests in
fstests, selftests, and LTP pass without regressions.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit f1fcbaa18b28dec10281551dfe6ed3a3ed80e3d6:
Linux 6.4-rc2 (2023-05-14 12:51:40 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs/v6.4-rc3/misc.fixes
for you to fetch changes up to 48524463f807ec516a291bdf717dcf2c8e059f51:
ntfs: Add myself as a reviewer (2023-05-17 15:25:21 +0200)
Please consider pulling these changes from the signed vfs/v6.4-rc2/misc.fixes tag.
Thanks!
Christian
----------------------------------------------------------------
vfs/v6.4-rc2/misc.fixes
----------------------------------------------------------------
Hao Ge (1):
fs: fix undefined behavior in bit shift for SB_NOUSER
Jeff Layton (1):
fs: don't call posix_acl_listxattr in generic_listxattr
Namjae Jeon (1):
ntfs: Add myself as a reviewer
MAINTAINERS | 1 +
fs/xattr.c | 15 +++++++++------
include/linux/fs.h | 42 +++++++++++++++++++++---------------------
3 files changed, 31 insertions(+), 27 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2023-05-12 15:31 Christian Brauner
2023-05-12 22:14 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2023-05-12 15:31 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
During the pipe nonblock rework that made it in the check for both
O_NONBLOCK and IOCB_NOWAIT was dropped. Both checks need to be performed
to ensure that files without O_NONBLOCK but IOCB_NOWAIT don't block when
writing to or reading from a pipe.
This just contains the fix adding the check for IOCB_NOWAIT back in.
---
On a personal note, I'm still traveling because of LSFMMBPF (I'm
probably missing 5 letters and rearranging 3) and LSS
and will only be back on a regular schedule starting Tuesday.
/* Testing */
clang: Ubuntu clang version 15.0.6
gcc: (Ubuntu 12.2.0-3ubuntu1) 12.2.0
All patches are based on 6.4-rc1 and have been sitting in linux-next.
No build failures or warnings were observed. All old and new tests in
fstests, selftests, and LTP pass without regressions.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs/v6.4-rc1/pipe
for you to fetch changes up to c04fe8e32f907ea668f3f802387c1148fdb0e6c9:
pipe: check for IOCB_NOWAIT alongside O_NONBLOCK (2023-05-12 17:17:27 +0200)
Please consider pulling these changes from the signed vfs/v6.4-rc1/pipe tag.
Thanks!
Christian
----------------------------------------------------------------
vfs/v6.4-rc1/pipe
----------------------------------------------------------------
Jens Axboe (1):
pipe: check for IOCB_NOWAIT alongside O_NONBLOCK
fs/pipe.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2023-04-03 11:04 Christian Brauner
2023-04-03 16:51 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2023-04-03 11:04 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
When a mount or mount tree is made shared the vfs allocates new peer
group ids for all mounts that have no peer group id set. Only mounts
that aren't marked with MNT_SHARED are relevant here as MNT_SHARED
indicates that the mount has fully transitioned to a shared mount. The
peer group id handling is done with namespace lock held.
On failure, the peer group id settings of mounts for which a new peer
group id was allocated need to be reverted and the allocated peer group
id freed. The cleanup_group_ids() helper can identify the mounts to
cleanup by checking whether a given mount has a peer group id set but
isn't marked MNT_SHARED. The deallocation always needs to happen with
namespace lock held to protect against concurrent modifications of the
propagation settings.
This pull request contains a fix for the one place where the namespace
lock was dropped before calling cleanup_group_ids().
/* Testing */
clang: Ubuntu clang version 15.0.6
gcc: gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0
All patches are based on v6.3-rc4 and have been sitting in linux-next.
No build failures or warnings were observed. All old and new tests in
fstests, selftests, and LTP pass without regressions.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit 197b6b60ae7bc51dd0814953c562833143b292aa:
Linux 6.3-rc4 (2023-03-26 14:40:20 -0700)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping.git tags/vfs.misc.fixes.v6.3-rc6
for you to fetch changes up to cb2239c198ad9fbd5aced22cf93e45562da781eb:
fs: drop peer group ids under namespace lock (2023-03-31 12:13:37 +0200)
Please consider pulling these changes from the signed vfs.misc.fixes.v6.3-rc6 tag.
Thanks!
Christian
----------------------------------------------------------------
vfs.misc.fixes.v6.3-rc6
----------------------------------------------------------------
Christian Brauner (1):
fs: drop peer group ids under namespace lock
fs/namespace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [GIT PULL] vfs fixes
@ 2023-03-12 12:18 Christian Brauner
2023-03-12 16:20 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Christian Brauner @ 2023-03-12 12:18 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Christian Brauner, linux-fsdevel, linux-kernel
Hey Linus,
/* Summary */
This contains a few simple vfs fixes for v6.3. There should be nothing
exciting in here:
* When allocating pages for a watch queue failed, we didn't return an
error causing userspace to proceed even though all subsequent
notifcations would be lost. Make sure to return an error.
* Fix a misformed tree entry for the idmapping maintainers entry.
* When setting file leases from an idmapped mount via generic_setlease()
we need to take the idmapping into account otherwise taking a lease
would fail from an idmapped mount.
* Remove two redundant assignments, one in splice code and the other in
locks code, that static checkers complained about.
The watch queue and file lease fix should be backported.
/* Testing */
clang: Ubuntu clang version 15.0.2-1
gcc: gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0
All patches are based on v6.3-rc1 and have been sitting in linux-next.
No build failures or warnings were observed. All old and new tests in
fstests, selftests, and LTP pass without regressions.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/vfs/idmapping.git tags/vfs.misc.v6.3-rc2
for you to fetch changes up to 42d0c4bdf753063b6eec55415003184d3ca24f6e:
filelocks: use mount idmapping for setlease permission check (2023-03-09 22:36:12 +0100)
Please consider pulling these changes from the signed vfs.misc.v6.3-rc2 tag.
Thanks!
Christian
----------------------------------------------------------------
vfs.misc.v6.3-rc2
----------------------------------------------------------------
David Disseldorp (1):
watch_queue: fix IOC_WATCH_QUEUE_SET_SIZE alloc error paths
Jiapeng Chong (2):
splice: Remove redundant assignment to ret
fs/locks: Remove redundant assignment to cmd
Lukas Bulwahn (1):
MAINTAINERS: repair a malformed T: entry in IDMAPPED MOUNTS
Seth Forshee (1):
filelocks: use mount idmapping for setlease permission check
MAINTAINERS | 4 ++--
fs/locks.c | 4 ++--
fs/splice.c | 1 -
kernel/watch_queue.c | 1 +
4 files changed, 5 insertions(+), 5 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [git pull] vfs fixes
@ 2020-09-22 21:29 Al Viro
2020-09-22 22:15 ` pr-tracker-bot
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2020-09-22 21:29 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-fsdevel, linux-kernel
No common topic, just several assorted fixes.
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 fixes
for you to fetch changes up to 933a3752babcf6513117d5773d2b70782d6ad149:
fuse: fix the ->direct_IO() treatment of iov_iter (2020-09-17 17:26:56 -0400)
----------------------------------------------------------------
Al Viro (1):
fuse: fix the ->direct_IO() treatment of iov_iter
Alexey Dobriyan (1):
fs: fix cast in fsparam_u32hex() macro
Hans de Goede (1):
vboxsf: Fix the check for the old binary mount-arguments struct
fs/fuse/file.c | 25 ++++++++++++-------------
fs/vboxsf/super.c | 2 +-
include/linux/fs_parser.h | 2 +-
3 files changed, 14 insertions(+), 15 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [git pull] vfs fixes
@ 2018-07-01 12:31 Al Viro
2018-07-01 19:36 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2018-07-01 12:31 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-fsdevel
Followup to procfs-seq_file series this window
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 fixes
for you to fetch changes up to 877f919e192a09e77962a13d7165783027dee5fd:
proc: add proc_seq_release (2018-06-27 20:44:38 -0400)
----------------------------------------------------------------
Chunyu Hu (1):
proc: add proc_seq_release
fs/proc/generic.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2018-07-01 12:31 Al Viro
@ 2018-07-01 19:36 ` Linus Torvalds
2018-07-01 20:05 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2018-07-01 19:36 UTC (permalink / raw)
To: Al Viro; +Cc: linux-fsdevel
On Sun, Jul 1, 2018 at 5:31 AM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> Followup to procfs-seq_file series this window
That was a singularly unhelpful "description" of what is going on.
As is the one-liner shortlog:
> Chunyu Hu (1):
> proc: add proc_seq_release
which also says *nothing* about what is actually going on here and
what is fixed.
Please make your pull requests actually describe what the hell is
going on, and why.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2018-07-01 19:36 ` Linus Torvalds
@ 2018-07-01 20:05 ` Al Viro
2018-07-01 20:25 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2018-07-01 20:05 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-fsdevel
On Sun, Jul 01, 2018 at 12:36:49PM -0700, Linus Torvalds wrote:
> On Sun, Jul 1, 2018 at 5:31 AM Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > Followup to procfs-seq_file series this window
>
> That was a singularly unhelpful "description" of what is going on.
>
> As is the one-liner shortlog:
>
> > Chunyu Hu (1):
> > proc: add proc_seq_release
>
> which also says *nothing* about what is actually going on here and
> what is fixed.
>
> Please make your pull requests actually describe what the hell is
> going on, and why.
Point taken... Would something along the lines of "fixing a leak
introduced in procfs-seq_file series" be OK, or do you prefer
more details?
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2018-07-01 20:05 ` Al Viro
@ 2018-07-01 20:25 ` Linus Torvalds
0 siblings, 0 replies; 188+ messages in thread
From: Linus Torvalds @ 2018-07-01 20:25 UTC (permalink / raw)
To: Al Viro; +Cc: linux-fsdevel
On Sun, Jul 1, 2018 at 1:05 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> Point taken... Would something along the lines of "fixing a leak
> introduced in procfs-seq_file series" be OK, or do you prefer
> more details?
That would have been sufficient. As it was now, it looked to all
intents and purposes like adding a new function. So I went and looked
what was going on, and found the "oh, fix a leak" and wrote my own
merge message.
But it's the kind of thing I would really want to just get in the pull
request - an explanation of why I should pull.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread
* [git pull] vfs fixes
@ 2018-04-20 15:58 Al Viro
2018-04-20 18:29 ` Andrew Morton
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2018-04-20 15:58 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
Assorted fixes. Some of that is only a matter with fault injection
(broken handling of small allocation failure in various mount-related places),
but the last one is a root-triggerable stack overflow, and combined with
userns it gets really nasty ;-/
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
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 16a34adb9392b2fe4195267475ab5b472e55292c:
Don't leak MNT_INTERNAL away from internal mounts (2018-04-19 23:52:15 -0400)
----------------------------------------------------------------
Al Viro (5):
hypfs_kill_super(): deal with failed allocations
jffs2_kill_sb(): deal with failed allocations
orangefs_kill_sb(): deal with allocation failures
rpc_pipefs: fix double-dput()
Don't leak MNT_INTERNAL away from internal mounts
Tetsuo Handa (1):
mm,vmscan: Allow preallocating memory for register_shrinker().
arch/s390/hypfs/inode.c | 2 +-
fs/jffs2/super.c | 2 +-
fs/namespace.c | 3 ++-
fs/orangefs/super.c | 5 +++++
fs/super.c | 9 ++++-----
include/linux/shrinker.h | 7 +++++--
mm/vmscan.c | 21 ++++++++++++++++++++-
net/sunrpc/rpc_pipe.c | 1 +
8 files changed, 39 insertions(+), 11 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2018-04-20 15:58 Al Viro
@ 2018-04-20 18:29 ` Andrew Morton
2018-04-20 19:09 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Andrew Morton @ 2018-04-20 18:29 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, linux-kernel, linux-fsdevel
On Fri, 20 Apr 2018 16:58:46 +0100 Al Viro <viro@ZenIV.linux.org.uk> wrote:
> Assorted fixes. Some of that is only a matter with fault injection
> (broken handling of small allocation failure in various mount-related places),
> but the last one is a root-triggerable stack overflow, and combined with
> userns it gets really nasty ;-/
>
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> 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 16a34adb9392b2fe4195267475ab5b472e55292c:
>
> Don't leak MNT_INTERNAL away from internal mounts (2018-04-19 23:52:15 -0400)
> ...
>
> Tetsuo Handa (1):
> mm,vmscan: Allow preallocating memory for register_shrinker().
Confused. You had a bunch of issues with this patch
(http://lkml.kernel.org/r/20180411005938.GN30522@ZenIV.linux.org.uk)
and Tetsuo sent out a v2 but now we've merged the v1. Deliberate?
Also, it would be nice if you could get the Link: thing working in your
commits please - this one took a bit of hunting down.
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2018-04-20 18:29 ` Andrew Morton
@ 2018-04-20 19:09 ` Al Viro
2018-04-20 19:57 ` Andrew Morton
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2018-04-20 19:09 UTC (permalink / raw)
To: Andrew Morton; +Cc: Linus Torvalds, linux-kernel, linux-fsdevel
On Fri, Apr 20, 2018 at 11:29:45AM -0700, Andrew Morton wrote:
> On Fri, 20 Apr 2018 16:58:46 +0100 Al Viro <viro@ZenIV.linux.org.uk> wrote:
>
> > Assorted fixes. Some of that is only a matter with fault injection
> > (broken handling of small allocation failure in various mount-related places),
> > but the last one is a root-triggerable stack overflow, and combined with
> > userns it gets really nasty ;-/
> >
> > The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
> >
> > Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
> >
> > 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 16a34adb9392b2fe4195267475ab5b472e55292c:
> >
> > Don't leak MNT_INTERNAL away from internal mounts (2018-04-19 23:52:15 -0400)
> > ...
> >
> > Tetsuo Handa (1):
> > mm,vmscan: Allow preallocating memory for register_shrinker().
>
> Confused. You had a bunch of issues with this patch
> (http://lkml.kernel.org/r/20180411005938.GN30522@ZenIV.linux.org.uk)
> and Tetsuo sent out a v2 but now we've merged the v1. Deliberate?
I think by that time I'd applied v1 and fixed those issues myself (same as his
variant, modulo slightly different names).
> Also, it would be nice if you could get the Link: thing working in your
> commits please - this one took a bit of hunting down.
*blink*
What Link: thing? You mean lkml.kernel.org references to original postings?
Or is it something else? Never done that, actually; any tips re tools needed
for that? Normally it's save a bunch of postings into a local file in mutt,
scp it over to development box, then git am -s - either all at once, or step
by step with ediiting and git commit --amend in between...
I realize that message-id can be picked and massaged into Link: ... form,
of course, but I'd rather not reinvent the wheel if it's already done by
somebody...
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2018-04-20 19:09 ` Al Viro
@ 2018-04-20 19:57 ` Andrew Morton
0 siblings, 0 replies; 188+ messages in thread
From: Andrew Morton @ 2018-04-20 19:57 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, linux-kernel, linux-fsdevel
On Fri, 20 Apr 2018 20:09:56 +0100 Al Viro <viro@ZenIV.linux.org.uk> wrote:
> On Fri, Apr 20, 2018 at 11:29:45AM -0700, Andrew Morton wrote:
> > On Fri, 20 Apr 2018 16:58:46 +0100 Al Viro <viro@ZenIV.linux.org.uk> wrote:
> >
> > > Assorted fixes. Some of that is only a matter with fault injection
> > > (broken handling of small allocation failure in various mount-related places),
> > > but the last one is a root-triggerable stack overflow, and combined with
> > > userns it gets really nasty ;-/
> > >
> > > The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
> > >
> > > Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
> > >
> > > 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 16a34adb9392b2fe4195267475ab5b472e55292c:
> > >
> > > Don't leak MNT_INTERNAL away from internal mounts (2018-04-19 23:52:15 -0400)
> > > ...
> > >
> > > Tetsuo Handa (1):
> > > mm,vmscan: Allow preallocating memory for register_shrinker().
> >
> > Confused. You had a bunch of issues with this patch
> > (http://lkml.kernel.org/r/20180411005938.GN30522@ZenIV.linux.org.uk)
> > and Tetsuo sent out a v2 but now we've merged the v1. Deliberate?
>
> I think by that time I'd applied v1 and fixed those issues myself (same as his
> variant, modulo slightly different names).
AH.
> > Also, it would be nice if you could get the Link: thing working in your
> > commits please - this one took a bit of hunting down.
>
> *blink*
>
> What Link: thing? You mean lkml.kernel.org references to original postings?
yup. It's often fairly useful.
> Or is it something else? Never done that, actually; any tips re tools needed
> for that? Normally it's save a bunch of postings into a local file in mutt,
> scp it over to development box, then git am -s - either all at once, or step
> by step with ediiting and git commit --amend in between...
I'd have expected git-am to have a way of doing that by now.
> I realize that message-id can be picked and massaged into Link: ... form,
> of course, but I'd rather not reinvent the wheel if it's already done by
> somebody...
I just do this:
message_url()
{
pname="$1"
idline=$(grep -i "^Message-Id:" "$pname" | head -1)
if [ x"$idline" != "x" ]
then
msgid=$(echo "$idline" | sed -e 's/[^<]*<\([^>]*\).*/\1/')
if [ x"$msgid" != "x" ]
then
echo "http://lkml.kernel.org/r/$msgid"
fi
fi
}
^ permalink raw reply [flat|nested] 188+ messages in thread
* [git pull] vfs fixes
@ 2017-06-17 2:56 Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2017-06-17 2:56 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
A couple of fixes; a leak in mntns_install() caught by Andrei
(this cycle regression) + d_invalidate() softlockup fix - that had
been reported by a bunch of people lately, but the problem is pretty
old.
The following changes since commit 32c1431eea4881a6b17bd7c639315010aeefa452:
Linux 4.12-rc5 (2017-06-11 16:48:20 -0700)
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 4068367c9ca7b515a209f9c0c8741309a1e90495:
fs: don't forget to put old mntns in mntns_install (2017-06-15 06:53:05 -0400)
----------------------------------------------------------------
Al Viro (1):
Hang/soft lockup in d_invalidate with simultaneous calls
Andrei Vagin (1):
fs: don't forget to put old mntns in mntns_install
fs/dcache.c | 10 ++++------
fs/namespace.c | 2 ++
2 files changed, 6 insertions(+), 6 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [git pull] vfs fixes
@ 2017-04-09 5:40 Al Viro
2017-04-11 6:10 ` Linus Torvalds
2017-04-15 6:41 ` Vegard Nossum
0 siblings, 2 replies; 188+ messages in thread
From: Al Viro @ 2017-04-09 5:40 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
The following changes since commit a71c9a1c779f2499fb2afc0553e543f18aff6edf:
Linux 4.11-rc5 (2017-04-02 17:23:54 -0700)
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 a8e28440016bfb23bec266c4c66eacca6ea2d48b:
Merge branch 'work.statx' into for-next (2017-04-03 01:06:59 -0400)
----------------------------------------------------------------
Al Viro (2):
alpha: fix stack smashing in old_adjtimex(2)
Merge branch 'work.statx' into for-next
Darrick J. Wong (1):
xfs: report crtime and attribute flags to statx
David Howells (3):
ext4: Add statx support
statx: Reserve the top bit of the mask for future struct expansion
statx: Include a mask for stx_attributes in struct statx
Eric Biggers (4):
Documentation/filesystems: fix documentation for ->getattr()
statx: reject unknown flags when using NULL path
statx: remove incorrect part of vfs_statx() comment
statx: optimize copy of struct statx to userspace
Documentation/filesystems/Locking | 3 +-
Documentation/filesystems/porting | 6 +++
Documentation/filesystems/vfs.txt | 3 +-
arch/alpha/kernel/osf_sys.c | 2 +-
fs/ext4/ext4.h | 1 +
fs/ext4/file.c | 2 +-
fs/ext4/inode.c | 41 +++++++++++++++++--
fs/ext4/namei.c | 2 +
fs/ext4/symlink.c | 3 ++
fs/stat.c | 86 ++++++++++++++++++---------------------
fs/xfs/xfs_iops.c | 14 +++++++
include/linux/stat.h | 1 +
include/uapi/linux/stat.h | 5 ++-
samples/statx/test-statx.c | 12 ++++--
14 files changed, 120 insertions(+), 61 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-09 5:40 Al Viro
@ 2017-04-11 6:10 ` Linus Torvalds
2017-04-11 6:48 ` Al Viro
2017-04-15 6:41 ` Vegard Nossum
1 sibling, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2017-04-11 6:10 UTC (permalink / raw)
To: Al Viro; +Cc: Linux Kernel Mailing List, linux-fsdevel
Hey Al,
mind looking at fs/namei,c line 2186:
if (likely(!nd_jump_root(nd)))
return s;
nd->root.mnt = NULL;
--> rcu_read_unlock(); <--
return ERR_PTR(-ECHILD);
because that rcu_read_unlock() looks odd.
It looks odd because the lock part is
if (flags & LOOKUP_RCU)
rcu_read_lock();
ie it's locked conditionally, and the code in between does not seem to
return every time LOOKUP_RCU is clear.
So mind giving this a look? Is it as obviously buggy as I think it is,
or is there something I'm missing?
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-11 6:10 ` Linus Torvalds
@ 2017-04-11 6:48 ` Al Viro
2017-04-11 21:02 ` Andreas Dilger
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2017-04-11 6:48 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Mon, Apr 10, 2017 at 11:10:19PM -0700, Linus Torvalds wrote:
> It looks odd because the lock part is
>
> if (flags & LOOKUP_RCU)
> rcu_read_lock();
>
> ie it's locked conditionally, and the code in between does not seem to
> return every time LOOKUP_RCU is clear.
>
> So mind giving this a look? Is it as obviously buggy as I think it is,
> or is there something I'm missing?
It's more obscure than I would like, and can grow into a bug one day, but...
nd_jump_root() can only return non-zero if you have LOOKUP_RCU. So without
LOOKUP_RCU in flags, this
if (flags & LOOKUP_RCU)
rcu_read_lock();
set_root(nd);
if (likely(!nd_jump_root(nd)))
return s;
nd->root.mnt = NULL;
rcu_read_unlock();
won't get to that rcu_read_unlock() at all - it'll get zero from nd_jump_root()
and proceed to return s;
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-11 6:48 ` Al Viro
@ 2017-04-11 21:02 ` Andreas Dilger
2017-04-12 7:00 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Andreas Dilger @ 2017-04-11 21:02 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, Linux Kernel Mailing List, linux-fsdevel
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
On Apr 11, 2017, at 12:48 AM, Al Viro <viro@ZenIV.linux.org.uk> wrote:
> On Mon, Apr 10, 2017 at 11:10:19PM -0700, Linus Torvalds wrote:
>
>> It looks odd because the lock part is
>>
>> if (flags & LOOKUP_RCU)
>> rcu_read_lock();
>>
>> ie it's locked conditionally, and the code in between does not seem to
>> return every time LOOKUP_RCU is clear.
>>
>> So mind giving this a look? Is it as obviously buggy as I think it is,
>> or is there something I'm missing?
>
> It's more obscure than I would like, and can grow into a bug one day, but...
> nd_jump_root() can only return non-zero if you have LOOKUP_RCU. So without
> LOOKUP_RCU in flags, this
> if (flags & LOOKUP_RCU)
> rcu_read_lock();
> set_root(nd);
> if (likely(!nd_jump_root(nd)))
> return s;
> nd->root.mnt = NULL;
> rcu_read_unlock();
> won't get to that rcu_read_unlock() at all - it'll get zero from nd_jump_root()
> and proceed to return s;
So possibly a comment like the following would be helpful:
rcu_read_unlock(); /* nd_jump_root() returns if !LOOKUP_RCU */
so that us mere mortals have a chance to understand this in the future?
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2017-04-11 21:02 ` Andreas Dilger
@ 2017-04-12 7:00 ` Linus Torvalds
0 siblings, 0 replies; 188+ messages in thread
From: Linus Torvalds @ 2017-04-12 7:00 UTC (permalink / raw)
To: Andreas Dilger; +Cc: Al Viro, Linux Kernel Mailing List, linux-fsdevel
On Tue, Apr 11, 2017 at 2:02 PM, Andreas Dilger <adilger@dilger.ca> wrote:
> On Apr 11, 2017, at 12:48 AM, Al Viro <viro@ZenIV.linux.org.uk> wrote:
>>
>> It's more obscure than I would like, and can grow into a bug one day, but...
>> nd_jump_root() can only return non-zero if you have LOOKUP_RCU.
>
> So possibly a comment like the following would be helpful:
>
> rcu_read_unlock(); /* nd_jump_root() returns if !LOOKUP_RCU */
>
> so that us mere mortals have a chance to understand this in the future?
That might be good, but the reason I noticed this at all was that I
looked at all those "if (LOOKUP_RCU)" in that function, and was
thinking that the whole function would be better being split up into
the RCU case and the non-RCU case. Because the two cases do have
shared code, but the sharing is almost less than the non-shared stuff.
And when I started doing that split to see what it looked like, that
rcu_read_unlock() really stood out like a sore thumb.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2017-04-09 5:40 Al Viro
2017-04-11 6:10 ` Linus Torvalds
@ 2017-04-15 6:41 ` Vegard Nossum
2017-04-15 16:51 ` Linus Torvalds
1 sibling, 1 reply; 188+ messages in thread
From: Vegard Nossum @ 2017-04-15 6:41 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, LKML, linux-fsdevel
On 9 April 2017 at 07:40, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> The following changes since commit a71c9a1c779f2499fb2afc0553e543f18aff6edf:
>
> Linux 4.11-rc5 (2017-04-02 17:23:54 -0700)
>
> 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 a8e28440016bfb23bec266c4c66eacca6ea2d48b:
>
> Merge branch 'work.statx' into for-next (2017-04-03 01:06:59 -0400)
>
> ----------------------------------------------------------------
> Al Viro (2):
> alpha: fix stack smashing in old_adjtimex(2)
> Merge branch 'work.statx' into for-next
I'm seeing the same memfd_create/name_to_handle_at/path_lookupat
use-after-free that Dmitry was seeing here:
https://lkml.org/lkml/2017/3/4/118
I haven't tried the patch from that thread yet, but was there any
reason for it not to get merged so far?
Vegard
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2017-04-15 6:41 ` Vegard Nossum
@ 2017-04-15 16:51 ` Linus Torvalds
2017-04-15 17:08 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2017-04-15 16:51 UTC (permalink / raw)
To: Vegard Nossum; +Cc: Al Viro, LKML, linux-fsdevel
On Fri, Apr 14, 2017 at 11:41 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
>
> I'm seeing the same memfd_create/name_to_handle_at/path_lookupat
> use-after-free that Dmitry was seeing here:
Ok, see if that is gone in current git with commit c0eb027e5aef ("vfs:
don't do RCU lookup of empty pathnames")
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-15 16:51 ` Linus Torvalds
@ 2017-04-15 17:08 ` Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2017-04-15 17:08 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Vegard Nossum, LKML, linux-fsdevel
On Sat, Apr 15, 2017 at 09:51:40AM -0700, Linus Torvalds wrote:
> On Fri, Apr 14, 2017 at 11:41 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> >
> > I'm seeing the same memfd_create/name_to_handle_at/path_lookupat
> > use-after-free that Dmitry was seeing here:
>
> Ok, see if that is gone in current git with commit c0eb027e5aef ("vfs:
> don't do RCU lookup of empty pathnames")
FWIW, I'm finishing testing of fixes for crap found during the discussion
of that stuff last week (making sure that mntns_install() can't be abused
into setting ->fs->root/->fs->pwd to dentry of NFS referral and its ilk
and doing that in a sane way).
^ permalink raw reply [flat|nested] 188+ messages in thread
* [git pull] vfs fixes
@ 2017-04-02 17:01 Al Viro
2017-04-02 23:59 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2017-04-02 17:01 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
statx followup fixes, fix for a nasty corner case in path_init()
leaving path.dentry in RCU mode pointing to a dentry without DCACHE_RCUACCESS
and a fix for stack-smashing on alpha.
The following changes since commit c02ed2e75ef4c74e41e421acb4ef1494671585e8:
Linux 4.11-rc4 (2017-03-26 14:15:16 -0700)
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 0b1367305acc8e8706e13aa4c6766a747cf489d4:
statx: Include a mask for stx_attributes in struct statx (2017-04-02 12:27:59 -0400)
----------------------------------------------------------------
Al Viro (2):
path_init(): make sure that nd->path.dentry freeing will be RCU-delayed
alpha: fix stack smashing in old_adjtimex(2)
Darrick J. Wong (1):
xfs: report crtime and attribute flags to statx
David Howells (3):
ext4: Add statx support
statx: Reserve the top bit of the mask for future struct expansion
statx: Include a mask for stx_attributes in struct statx
Eric Biggers (4):
Documentation/filesystems: fix documentation for ->getattr()
statx: reject unknown flags when using NULL path
statx: remove incorrect part of vfs_statx() comment
statx: optimize copy of struct statx to userspace
Documentation/filesystems/Locking | 3 +-
Documentation/filesystems/porting | 6 +++
Documentation/filesystems/vfs.txt | 3 +-
arch/alpha/kernel/osf_sys.c | 2 +-
fs/ext4/ext4.h | 1 +
fs/ext4/file.c | 2 +-
fs/ext4/inode.c | 41 +++++++++++++++++--
fs/ext4/namei.c | 2 +
fs/ext4/symlink.c | 3 ++
fs/namei.c | 11 +++--
fs/stat.c | 86 ++++++++++++++++++---------------------
fs/xfs/xfs_iops.c | 14 +++++++
include/linux/stat.h | 1 +
include/uapi/linux/stat.h | 5 ++-
samples/statx/test-statx.c | 12 ++++--
15 files changed, 128 insertions(+), 64 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-02 17:01 Al Viro
@ 2017-04-02 23:59 ` Linus Torvalds
2017-04-03 0:10 ` Linus Torvalds
2017-04-03 0:20 ` Al Viro
0 siblings, 2 replies; 188+ messages in thread
From: Linus Torvalds @ 2017-04-02 23:59 UTC (permalink / raw)
To: Al Viro; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Sun, Apr 2, 2017 at 10:01 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> statx followup fixes, fix for a nasty corner case in path_init()
> leaving path.dentry in RCU mode pointing to a dentry without DCACHE_RCUACCESS
> and a fix for stack-smashing on alpha.
These were apparently committed minutes before sending me the pull request.
Why? What kind of testing did this all get?
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-02 23:59 ` Linus Torvalds
@ 2017-04-03 0:10 ` Linus Torvalds
2017-04-03 0:30 ` Al Viro
2017-04-03 0:20 ` Al Viro
1 sibling, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2017-04-03 0:10 UTC (permalink / raw)
To: Al Viro; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Sun, Apr 2, 2017 at 4:59 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Sun, Apr 2, 2017 at 10:01 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>> statx followup fixes, fix for a nasty corner case in path_init()
>> leaving path.dentry in RCU mode pointing to a dentry without DCACHE_RCUACCESS
>> and a fix for stack-smashing on alpha.
>
> These were apparently committed minutes before sending me the pull request.
>
> Why? What kind of testing did this all get?
Also, that RCU fix really stinks. It makes no sense. Any valid base
for actual pathname lookup will already have the bit set, so the only
issue is when people play games and use a non-path file descriptor
without a pathname. Right?
And that case shouldn't actually use RCU lookup AT ALL!
By definition such a case will just be immediately unlazied anyway in
complete_walk(), so doing an RCU lookup on an empty path only adds
overhead, and there is no actual point in doing an RCU walk on an
empty pathname.
So I get the feeling that the proper fix would be just something like
/* Don't RCU-lookup empty pathnames */
if ((flags & LOOKUP_RCU) && !*s)
flags &= ~LOOKUP_RCU;
at the very top of path_init(), which
(a) makes the code more efficiant, since we don't do those
unnecessary games with sequence numbers and RCU locking only to un-RCU
it immedately
and
(b) obviates the need for those DCACHE_RCUACCESS games entirely,
since anything that can actually be used as a base for pathname lookup
will already have that bit set, afaik.
So honestly, that fix to add DCACHE_RCUACCESS just looks like the
wrong thing to me.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-03 0:10 ` Linus Torvalds
@ 2017-04-03 0:30 ` Al Viro
2017-04-03 0:43 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2017-04-03 0:30 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Sun, Apr 02, 2017 at 05:10:08PM -0700, Linus Torvalds wrote:
> On Sun, Apr 2, 2017 at 4:59 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > On Sun, Apr 2, 2017 at 10:01 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >> statx followup fixes, fix for a nasty corner case in path_init()
> >> leaving path.dentry in RCU mode pointing to a dentry without DCACHE_RCUACCESS
> >> and a fix for stack-smashing on alpha.
> >
> > These were apparently committed minutes before sending me the pull request.
> >
> > Why? What kind of testing did this all get?
>
> Also, that RCU fix really stinks. It makes no sense. Any valid base
> for actual pathname lookup will already have the bit set, so the only
> issue is when people play games and use a non-path file descriptor
> without a pathname. Right?
>
> And that case shouldn't actually use RCU lookup AT ALL!
>
> By definition such a case will just be immediately unlazied anyway in
> complete_walk(), so doing an RCU lookup on an empty path only adds
> overhead, and there is no actual point in doing an RCU walk on an
> empty pathname.
>
> So I get the feeling that the proper fix would be just something like
>
> /* Don't RCU-lookup empty pathnames */
> if ((flags & LOOKUP_RCU) && !*s)
> flags &= ~LOOKUP_RCU;
>
> at the very top of path_init(), which
>
> (a) makes the code more efficiant, since we don't do those
> unnecessary games with sequence numbers and RCU locking only to un-RCU
> it immedately
>
> and
>
> (b) obviates the need for those DCACHE_RCUACCESS games entirely,
> since anything that can actually be used as a base for pathname lookup
> will already have that bit set, afaik.
Currently true and almost certainly will remain so. Point taken, what you
are suggesting is better. Actually, the invariant to watch for is
"no d_can_lookup() withtout DCACHE_RCUACCESS" and that we can trivially
enforce by one-liner change in d_flags_for_inode() -
s/DCACHE_DIRECTORY_TYPE/& | DCACHE_RCUACCESS/
OK...
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2017-04-03 0:30 ` Al Viro
@ 2017-04-03 0:43 ` Al Viro
2017-04-03 0:58 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2017-04-03 0:43 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Mon, Apr 03, 2017 at 01:30:45AM +0100, Al Viro wrote:
> Currently true and almost certainly will remain so. Point taken, what you
> are suggesting is better. Actually, the invariant to watch for is
> "no d_can_lookup() withtout DCACHE_RCUACCESS" and that we can trivially
> enforce by one-liner change in d_flags_for_inode() -
> s/DCACHE_DIRECTORY_TYPE/& | DCACHE_RCUACCESS/
>
> OK...
Do you have any objections against the following (still untested) variant?
I don't see any point in checking for flags & LOOKUP_RCU in case of !*s -
flags is in register at that point, so...
diff --git a/fs/dcache.c b/fs/dcache.c
index 95d71eda8142..05550139a8a6 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -1757,7 +1757,13 @@ static unsigned d_flags_for_inode(struct inode *inode)
return DCACHE_MISS_TYPE;
if (S_ISDIR(inode->i_mode)) {
- add_flags = DCACHE_DIRECTORY_TYPE;
+ /*
+ * Any potential starting point of lookup should have
+ * DCACHE_RCUACCESS; currently directory dentries
+ * come from d_alloc() anyway, but it costs us nothing
+ * to enforce it here.
+ */
+ add_flags = DCACHE_DIRECTORY_TYPE | DCACHE_RCUACCESS;
if (unlikely(!(inode->i_opflags & IOP_LOOKUP))) {
if (unlikely(!inode->i_op->lookup))
add_flags = DCACHE_AUTODIR_TYPE;
diff --git a/fs/namei.c b/fs/namei.c
index d41fab78798b..19dcf62133cc 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -2145,6 +2145,9 @@ static const char *path_init(struct nameidata *nd, unsigned flags)
int retval = 0;
const char *s = nd->name->name;
+ if (!*s)
+ flags &= ~LOOKUP_RCU;
+
nd->last_type = LAST_ROOT; /* if there are only slashes... */
nd->flags = flags | LOOKUP_JUMPED | LOOKUP_PARENT;
nd->depth = 0;
^ permalink raw reply related [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-03 0:43 ` Al Viro
@ 2017-04-03 0:58 ` Linus Torvalds
2017-04-03 2:21 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2017-04-03 0:58 UTC (permalink / raw)
To: Al Viro; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Sun, Apr 2, 2017 at 5:43 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> Do you have any objections against the following (still untested) variant?
> I don't see any point in checking for flags & LOOKUP_RCU in case of !*s -
> flags is in register at that point, so...
Looks sane to me.
I had to go and double-check that "DCACHE_DIRECTORY_TYPE" is what
d_can_lookup() actually checks, so _that_ part is perhaps a bit
subtle, and might be worth noting in that comment that you edited.
So the real "rule" ends up being that we only ever look up things from
dentries of type DCACHE_DIRECTORY_TYPE set, and those had better have
DCACHE_RCUACCESS bit set.
And the only reason path_init() only checks it for that case is that
nd->root and nd->pwd both have to be of type d_can_lookup().
Do we check that when we set it? I hope/assume we do.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-03 0:58 ` Linus Torvalds
@ 2017-04-03 2:21 ` Al Viro
2017-04-03 6:00 ` Eric W. Biederman
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2017-04-03 2:21 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, linux-fsdevel, Eric Biederman
On Sun, Apr 02, 2017 at 05:58:41PM -0700, Linus Torvalds wrote:
> I had to go and double-check that "DCACHE_DIRECTORY_TYPE" is what
> d_can_lookup() actually checks, so _that_ part is perhaps a bit
> subtle, and might be worth noting in that comment that you edited.
>
> So the real "rule" ends up being that we only ever look up things from
> dentries of type DCACHE_DIRECTORY_TYPE set, and those had better have
> DCACHE_RCUACCESS bit set.
>
> And the only reason path_init() only checks it for that case is that
> nd->root and nd->pwd both have to be of type d_can_lookup().
>
> Do we check that when we set it? I hope/assume we do.
For chdir()/chroot()/pivot_root() it's done by LOOKUP_DIRECTORY in lookup
flags; fchdir() is slightly different - there we check S_ISDIR of inode
of opened file. Which is almost the same thing, except for
kinda-sorta directories that have no ->lookup() - we have them for
NFS referral points. It should be impossible to end up with
one of those opened - not even with O_PATH; follow_managed() will be called
and we'll either fail or cross into whatever ends up overmounting them.
Still, it might be cleaner to turn that check into
d_can_lookup(f.file->f_path.dentry)
simply for consistency sake.
The thing I really don't like is mntns_install(). With sufficiently
nasty nfsroot setup it might be possible to end up with referral point
as one's root/pwd; getting out of such state would be interesting...
Smells like that place should be a solitary follow_down(), not a loop
of follow_down_one(), but I want Eric's opinion on that one; userns stuff
is weird.
diff --git a/fs/dcache.c b/fs/dcache.c
index 95d71eda8142..05550139a8a6 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -1757,7 +1757,13 @@ static unsigned d_flags_for_inode(struct inode *inode)
return DCACHE_MISS_TYPE;
if (S_ISDIR(inode->i_mode)) {
- add_flags = DCACHE_DIRECTORY_TYPE;
+ /*
+ * Any potential starting point of lookup should have
+ * DCACHE_RCUACCESS; currently directory dentries
+ * come from d_alloc() anyway, but it costs us nothing
+ * to enforce it here.
+ */
+ add_flags = DCACHE_DIRECTORY_TYPE | DCACHE_RCUACCESS;
if (unlikely(!(inode->i_opflags & IOP_LOOKUP))) {
if (unlikely(!inode->i_op->lookup))
add_flags = DCACHE_AUTODIR_TYPE;
diff --git a/fs/namei.c b/fs/namei.c
index d41fab78798b..19dcf62133cc 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -2145,6 +2145,9 @@ static const char *path_init(struct nameidata *nd, unsigned flags)
int retval = 0;
const char *s = nd->name->name;
+ if (!*s)
+ flags &= ~LOOKUP_RCU;
+
nd->last_type = LAST_ROOT; /* if there are only slashes... */
nd->flags = flags | LOOKUP_JUMPED | LOOKUP_PARENT;
nd->depth = 0;
diff --git a/fs/namespace.c b/fs/namespace.c
index cc1375eff88c..31ec9a79d2d4 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -3467,6 +3467,7 @@ static int mntns_install(struct nsproxy *nsproxy, struct ns_common *ns)
struct fs_struct *fs = current->fs;
struct mnt_namespace *mnt_ns = to_mnt_ns(ns);
struct path root;
+ int err;
if (!ns_capable(mnt_ns->user_ns, CAP_SYS_ADMIN) ||
!ns_capable(current_user_ns(), CAP_SYS_CHROOT) ||
@@ -3484,15 +3485,14 @@ static int mntns_install(struct nsproxy *nsproxy, struct ns_common *ns)
root.mnt = &mnt_ns->root->mnt;
root.dentry = mnt_ns->root->mnt.mnt_root;
path_get(&root);
- while(d_mountpoint(root.dentry) && follow_down_one(&root))
- ;
-
- /* Update the pwd and root */
- set_fs_pwd(fs, &root);
- set_fs_root(fs, &root);
-
+ err = follow_down(&root);
+ if (likely(!err)) {
+ /* Update the pwd and root */
+ set_fs_pwd(fs, &root);
+ set_fs_root(fs, &root);
+ }
path_put(&root);
- return 0;
+ return err;
}
static struct user_namespace *mntns_owner(struct ns_common *ns)
diff --git a/fs/open.c b/fs/open.c
index 949cef29c3bb..217b5db588c8 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -459,20 +459,17 @@ SYSCALL_DEFINE1(chdir, const char __user *, filename)
SYSCALL_DEFINE1(fchdir, unsigned int, fd)
{
struct fd f = fdget_raw(fd);
- struct inode *inode;
int error = -EBADF;
error = -EBADF;
if (!f.file)
goto out;
- inode = file_inode(f.file);
-
error = -ENOTDIR;
- if (!S_ISDIR(inode->i_mode))
+ if (!d_can_lookup(f.file->f_path.dentry))
goto out_putf;
- error = inode_permission(inode, MAY_EXEC | MAY_CHDIR);
+ error = inode_permission(file_inode(f.file), MAY_EXEC | MAY_CHDIR);
if (!error)
set_fs_pwd(current->fs, &f.file->f_path);
out_putf:
^ permalink raw reply related [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-03 2:21 ` Al Viro
@ 2017-04-03 6:00 ` Eric W. Biederman
2017-04-03 7:46 ` Al Viro
` (2 more replies)
0 siblings, 3 replies; 188+ messages in thread
From: Eric W. Biederman @ 2017-04-03 6:00 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, Linux Kernel Mailing List, linux-fsdevel,
Ian Kent
Al Viro <viro@ZenIV.linux.org.uk> writes:
> On Sun, Apr 02, 2017 at 05:58:41PM -0700, Linus Torvalds wrote:
>
>> I had to go and double-check that "DCACHE_DIRECTORY_TYPE" is what
>> d_can_lookup() actually checks, so _that_ part is perhaps a bit
>> subtle, and might be worth noting in that comment that you edited.
>>
>> So the real "rule" ends up being that we only ever look up things from
>> dentries of type DCACHE_DIRECTORY_TYPE set, and those had better have
>> DCACHE_RCUACCESS bit set.
>>
>> And the only reason path_init() only checks it for that case is that
>> nd->root and nd->pwd both have to be of type d_can_lookup().
>>
>> Do we check that when we set it? I hope/assume we do.
>
> For chdir()/chroot()/pivot_root() it's done by LOOKUP_DIRECTORY in lookup
> flags; fchdir() is slightly different - there we check S_ISDIR of inode
> of opened file. Which is almost the same thing, except for
> kinda-sorta directories that have no ->lookup() - we have them for
> NFS referral points. It should be impossible to end up with
> one of those opened - not even with O_PATH; follow_managed() will be called
> and we'll either fail or cross into whatever ends up overmounting them.
> Still, it might be cleaner to turn that check into
> d_can_lookup(f.file->f_path.dentry)
> simply for consistency sake.
>
> The thing I really don't like is mntns_install(). With sufficiently
> nasty nfsroot setup it might be possible to end up with referral point
> as one's root/pwd; getting out of such state would be interesting...
> Smells like that place should be a solitary follow_down(), not a loop
> of follow_down_one(), but I want Eric's opinion on that one; userns stuff
> is weird.
If I read the conversation correctly the concern is that we might
initialize a pwd or root with something that is almost but not quite a
directory in mntns_install.
Refereshing my memory. d_automount mounts things and is what
is used for nfs referrals. d_manage blocks waiting for
an automounts to complete or expire. follow_down just calls d_manage,
follow_manage calls both d_manage and d_automount as appropriate.
If the concern is nfs referral points calling follow_down is wrong and
what is wanted is follow_managed.
The only thing that follow_down prevents is changing onto directories
that are only half mounted, and not really directories yet. Which
is certainly part of the invarient we want to preserve.
The intent of the logic in mntns_install is to just pick a reasonable
looking place somewhere in that mount namespace to use as a root
directory. I arbitrarily picked the top of the mount stack on "/". Which
is typically used as the root directory. If people really care where
their root is they save a directory file descriptor off somewhere and
call chroot. So there is a little wiggle room exactly what the code
does.
There is a secondary use of mntns_install which is to give you a way to
access what is under "/" if you are so foolish as to umount "/". I keep
thinking setns to your own mount namespace would be a handy way to get
back to the rootfs and to use it for something during system shutdown.
I don't know if anyone has actually used setns to your own mount
namespace for that.
The worst case I can see from the proposed change is we would
not be able to umount all of the way down to rootfs. That
would be a self inflicted wound so I don't care.
I can't imagine anyone mounting an automount point deliberately on /
except as way to confuse the vfs. Though I can almost imagine getting
there by accident if an automount expires.
So yes please let's change the follow_down_one loop to follow_managed
to preserve the invariant that we always have a directory that
supports d_can_lookup to pass to set_fs_pwd and set_fs_root.
Eric
> diff --git a/fs/dcache.c b/fs/dcache.c
> index 95d71eda8142..05550139a8a6 100644
> --- a/fs/dcache.c
> +++ b/fs/dcache.c
> @@ -1757,7 +1757,13 @@ static unsigned d_flags_for_inode(struct inode *inode)
> return DCACHE_MISS_TYPE;
>
> if (S_ISDIR(inode->i_mode)) {
> - add_flags = DCACHE_DIRECTORY_TYPE;
> + /*
> + * Any potential starting point of lookup should have
> + * DCACHE_RCUACCESS; currently directory dentries
> + * come from d_alloc() anyway, but it costs us nothing
> + * to enforce it here.
> + */
> + add_flags = DCACHE_DIRECTORY_TYPE | DCACHE_RCUACCESS;
> if (unlikely(!(inode->i_opflags & IOP_LOOKUP))) {
> if (unlikely(!inode->i_op->lookup))
> add_flags = DCACHE_AUTODIR_TYPE;
> diff --git a/fs/namei.c b/fs/namei.c
> index d41fab78798b..19dcf62133cc 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -2145,6 +2145,9 @@ static const char *path_init(struct nameidata *nd, unsigned flags)
> int retval = 0;
> const char *s = nd->name->name;
>
> + if (!*s)
> + flags &= ~LOOKUP_RCU;
> +
> nd->last_type = LAST_ROOT; /* if there are only slashes... */
> nd->flags = flags | LOOKUP_JUMPED | LOOKUP_PARENT;
> nd->depth = 0;
> diff --git a/fs/namespace.c b/fs/namespace.c
> index cc1375eff88c..31ec9a79d2d4 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -3467,6 +3467,7 @@ static int mntns_install(struct nsproxy *nsproxy, struct ns_common *ns)
> struct fs_struct *fs = current->fs;
> struct mnt_namespace *mnt_ns = to_mnt_ns(ns);
> struct path root;
> + int err;
>
> if (!ns_capable(mnt_ns->user_ns, CAP_SYS_ADMIN) ||
> !ns_capable(current_user_ns(), CAP_SYS_CHROOT) ||
> @@ -3484,15 +3485,14 @@ static int mntns_install(struct nsproxy *nsproxy, struct ns_common *ns)
> root.mnt = &mnt_ns->root->mnt;
> root.dentry = mnt_ns->root->mnt.mnt_root;
> path_get(&root);
> - while(d_mountpoint(root.dentry) && follow_down_one(&root))
> - ;
> -
> - /* Update the pwd and root */
> - set_fs_pwd(fs, &root);
> - set_fs_root(fs, &root);
> -
> + err = follow_down(&root);
> + if (likely(!err)) {
> + /* Update the pwd and root */
> + set_fs_pwd(fs, &root);
> + set_fs_root(fs, &root);
> + }
> path_put(&root);
> - return 0;
> + return err;
> }
>
> static struct user_namespace *mntns_owner(struct ns_common *ns)
> diff --git a/fs/open.c b/fs/open.c
> index 949cef29c3bb..217b5db588c8 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -459,20 +459,17 @@ SYSCALL_DEFINE1(chdir, const char __user *, filename)
> SYSCALL_DEFINE1(fchdir, unsigned int, fd)
> {
> struct fd f = fdget_raw(fd);
> - struct inode *inode;
> int error = -EBADF;
>
> error = -EBADF;
> if (!f.file)
> goto out;
>
> - inode = file_inode(f.file);
> -
> error = -ENOTDIR;
> - if (!S_ISDIR(inode->i_mode))
> + if (!d_can_lookup(f.file->f_path.dentry))
> goto out_putf;
>
> - error = inode_permission(inode, MAY_EXEC | MAY_CHDIR);
> + error = inode_permission(file_inode(f.file), MAY_EXEC | MAY_CHDIR);
> if (!error)
> set_fs_pwd(current->fs, &f.file->f_path);
> out_putf:
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-03 6:00 ` Eric W. Biederman
@ 2017-04-03 7:46 ` Al Viro
2017-04-04 0:22 ` Ian Kent
2017-04-04 0:47 ` Ian Kent
2 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2017-04-03 7:46 UTC (permalink / raw)
To: Eric W. Biederman
Cc: Linus Torvalds, Linux Kernel Mailing List, linux-fsdevel,
Ian Kent
On Mon, Apr 03, 2017 at 01:00:56AM -0500, Eric W. Biederman wrote:
> Refereshing my memory. d_automount mounts things and is what
> is used for nfs referrals. d_manage blocks waiting for
> an automounts to complete or expire. follow_down just calls d_manage,
> follow_manage calls both d_manage and d_automount as appropriate.
D'oh... Right. What's more, by that point getting back to original
state on error is needed.
> If the concern is nfs referral points calling follow_down is wrong and
> what is wanted is follow_managed.
... except that follow_managed() takes nameidata and there is no way in
hell we are letting that animal out of fs/namei.c ever again. Too low-level.
> The intent of the logic in mntns_install is to just pick a reasonable
> looking place somewhere in that mount namespace to use as a root
> directory. I arbitrarily picked the top of the mount stack on "/". Which
> is typically used as the root directory. If people really care where
> their root is they save a directory file descriptor off somewhere and
> call chroot. So there is a little wiggle room exactly what the code
> does.
Hmm... If anything, I'm tempted to add LOOKUP_DOWN that would have
path_lookupat() do
if (unlikely(flags & LOOKUP_DOWN)) {
struct path path = nd->path;
dget(nd->path.dentry);
err = follow_managed(&path, nd);
if (unlikely(err < 0))
terminate_walk(nd);
return err;
}
path_to_nameidate(&path, nd);
}
right after path_init(). Then your stuff would've turned into
get_mnt_ns(mnt_ns);
old_mnt_ns = nsproxy->mnt_ns;
nsproxy->mnt_ns = mnt_ns;
/* Find the root */
err = vfs_path_lookup(mnt_ns->root->mnt.mnt_root, &mnt_ns->root->mnt,
"/", LOOKUP_DOWN, &root);
if (err) {
/* revert to old namespace */
nsproxy->mnt_ns = old_mnt_ns;
put_mnt_ns(mnt_ns);
return err;
}
/* Update the pwd and root */
set_fs_pwd(fs, &root);
set_fs_root(fs, &root);
path_put(&root);
put_mnt_ns(old_mnt_ns);
return 0;
This is absolutely untested, and I won't get around to testing it until
tomorrow, but something along those lines would IMO be better than
exposing a trimmed-down follow_managed(), not to mention struct nameidata
itself...
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-03 6:00 ` Eric W. Biederman
2017-04-03 7:46 ` Al Viro
@ 2017-04-04 0:22 ` Ian Kent
2017-04-04 0:47 ` Ian Kent
2 siblings, 0 replies; 188+ messages in thread
From: Ian Kent @ 2017-04-04 0:22 UTC (permalink / raw)
To: Eric W. Biederman, Al Viro
Cc: Linus Torvalds, Linux Kernel Mailing List, linux-fsdevel
On Mon, 2017-04-03 at 01:00 -0500, Eric W. Biederman wrote:
> Al Viro <viro@ZenIV.linux.org.uk> writes:
>
> > On Sun, Apr 02, 2017 at 05:58:41PM -0700, Linus Torvalds wrote:
> >
> > > I had to go and double-check that "DCACHE_DIRECTORY_TYPE" is what
> > > d_can_lookup() actually checks, so _that_ part is perhaps a bit
> > > subtle, and might be worth noting in that comment that you edited.
> > >
> > > So the real "rule" ends up being that we only ever look up things from
> > > dentries of type DCACHE_DIRECTORY_TYPE set, and those had better have
> > > DCACHE_RCUACCESS bit set.
> > >
> > > And the only reason path_init() only checks it for that case is that
> > > nd->root and nd->pwd both have to be of type d_can_lookup().
> > >
> > > Do we check that when we set it? I hope/assume we do.
> >
> > For chdir()/chroot()/pivot_root() it's done by LOOKUP_DIRECTORY in lookup
> > flags; fchdir() is slightly different - there we check S_ISDIR of inode
> > of opened file. Which is almost the same thing, except for
> > kinda-sorta directories that have no ->lookup() - we have them for
> > NFS referral points. It should be impossible to end up with
> > one of those opened - not even with O_PATH; follow_managed() will be called
> > and we'll either fail or cross into whatever ends up overmounting them.
> > Still, it might be cleaner to turn that check into
> > d_can_lookup(f.file->f_path.dentry)
> > simply for consistency sake.
> >
> > The thing I really don't like is mntns_install(). With sufficiently
> > nasty nfsroot setup it might be possible to end up with referral point
> > as one's root/pwd; getting out of such state would be interesting...
> > Smells like that place should be a solitary follow_down(), not a loop
> > of follow_down_one(), but I want Eric's opinion on that one; userns stuff
> > is weird.
>
> If I read the conversation correctly the concern is that we might
> initialize a pwd or root with something that is almost but not quite a
> directory in mntns_install.
>
> Refereshing my memory. d_automount mounts things and is what
> is used for nfs referrals. d_manage blocks waiting for
> an automounts to complete or expire. follow_down just calls d_manage,
> follow_manage calls both d_manage and d_automount as appropriate.
AFAIK d_manage() is only defined by autofs.
It was needed by autofs because the the mount creation and addition is done by
another (user space) thread whereas "normal" file systems like NFS do all the
work in-kernel.
>
> If the concern is nfs referral points calling follow_down is wrong and
> what is wanted is follow_managed.
>
> The only thing that follow_down prevents is changing onto directories
> that are only half mounted, and not really directories yet. Which
> is certainly part of the invarient we want to preserve.
>
>
>
> The intent of the logic in mntns_install is to just pick a reasonable
> looking place somewhere in that mount namespace to use as a root
> directory. I arbitrarily picked the top of the mount stack on "/". Which
> is typically used as the root directory. If people really care where
> their root is they save a directory file descriptor off somewhere and
> call chroot. So there is a little wiggle room exactly what the code
> does.
>
> There is a secondary use of mntns_install which is to give you a way to
> access what is under "/" if you are so foolish as to umount "/". I keep
> thinking setns to your own mount namespace would be a handy way to get
> back to the rootfs and to use it for something during system shutdown.
> I don't know if anyone has actually used setns to your own mount
> namespace for that.
>
> The worst case I can see from the proposed change is we would
> not be able to umount all of the way down to rootfs. That
> would be a self inflicted wound so I don't care.
>
> I can't imagine anyone mounting an automount point deliberately on /
> except as way to confuse the vfs. Though I can almost imagine getting
> there by accident if an automount expires.
>
> So yes please let's change the follow_down_one loop to follow_managed
> to preserve the invariant that we always have a directory that
> supports d_can_lookup to pass to set_fs_pwd and set_fs_root.
>
> Eric
>
> > diff --git a/fs/dcache.c b/fs/dcache.c
> > index 95d71eda8142..05550139a8a6 100644
> > --- a/fs/dcache.c
> > +++ b/fs/dcache.c
> > @@ -1757,7 +1757,13 @@ static unsigned d_flags_for_inode(struct inode
> > *inode)
> > return DCACHE_MISS_TYPE;
> >
> > if (S_ISDIR(inode->i_mode)) {
> > - add_flags = DCACHE_DIRECTORY_TYPE;
> > + /*
> > + * Any potential starting point of lookup should have
> > + * DCACHE_RCUACCESS; currently directory dentries
> > + * come from d_alloc() anyway, but it costs us nothing
> > + * to enforce it here.
> > + */
> > + add_flags = DCACHE_DIRECTORY_TYPE | DCACHE_RCUACCESS;
> > if (unlikely(!(inode->i_opflags & IOP_LOOKUP))) {
> > if (unlikely(!inode->i_op->lookup))
> > add_flags = DCACHE_AUTODIR_TYPE;
> > diff --git a/fs/namei.c b/fs/namei.c
> > index d41fab78798b..19dcf62133cc 100644
> > --- a/fs/namei.c
> > +++ b/fs/namei.c
> > @@ -2145,6 +2145,9 @@ static const char *path_init(struct nameidata *nd,
> > unsigned flags)
> > int retval = 0;
> > const char *s = nd->name->name;
> >
> > + if (!*s)
> > + flags &= ~LOOKUP_RCU;
> > +
> > nd->last_type = LAST_ROOT; /* if there are only slashes... */
> > nd->flags = flags | LOOKUP_JUMPED | LOOKUP_PARENT;
> > nd->depth = 0;
> > diff --git a/fs/namespace.c b/fs/namespace.c
> > index cc1375eff88c..31ec9a79d2d4 100644
> > --- a/fs/namespace.c
> > +++ b/fs/namespace.c
> > @@ -3467,6 +3467,7 @@ static int mntns_install(struct nsproxy *nsproxy,
> > struct ns_common *ns)
> > struct fs_struct *fs = current->fs;
> > struct mnt_namespace *mnt_ns = to_mnt_ns(ns);
> > struct path root;
> > + int err;
> >
> > if (!ns_capable(mnt_ns->user_ns, CAP_SYS_ADMIN) ||
> > !ns_capable(current_user_ns(), CAP_SYS_CHROOT) ||
> > @@ -3484,15 +3485,14 @@ static int mntns_install(struct nsproxy *nsproxy,
> > struct ns_common *ns)
> > root.mnt = &mnt_ns->root->mnt;
> > root.dentry = mnt_ns->root->mnt.mnt_root;
> > path_get(&root);
> > - while(d_mountpoint(root.dentry) && follow_down_one(&root))
> > - ;
> > -
> > - /* Update the pwd and root */
> > - set_fs_pwd(fs, &root);
> > - set_fs_root(fs, &root);
> > -
> > + err = follow_down(&root);
> > + if (likely(!err)) {
> > + /* Update the pwd and root */
> > + set_fs_pwd(fs, &root);
> > + set_fs_root(fs, &root);
> > + }
> > path_put(&root);
> > - return 0;
> > + return err;
> > }
> >
> > static struct user_namespace *mntns_owner(struct ns_common *ns)
> > diff --git a/fs/open.c b/fs/open.c
> > index 949cef29c3bb..217b5db588c8 100644
> > --- a/fs/open.c
> > +++ b/fs/open.c
> > @@ -459,20 +459,17 @@ SYSCALL_DEFINE1(chdir, const char __user *, filename)
> > SYSCALL_DEFINE1(fchdir, unsigned int, fd)
> > {
> > struct fd f = fdget_raw(fd);
> > - struct inode *inode;
> > int error = -EBADF;
> >
> > error = -EBADF;
> > if (!f.file)
> > goto out;
> >
> > - inode = file_inode(f.file);
> > -
> > error = -ENOTDIR;
> > - if (!S_ISDIR(inode->i_mode))
> > + if (!d_can_lookup(f.file->f_path.dentry))
> > goto out_putf;
> >
> > - error = inode_permission(inode, MAY_EXEC | MAY_CHDIR);
> > + error = inode_permission(file_inode(f.file), MAY_EXEC | MAY_CHDIR);
> > if (!error)
> > set_fs_pwd(current->fs, &f.file->f_path);
> > out_putf:
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2017-04-03 6:00 ` Eric W. Biederman
2017-04-03 7:46 ` Al Viro
2017-04-04 0:22 ` Ian Kent
@ 2017-04-04 0:47 ` Ian Kent
2 siblings, 0 replies; 188+ messages in thread
From: Ian Kent @ 2017-04-04 0:47 UTC (permalink / raw)
To: Eric W. Biederman, Al Viro
Cc: Linus Torvalds, Linux Kernel Mailing List, linux-fsdevel
On Mon, 2017-04-03 at 01:00 -0500, Eric W. Biederman wrote:
> Al Viro <viro@ZenIV.linux.org.uk> writes:
>
> > On Sun, Apr 02, 2017 at 05:58:41PM -0700, Linus Torvalds wrote:
> >
> > > I had to go and double-check that "DCACHE_DIRECTORY_TYPE" is what
> > > d_can_lookup() actually checks, so _that_ part is perhaps a bit
> > > subtle, and might be worth noting in that comment that you edited.
> > >
> > > So the real "rule" ends up being that we only ever look up things from
> > > dentries of type DCACHE_DIRECTORY_TYPE set, and those had better have
> > > DCACHE_RCUACCESS bit set.
> > >
> > > And the only reason path_init() only checks it for that case is that
> > > nd->root and nd->pwd both have to be of type d_can_lookup().
> > >
> > > Do we check that when we set it? I hope/assume we do.
> >
> > For chdir()/chroot()/pivot_root() it's done by LOOKUP_DIRECTORY in lookup
> > flags; fchdir() is slightly different - there we check S_ISDIR of inode
> > of opened file. Which is almost the same thing, except for
> > kinda-sorta directories that have no ->lookup() - we have them for
> > NFS referral points. It should be impossible to end up with
> > one of those opened - not even with O_PATH; follow_managed() will be called
> > and we'll either fail or cross into whatever ends up overmounting them.
> > Still, it might be cleaner to turn that check into
> > d_can_lookup(f.file->f_path.dentry)
> > simply for consistency sake.
> >
> > The thing I really don't like is mntns_install(). With sufficiently
> > nasty nfsroot setup it might be possible to end up with referral point
> > as one's root/pwd; getting out of such state would be interesting...
> > Smells like that place should be a solitary follow_down(), not a loop
> > of follow_down_one(), but I want Eric's opinion on that one; userns stuff
> > is weird.
>
> If I read the conversation correctly the concern is that we might
> initialize a pwd or root with something that is almost but not quite a
> directory in mntns_install.
>
> Refereshing my memory. d_automount mounts things and is what
> is used for nfs referrals. d_manage blocks waiting for
> an automounts to complete or expire. follow_down just calls d_manage,
> follow_manage calls both d_manage and d_automount as appropriate.
>
> If the concern is nfs referral points calling follow_down is wrong and
> what is wanted is follow_managed.
The case Al was concerned about (sounds like) where the root (or pwd) being
followed is an NFS referral (a similar case could be NFS file system migration
if (when?) being used, and that's probably more likely to be triggered from a
file system root than a referral).
I can't see how that could happen for a referral, but if it did the follow would
need to call d_automount(). It's unlikely ->d_manage() would factor into it but
it is available for use so should be part of it.
So follow_down() rather than follow_down_one() sounds like the right thing to
do.
>
> The only thing that follow_down prevents is changing onto directories
> that are only half mounted, and not really directories yet. Which
> is certainly part of the invarient we want to preserve.
>
>
>
> The intent of the logic in mntns_install is to just pick a reasonable
> looking place somewhere in that mount namespace to use as a root
> directory. I arbitrarily picked the top of the mount stack on "/". Which
> is typically used as the root directory. If people really care where
> their root is they save a directory file descriptor off somewhere and
> call chroot. So there is a little wiggle room exactly what the code
> does.
>
> There is a secondary use of mntns_install which is to give you a way to
> access what is under "/" if you are so foolish as to umount "/". I keep
> thinking setns to your own mount namespace would be a handy way to get
> back to the rootfs and to use it for something during system shutdown.
> I don't know if anyone has actually used setns to your own mount
> namespace for that.
>
> The worst case I can see from the proposed change is we would
> not be able to umount all of the way down to rootfs. That
> would be a self inflicted wound so I don't care.
>
> I can't imagine anyone mounting an automount point deliberately on /
> except as way to confuse the vfs. Though I can almost imagine getting
> there by accident if an automount expires.
>
> So yes please let's change the follow_down_one loop to follow_managed
> to preserve the invariant that we always have a directory that
> supports d_can_lookup to pass to set_fs_pwd and set_fs_root.
>
> Eric
>
> > diff --git a/fs/dcache.c b/fs/dcache.c
> > index 95d71eda8142..05550139a8a6 100644
> > --- a/fs/dcache.c
> > +++ b/fs/dcache.c
> > @@ -1757,7 +1757,13 @@ static unsigned d_flags_for_inode(struct inode
> > *inode)
> > return DCACHE_MISS_TYPE;
> >
> > if (S_ISDIR(inode->i_mode)) {
> > - add_flags = DCACHE_DIRECTORY_TYPE;
> > + /*
> > + * Any potential starting point of lookup should have
> > + * DCACHE_RCUACCESS; currently directory dentries
> > + * come from d_alloc() anyway, but it costs us nothing
> > + * to enforce it here.
> > + */
> > + add_flags = DCACHE_DIRECTORY_TYPE | DCACHE_RCUACCESS;
> > if (unlikely(!(inode->i_opflags & IOP_LOOKUP))) {
> > if (unlikely(!inode->i_op->lookup))
> > add_flags = DCACHE_AUTODIR_TYPE;
> > diff --git a/fs/namei.c b/fs/namei.c
> > index d41fab78798b..19dcf62133cc 100644
> > --- a/fs/namei.c
> > +++ b/fs/namei.c
> > @@ -2145,6 +2145,9 @@ static const char *path_init(struct nameidata *nd,
> > unsigned flags)
> > int retval = 0;
> > const char *s = nd->name->name;
> >
> > + if (!*s)
> > + flags &= ~LOOKUP_RCU;
> > +
> > nd->last_type = LAST_ROOT; /* if there are only slashes... */
> > nd->flags = flags | LOOKUP_JUMPED | LOOKUP_PARENT;
> > nd->depth = 0;
> > diff --git a/fs/namespace.c b/fs/namespace.c
> > index cc1375eff88c..31ec9a79d2d4 100644
> > --- a/fs/namespace.c
> > +++ b/fs/namespace.c
> > @@ -3467,6 +3467,7 @@ static int mntns_install(struct nsproxy *nsproxy,
> > struct ns_common *ns)
> > struct fs_struct *fs = current->fs;
> > struct mnt_namespace *mnt_ns = to_mnt_ns(ns);
> > struct path root;
> > + int err;
> >
> > if (!ns_capable(mnt_ns->user_ns, CAP_SYS_ADMIN) ||
> > !ns_capable(current_user_ns(), CAP_SYS_CHROOT) ||
> > @@ -3484,15 +3485,14 @@ static int mntns_install(struct nsproxy *nsproxy,
> > struct ns_common *ns)
> > root.mnt = &mnt_ns->root->mnt;
> > root.dentry = mnt_ns->root->mnt.mnt_root;
> > path_get(&root);
> > - while(d_mountpoint(root.dentry) && follow_down_one(&root))
> > - ;
> > -
> > - /* Update the pwd and root */
> > - set_fs_pwd(fs, &root);
> > - set_fs_root(fs, &root);
> > -
> > + err = follow_down(&root);
> > + if (likely(!err)) {
> > + /* Update the pwd and root */
> > + set_fs_pwd(fs, &root);
> > + set_fs_root(fs, &root);
> > + }
> > path_put(&root);
> > - return 0;
> > + return err;
> > }
> >
> > static struct user_namespace *mntns_owner(struct ns_common *ns)
> > diff --git a/fs/open.c b/fs/open.c
> > index 949cef29c3bb..217b5db588c8 100644
> > --- a/fs/open.c
> > +++ b/fs/open.c
> > @@ -459,20 +459,17 @@ SYSCALL_DEFINE1(chdir, const char __user *, filename)
> > SYSCALL_DEFINE1(fchdir, unsigned int, fd)
> > {
> > struct fd f = fdget_raw(fd);
> > - struct inode *inode;
> > int error = -EBADF;
> >
> > error = -EBADF;
> > if (!f.file)
> > goto out;
> >
> > - inode = file_inode(f.file);
> > -
> > error = -ENOTDIR;
> > - if (!S_ISDIR(inode->i_mode))
> > + if (!d_can_lookup(f.file->f_path.dentry))
> > goto out_putf;
> >
> > - error = inode_permission(inode, MAY_EXEC | MAY_CHDIR);
> > + error = inode_permission(file_inode(f.file), MAY_EXEC | MAY_CHDIR);
> > if (!error)
> > set_fs_pwd(current->fs, &f.file->f_path);
> > out_putf:
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2017-04-02 23:59 ` Linus Torvalds
2017-04-03 0:10 ` Linus Torvalds
@ 2017-04-03 0:20 ` Al Viro
1 sibling, 0 replies; 188+ messages in thread
From: Al Viro @ 2017-04-03 0:20 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Sun, Apr 02, 2017 at 04:59:10PM -0700, Linus Torvalds wrote:
> On Sun, Apr 2, 2017 at 10:01 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > statx followup fixes, fix for a nasty corner case in path_init()
> > leaving path.dentry in RCU mode pointing to a dentry without DCACHE_RCUACCESS
> > and a fix for stack-smashing on alpha.
>
> These were apparently committed minutes before sending me the pull request.
>
> Why?
The first two used to sit on a branch that predated statx merge into mainline,
the rest obviously depends on statx.
> What kind of testing did this all get?
xfstests/ltp for the last part (-rc4 based branch with statx), same + Dmitry's
reproducer for path_init() crap, trivial test for alpha old_adjtimex().
My apologies for rebase; if anything, it would've been cleaner to cherry-pick
the old pair of fixes on top of statx series.
^ permalink raw reply [flat|nested] 188+ messages in thread
* Q. hlist_bl_add_head_rcu() in d_alloc_parallel()
@ 2016-06-17 20:50 J. R. Okajima
2016-06-17 22:16 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: J. R. Okajima @ 2016-06-17 20:50 UTC (permalink / raw)
To: viro, linux-fsdevel
I am afraid there may exist another violation of "no lookups on the same
name in parallel" rule, but I am not sure.
Roughly d_alloc_parallel() behaves like this.
struct dentry *d_alloc_parallel()
{
new = d_alloc(parent, name);
rcu_read_lock();
hlist_bl_lock(b);
rcu_read_unlock();
hlist_bl_for_each_entry(dentry, node, b, d_u.d_in_lookup_hash) {
if (!matched_dentry_found)
continue;
dget(dentry);
hlist_bl_unlock(b);
return dentry;
}
hlist_bl_add_head_rcu(&new->d_u.d_in_lookup_hash, b);
hlist_bl_unlock(b);
return new;
}
When two processes try opening a single existing file and enters
d_alloc_parallel() at the same time, only one process wins and should
succeeds hlist_bl_add_head_rcu(). The other process should find the
dentry in d_u.d_in_lookup_hash and return 'dentry' (instead of
'new'). Am I right?
My question is when will 'new' be added into d_u.d_in_lookup_hash?
It should be between these two lines, I guess.
rcu_read_unlock();
hlist_bl_for_each_entry(dentry, node, b, d_u.d_in_lookup_hash) {
But can it surely happen?
If 'new' is not added here because someone else is in rcu_read_lock
region or other reason, then both processes will add the same named but
different dentry?
Is it better to change the lock/unlock-order like this?
rcu_read_unlock();
rcu_barrier();
hlist_bl_lock(b);
hlist_bl_for_each_entry(dentry, node, b, d_u.d_in_lookup_hash) {
J. R. Okajima
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: Q. hlist_bl_add_head_rcu() in d_alloc_parallel()
2016-06-17 20:50 Q. hlist_bl_add_head_rcu() in d_alloc_parallel() J. R. Okajima
@ 2016-06-17 22:16 ` Al Viro
2016-06-19 5:24 ` J. R. Okajima
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2016-06-17 22:16 UTC (permalink / raw)
To: J. R. Okajima; +Cc: linux-fsdevel
On Sat, Jun 18, 2016 at 05:50:30AM +0900, J. R. Okajima wrote:
> hlist_bl_lock(b);
> rcu_read_unlock();
> hlist_bl_for_each_entry(dentry, node, b, d_u.d_in_lookup_hash) {
> if (!matched_dentry_found)
> continue;
> dget(dentry);
> hlist_bl_unlock(b);
> return dentry;
> }
> hlist_bl_add_head_rcu(&new->d_u.d_in_lookup_hash, b);
> hlist_bl_unlock(b);
> return new;
> }
> When two processes try opening a single existing file and enters
> d_alloc_parallel() at the same time, only one process wins and should
> succeeds hlist_bl_add_head_rcu(). The other process should find the
> dentry in d_u.d_in_lookup_hash and return 'dentry' (instead of
> 'new'). Am I right?
>
> My question is when will 'new' be added into d_u.d_in_lookup_hash?
You've quoted it yourself:
> hlist_bl_add_head_rcu(&new->d_u.d_in_lookup_hash, b);
> It should be between these two lines, I guess.
> rcu_read_unlock();
> hlist_bl_for_each_entry(dentry, node, b, d_u.d_in_lookup_hash) {
> But can it surely happen?
> If 'new' is not added here because someone else is in rcu_read_lock
> region or other reason, then both processes will add the same named but
> different dentry?
Huh? If you have two processes reaching that insertion into the in-lookup
hash, whoever gets the hlist_bl_lock() first wins; the loser will find
the instance added by the winner and bugger off with it. RCU is completely
unrelated to that. It's about the search in *primary* hash.
> Is it better to change the lock/unlock-order like this?
>
> rcu_read_unlock();
> rcu_barrier();
> hlist_bl_lock(b);
> hlist_bl_for_each_entry(dentry, node, b, d_u.d_in_lookup_hash) {
No. We need to verify that nothing had been transferred from in-lookup to
primary hash after we'd found no match in the primary. That's what the
->i_dir_seq check is about, and it has to be done after we'd locked the
in-lookup hash chain. We could drop rcu_read_lock before locking the
chain, but this way we make sure we won't get preempted between fetching
the ->i_dir_seq and checking if it had been changed. The last thing we
want is rcu_barrier() - WTF for? To get an extra chance of something
being moved from in-lookup to primary, forcing us to repeat the primary
hash lookup?
We are *NOT* modifying the primary hash in d_alloc_parallel(). At all.
With respect to the primary hash it's a pure reader. And in-lookup hash
is only accessed under hlist_bl_lock() on its chains - no RCU accesses to
that one.
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: Q. hlist_bl_add_head_rcu() in d_alloc_parallel()
2016-06-17 22:16 ` Al Viro
@ 2016-06-19 5:24 ` J. R. Okajima
2016-06-19 16:55 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: J. R. Okajima @ 2016-06-19 5:24 UTC (permalink / raw)
To: Al Viro; +Cc: linux-fsdevel
Al Viro:
> Huh? If you have two processes reaching that insertion into the in-lookup
> hash, whoever gets the hlist_bl_lock() first wins; the loser will find
> the instance added by the winner and bugger off with it. RCU is completely
> unrelated to that. It's about the search in *primary* hash.
Ok, forget about rcu_barrier.
----------------------------------------
> look for match in in-lookup hash
> if found
> unlock the chain
> wait for the match to cease being in-lookup
> drop the match
> goto retry [see below]
> insert new into in-lookup hash
The actual matching test which corresponds to above pseudo-code (if
found) is this (from v4.7-rc3).
dentry->d_name.hash != hash
dentry->d_parent != parent
d_unhashed(dentry)
name (length and string)
I am afraid this d_unhashed() test is racy.
Here is what I am guessing.
- two processes try opening the same file
- the both enter the hlist_bl_lock protected loop in d_alloc_parallel()
- the winner puts the new dentry into in-lookup hash
+ here d_unhashed(dentry) would still return true.
- then the winner process will call ->atomic_open or ->lookup. finally
d_add() and rehash will be called and the dentry will be moved to the
primary hash.
+ here d_unhashed(dentry) would return false.
As soon as the winner calls hlist_bl_unlock(), the looser starts
d_in_lookup_hash loop and find the dentry which the winner added.
- the looser (or we should call processB) do the tests
dentry->d_name.hash != hash
dentry->d_parent != parent
d_unhashed(dentry)
- if processA has already called d_add and rehash, then this
d_unhashed() test would return false, and processB will throw away his
own 'new' dentry and return the found one.
- if processA has NOT called d_add and rehash yet (due to the schedule
timing), then this d_unhashed() test would return true, and processB
will simply skip the found dentry.
in this case, processB will add his own 'new' dentry into in-lookup
hash and return it.
Finally this race between these two
- d_add and rehash via ->atomic_open or ->lookup
- d_unhashed test in d_alloc_parallel
leads to the duplicated dentries (same named dentry under the same
parent).
Do you think it can happen?
J. R. Okajima
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: Q. hlist_bl_add_head_rcu() in d_alloc_parallel()
2016-06-19 5:24 ` J. R. Okajima
@ 2016-06-19 16:55 ` Al Viro
2016-06-20 4:34 ` J. R. Okajima
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2016-06-19 16:55 UTC (permalink / raw)
To: J. R. Okajima; +Cc: linux-fsdevel
On Sun, Jun 19, 2016 at 02:24:44PM +0900, J. R. Okajima wrote:
> - two processes try opening the same file
> - the both enter the hlist_bl_lock protected loop in d_alloc_parallel()
>
> - the winner puts the new dentry into in-lookup hash
> + here d_unhashed(dentry) would still return true.
> - then the winner process will call ->atomic_open or ->lookup. finally
> d_add() and rehash will be called and the dentry will be moved to the
> primary hash.
> + here d_unhashed(dentry) would return false.
> As soon as the winner calls hlist_bl_unlock(), the looser starts
> d_in_lookup_hash loop and find the dentry which the winner added.
>
> - the looser (or we should call processB) do the tests
> dentry->d_name.hash != hash
> dentry->d_parent != parent
> d_unhashed(dentry)
> - if processA has already called d_add and rehash, then this
> d_unhashed() test would return false, and processB will throw away his
> own 'new' dentry and return the found one.
> - if processA has NOT called d_add and rehash yet (due to the schedule
> timing), then this d_unhashed() test would return true, and processB
> will simply skip the found dentry.
> in this case, processB will add his own 'new' dentry into in-lookup
> hash and return it.
How would processB get past d_wait_lookup()? It would have to have
observed !d_in_lookup() while holding ->d_lock on that sucker; it does
*not* drop ->d_lock through the tests you've mentioned. And both the
removals of in-lookup flag and insertion into primary hash are done under
->d_lock without dropping it in between.
That was the point of taking security_d_instantiate() prior to attaching
to inode, etc. - that way we can make those actions (removal from in-lookup
hash, possibly attaching to inode, inserting into the primary hash) atomic
wrt d_wait_lookup().
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: Q. hlist_bl_add_head_rcu() in d_alloc_parallel()
2016-06-19 16:55 ` Al Viro
@ 2016-06-20 4:34 ` J. R. Okajima
2016-06-20 5:35 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: J. R. Okajima @ 2016-06-20 4:34 UTC (permalink / raw)
To: Al Viro; +Cc: linux-fsdevel
Al Viro:
> How would processB get past d_wait_lookup()? It would have to have
By the first d_unhashed() test in the loop, processB doesn't reach
d_wait_lookup().
Here is a more detailed scenario I am considering.
- two processes try opening the same file
- the both enter lookup_open() and the hlist_bl_lock protected loop in
d_alloc_parallel()
processA (the winner of hlist_bl_lock)
d_alloc_parallel()
+ new = d_alloc()
+ rcu_read_lock()
+ dentry = __d_lookup_rcu()
NULL
+ hlist_bl_lock() --- (BL0)
+ test parent's i_dir_seq --- (DS1)
+ rcu_read_unlock()
+ hlist_bl_for_each_entry(d_u.d_in_lookup_hash)
not found
+ new->d_flags |= DCACHE_PAR_LOOKUP
+ new->d_wait = wq
+ hlist_bl_add_head_rcu(new->d_u.d_in_lookup_hash)
+ hlist_bl_unlock() --- (BL1)
+ return new
--> a new dentry is added into in-lookup hash.
And then
processA
->atomic_open or ->lookup
+ __d_add()
+ spin_lock(d_lock)
+ update parent's i_dir_seq --- (DS2)
+ __d_lookup_done()
+ hlist_bl_lock() --- (BL2)
+ dentry->d_flags &= ~DCACHE_PAR_LOOKUP
+ __hlist_bl_del(d_u.d_in_lookup_hash)
+ hlist_bl_unlock() --- (BL3)
+ _d_rehash()
+ hlist_bl_lock() --- (BL4)
+ hlist_bl_add_head_rcu(d_hash)
+ hlist_bl_unlock()
+ spin_unlock(d_lock)
--> the new dentry is moved from in-lookup to primary hash.
Between (BL1) and (BL2) in processA flow, processB may acquire
hlist_bl_lock() which was blocked at (BL0), and it may happen even
before processA's (DS2).
In this case, processB will return an unexpectedly duplicated dentry
because DS1 test will be passed and the loop body will be skipped by
d_unhashed() test before d_wait_lookup().
It is after (BL4) when d_unhashed() turns FALSE.
processB
d_alloc_parallel()
+ hlist_bl_lock()
+ test parent's i_dir_seq
passed if processA doesn't reach (DS2) yet.
+ rcu_read_unlock()
+ hlist_bl_for_each_entry(d_u.d_in_lookup_hash)
dentry found but skips because
if (d_unhashed(dentry))
continue;
before d_wait_lookup().
+ new->d_flags |= DCACHE_PAR_LOOKUP
+ new->d_wait = wq
+ hlist_bl_add_head_rcu(new->d_u.d_in_lookup_hash)
+ hlist_bl_unlock()
+ return new
--> another same named dentry is added into in-lookup hash.
On the other hand, in case of processB acquires hlist_bl_lock() between
(BL3) and (BL4) in processA's flow, processB will detect the parent's
i_dir_seq is modified and 'goto retry'. It is good.
Finally the race condition I am afraid is
- processB aqcuires BL0 between processA's BL1 and BL2.
and
- processB tests DS1 before processA's DS2.
J. R. Okajima
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: Q. hlist_bl_add_head_rcu() in d_alloc_parallel()
2016-06-20 4:34 ` J. R. Okajima
@ 2016-06-20 5:35 ` Al Viro
2016-06-20 14:51 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2016-06-20 5:35 UTC (permalink / raw)
To: J. R. Okajima; +Cc: linux-fsdevel
On Mon, Jun 20, 2016 at 01:34:14PM +0900, J. R. Okajima wrote:
>
> Al Viro:
> > How would processB get past d_wait_lookup()? It would have to have
>
> By the first d_unhashed() test in the loop, processB doesn't reach
> d_wait_lookup().
Huh? What first d_unhashed()... <stares>
That check is definitely bogus and I'm completely at loss as to WTF is it
doing there. Thanks for catching that; this kind of idiotic braino can
escape notice when rereading the code again and again, unfortunately ;-/
Fixed, will push to Linus tonight or tomorrow.
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: Q. hlist_bl_add_head_rcu() in d_alloc_parallel()
2016-06-20 5:35 ` Al Viro
@ 2016-06-20 14:51 ` Al Viro
2016-06-20 17:14 ` [git pull] vfs fixes Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2016-06-20 14:51 UTC (permalink / raw)
To: J. R. Okajima; +Cc: linux-fsdevel, Linus Torvalds
On Mon, Jun 20, 2016 at 06:35:30AM +0100, Al Viro wrote:
> On Mon, Jun 20, 2016 at 01:34:14PM +0900, J. R. Okajima wrote:
> >
> > Al Viro:
> > > How would processB get past d_wait_lookup()? It would have to have
> >
> > By the first d_unhashed() test in the loop, processB doesn't reach
> > d_wait_lookup().
>
> Huh? What first d_unhashed()... <stares>
>
> That check is definitely bogus and I'm completely at loss as to WTF is it
> doing there. Thanks for catching that; this kind of idiotic braino can
> escape notice when rereading the code again and again, unfortunately ;-/
>
> Fixed, will push to Linus tonight or tomorrow.
FWIW, I understand how it got there; it was a garbage from cut'n'paste from
lockless primary hash lookups (cut'n'paste was for the sake of "compare
the name" logics). It was absolutely wrong - dentry is never added to
the primary hash until it has been removed from in-lookup one. And we are
walking the in-lookup hash chain with its bitlock held, so there's no
chance of that.
In effect that junk prevented d_alloc_parallel() from *ever* spotting
in-lookup matches. What's more, removing it has instantly uncovered
another bug in the match-handling code - dget() done under the chain
bitlock, which nests inside ->d_lock. Trivially fixed, of course (we
just hold rcu_read_lock() through the in-lookup hash search and instead
of dget() while holding the chain bitlock do lockref_get_not_dead()
after dropping the bitlock), but... *ouch*
It's going through the local tests right now; seems to be OK so far; I'll
send a pull request once it's through those. But this demonstrates why RTFS
(and by somebody other than the author of TFS being R) is really, _really_
important. I have read through that loop many times and kept missing that
turdlet ;-/
Al, wearing a brown paperbag ;-/
^ permalink raw reply [flat|nested] 188+ messages in thread
* [git pull] vfs fixes
2016-06-20 14:51 ` Al Viro
@ 2016-06-20 17:14 ` Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2016-06-20 17:14 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
A couple more of d_walk()/d_subdirs reordering fixes (stable fodder; ought to
solve that crap for good) and a fix for a brown paperbag bug in
d_alloc_parallel() (this cycle).
The following changes since commit 1607f09c226d1378439c411baaaa020042750338:
coredump: fix dumping through pipes (2016-06-07 22:07:09 -0400)
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 e7d6ef9790bc281f5c29d0132b68031248523fe8:
fix idiotic braino in d_alloc_parallel() (2016-06-20 10:07:42 -0400)
----------------------------------------------------------------
Al Viro (3):
much milder d_walk() race
autofs races
fix idiotic braino in d_alloc_parallel()
fs/autofs4/autofs_i.h | 8 ++++--
fs/autofs4/expire.c | 27 ++++++------------
fs/autofs4/root.c | 2 +-
fs/dcache.c | 75 ++++++++++++++++++++++++++++++++++++++++++--------
fs/internal.h | 1 +
fs/libfs.c | 4 +--
include/linux/dcache.h | 1 +
7 files changed, 82 insertions(+), 36 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread
* [git pull] vfs fixes
@ 2016-06-08 2:12 Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2016-06-08 2:12 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
Fixes for crap of assorted ages: EOPENSTALE one is 4.2+, autofs
one is 4.6, d_walk - 3.2+, atomic_open() and coredump ones are this window
regressions.
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
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 1607f09c226d1378439c411baaaa020042750338:
coredump: fix dumping through pipes (2016-06-07 22:07:09 -0400)
----------------------------------------------------------------
Al Viro (4):
fix EOPENSTALE bug in do_last()
autofs braino fix for do_last()
fix d_walk()/non-delayed __d_free() race
fix a regression in atomic_open()
Mateusz Guzik (1):
coredump: fix dumping through pipes
arch/powerpc/platforms/cell/spufs/coredump.c | 2 +-
fs/binfmt_elf.c | 2 +-
fs/binfmt_elf_fdpic.c | 2 +-
fs/coredump.c | 4 +-
fs/dcache.c | 4 +-
fs/namei.c | 61 +++++++---------------------
include/linux/binfmts.h | 1 +
7 files changed, 24 insertions(+), 52 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [git pull] vfs fixes
@ 2016-05-28 0:10 Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2016-05-28 0:10 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
work.lookups followups - update docs, restore killability of
the places that used to take ->i_mutex killably now that we have
down_write_killable() merged. Additionally, it turns out that I missed
a prereq for security_d_instantiate() stuff - ->getxattr() wasn't the
only thing that could be called before dentry is attached to inode; with
smack we needed the same treatment applied to ->setxattr() as well.
The following changes since commit 0985b65d3ba2c09f10a594b73df45c1f7f68d317:
Merge branch 'work.iov_iter' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2016-05-25 15:59:09 -0700)
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 3767e255b390d72f9a33c08d9e86c5f21f25860f:
switch ->setxattr() to passing dentry and inode separately (2016-05-27 20:09:16 -0400)
----------------------------------------------------------------
Al Viro (5):
update D/f/directory-locking
add down_write_killable_nested()
restore killability of old mutex_lock_killable(&inode->i_mutex) users
switch xattr_handler->set() to passing dentry and inode separately
switch ->setxattr() to passing dentry and inode separately
Documentation/filesystems/directory-locking | 32 ++++++++++++++--------
Documentation/filesystems/porting | 7 +++++
.../staging/lustre/lustre/llite/llite_internal.h | 4 +--
drivers/staging/lustre/lustre/llite/xattr.c | 6 ++--
fs/9p/acl.c | 6 ++--
fs/9p/xattr.c | 5 ++--
fs/bad_inode.c | 4 +--
fs/btrfs/ioctl.c | 18 +++++-------
fs/btrfs/xattr.c | 12 ++++----
fs/ceph/xattr.c | 7 +++--
fs/cifs/xattr.c | 9 +++---
fs/ecryptfs/crypto.c | 9 +++---
fs/ecryptfs/ecryptfs_kernel.h | 4 +--
fs/ecryptfs/inode.c | 7 +++--
fs/ecryptfs/mmap.c | 3 +-
fs/ext2/xattr_security.c | 7 +++--
fs/ext2/xattr_trusted.c | 7 +++--
fs/ext2/xattr_user.c | 9 +++---
fs/ext4/xattr_security.c | 7 +++--
fs/ext4/xattr_trusted.c | 7 +++--
fs/ext4/xattr_user.c | 9 +++---
fs/f2fs/xattr.c | 12 ++++----
fs/fuse/dir.c | 6 ++--
fs/gfs2/xattr.c | 6 ++--
fs/hfs/attr.c | 6 ++--
fs/hfs/hfs_fs.h | 2 +-
fs/hfsplus/xattr.c | 12 ++++----
fs/hfsplus/xattr.h | 2 +-
fs/hfsplus/xattr_security.c | 7 +++--
fs/hfsplus/xattr_trusted.c | 7 +++--
fs/hfsplus/xattr_user.c | 7 +++--
fs/jffs2/security.c | 7 +++--
fs/jffs2/xattr_trusted.c | 7 +++--
fs/jffs2/xattr_user.c | 7 +++--
fs/jfs/xattr.c | 14 ++++------
fs/kernfs/inode.c | 11 ++++----
fs/kernfs/kernfs-internal.h | 3 +-
fs/libfs.c | 5 ++--
fs/nfs/nfs4proc.c | 19 ++++++-------
fs/ocfs2/xattr.c | 23 +++++++++-------
fs/orangefs/xattr.c | 10 ++++---
fs/overlayfs/inode.c | 5 ++--
fs/overlayfs/overlayfs.h | 5 ++--
fs/overlayfs/readdir.c | 4 +--
fs/posix_acl.c | 6 ++--
fs/readdir.c | 12 ++++----
fs/reiserfs/xattr_security.c | 9 +++---
fs/reiserfs/xattr_trusted.c | 9 +++---
fs/reiserfs/xattr_user.c | 9 +++---
fs/ubifs/xattr.c | 7 ++---
fs/xattr.c | 10 ++++---
fs/xfs/xfs_xattr.c | 9 +++---
include/linux/fs.h | 3 +-
include/linux/rwsem.h | 2 ++
include/linux/xattr.h | 7 +++--
kernel/locking/rwsem.c | 16 +++++++++++
mm/shmem.c | 7 +++--
security/smack/smack_lsm.c | 2 +-
58 files changed, 265 insertions(+), 209 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [git pull] vfs fixes
@ 2016-02-28 1:09 Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2016-02-28 1:09 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
The following changes since commit 7ae8fd0351f912b075149a1e03a017be8b903b9a:
fs/pnode.c: treat zero mnt_group_id-s as unequal (2016-02-20 00:15:52 -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 5129fa482b16615fd4464d2f5d23acb1b7056c66:
do_last(): ELOOP failure exit should be done after leaving RCU mode (2016-02-27 19:37:37 -0500)
----------------------------------------------------------------
Al Viro (4):
do_last(): don't let a bogus return value from ->open() et.al. to confuse us
namei: ->d_inode of a pinned dentry is stable only for positives
should_follow_link(): validate ->d_seq after having decided to follow
do_last(): ELOOP failure exit should be done after leaving RCU mode
Christoph Hellwig (1):
fs: return -EOPNOTSUPP if clone is not supported
Mikulas Patocka (1):
hpfs: don't truncate the file when delete fails
fs/hpfs/namei.c | 31 +++----------------------------
fs/namei.c | 22 +++++++++++++++-------
fs/read_write.c | 6 ++++--
3 files changed, 22 insertions(+), 37 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [git pull] vfs fixes
@ 2014-09-14 19:47 Al Viro
2014-09-26 20:38 ` Joachim Eastwood
2014-09-26 20:46 ` Joachim Eastwood
0 siblings, 2 replies; 188+ messages in thread
From: Al Viro @ 2014-09-14 19:47 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
double iput() on failure exit in lustre, racy removal of spliced dentries
from ->s_anon in __d_materialise_dentry() plus a bunch of assorted RCU pathwalk
fixes. Please, pull from the usual place -
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (5):
[fix] lustre: d_make_root() does iput() on dentry allocation failure
move the call of __d_drop(anon) into __d_materialise_unique(dentry, anon)
fix bogus read_seqretry() checks introduced in b37199e
don't bugger nd->seq on set_root_rcu() from follow_dotdot_rcu()
be careful with nd->inode in path_init() and follow_dotdot_rcu()
Diffstat:
drivers/staging/lustre/lustre/llite/llite_lib.c | 2 +-
fs/dcache.c | 8 +++-
fs/namei.c | 52 ++++++++++++++---------
3 files changed, 39 insertions(+), 23 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2014-09-14 19:47 Al Viro
@ 2014-09-26 20:38 ` Joachim Eastwood
2014-09-26 20:46 ` Joachim Eastwood
1 sibling, 0 replies; 188+ messages in thread
From: Joachim Eastwood @ 2014-09-26 20:38 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, linux-kernel@vger.kernel.org, linux-fsdevel
On 14 September 2014 21:47, Al Viro <viro@zeniv.linux.org.uk> wrote:
> double iput() on failure exit in lustre, racy removal of spliced dentries
> from ->s_anon in __d_materialise_dentry() plus a bunch of assorted RCU pathwalk
> fixes. Please, pull from the usual place -
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
>
> Shortlog:
> Al Viro (5):
> [fix] lustre: d_make_root() does iput() on dentry allocation failure
> move the call of __d_drop(anon) into __d_materialise_unique(dentry, anon)
> fix bogus read_seqretry() checks introduced in b37199e
> don't bugger nd->seq on set_root_rcu() from follow_dotdot_rcu()
> be careful with nd->inode in path_init() and follow_dotdot_rcu()
>
> Diffstat:
> drivers/staging/lustre/lustre/llite/llite_lib.c | 2 +-
> fs/dcache.c | 8 +++-
> fs/namei.c | 52 ++++++++++++++---------
> 3 files changed, 39 insertions(+), 23 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-09-14 19:47 Al Viro
2014-09-26 20:38 ` Joachim Eastwood
@ 2014-09-26 20:46 ` Joachim Eastwood
2014-09-26 20:58 ` Al Viro
1 sibling, 1 reply; 188+ messages in thread
From: Joachim Eastwood @ 2014-09-26 20:46 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, linux-kernel@vger.kernel.org, linux-fsdevel
On 14 September 2014 21:47, Al Viro <viro@zeniv.linux.org.uk> wrote:
> double iput() on failure exit in lustre, racy removal of spliced dentries
> from ->s_anon in __d_materialise_dentry() plus a bunch of assorted RCU pathwalk
> fixes. Please, pull from the usual place -
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
>
> Shortlog:
> Al Viro (5):
> [fix] lustre: d_make_root() does iput() on dentry allocation failure
> move the call of __d_drop(anon) into __d_materialise_unique(dentry, anon)
> fix bogus read_seqretry() checks introduced in b37199e
> don't bugger nd->seq on set_root_rcu() from follow_dotdot_rcu()
> be careful with nd->inode in path_init() and follow_dotdot_rcu()
Hi,
Commit 4023bfc9f351a7994 "be careful with nd->inode in path_init() and
follow_dotdot_rcu(), seem to hang my ARM no-MMU platform when mounting
the ramdisk.
3.17-rc4 - works
3.17-rc5 - works with 4023bfc9f351a7994 reverted.
Boot log with from rc5:
[ 5.810000] TCP: cubic registered
[ 5.820000] NET: Registered protocol family 17
[ 5.860000] lpc2k-rtc 40046000.rtc: hctosys: unable to read the hardware clock
[ 5.910000] mmc_host mmc0: Bus speed (slot 0) = 12000000Hz (slot req
25000000Hz, actual 12000000HZ div = 0)
[ 5.930000] mmc0: new SDHC card at address 0007
[ 5.950000] mmcblk0: mmc0:0007 SD08G 7.42 GiB
[ 6.150000] clk: Not disabling unused clocks
[ 81.240000] random: nonblocking pool is initialized
And there it just hangs it seems.
With patch reverted
[ 5.810000] TCP: cubic registered
[ 5.820000] NET: Registered protocol family 17
[ 5.850000] lpc2k-rtc 40046000.rtc: hctosys: unable to read the hardware clock
[ 6.100000] clk: Not disabling unused clocks
[ 6.110000] RAMDISK: gzip image found at block 0
[ 9.590000] VFS: Mounted root (ext2 filesystem) readonly on device 1:0.
[ 9.600000] devtmpfs: mounted
[ 9.610000] Freeing unused kernel memory: 68K (281e5000 - 281f6000)
And then user space starts.
This is an ARM Cortex-M4 no-MMU platform that is not yet upstream.
regards,
Joachim Eastwood
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-09-26 20:46 ` Joachim Eastwood
@ 2014-09-26 20:58 ` Al Viro
2014-09-26 21:28 ` Joachim Eastwood
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2014-09-26 20:58 UTC (permalink / raw)
To: Joachim Eastwood
Cc: Linus Torvalds, linux-kernel@vger.kernel.org, linux-fsdevel
On Fri, Sep 26, 2014 at 10:46:14PM +0200, Joachim Eastwood wrote:
> On 14 September 2014 21:47, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > double iput() on failure exit in lustre, racy removal of spliced dentries
> > from ->s_anon in __d_materialise_dentry() plus a bunch of assorted RCU pathwalk
> > fixes. Please, pull from the usual place -
> > git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
> >
> > Shortlog:
> > Al Viro (5):
> > [fix] lustre: d_make_root() does iput() on dentry allocation failure
> > move the call of __d_drop(anon) into __d_materialise_unique(dentry, anon)
> > fix bogus read_seqretry() checks introduced in b37199e
> > don't bugger nd->seq on set_root_rcu() from follow_dotdot_rcu()
> > be careful with nd->inode in path_init() and follow_dotdot_rcu()
>
> Hi,
>
> Commit 4023bfc9f351a7994 "be careful with nd->inode in path_init() and
> follow_dotdot_rcu(), seem to hang my ARM no-MMU platform when mounting
> the ramdisk.
>
> 3.17-rc4 - works
> 3.17-rc5 - works with 4023bfc9f351a7994 reverted.
>
> Boot log with from rc5:
> [ 5.810000] TCP: cubic registered
> [ 5.820000] NET: Registered protocol family 17
> [ 5.860000] lpc2k-rtc 40046000.rtc: hctosys: unable to read the hardware clock
> [ 5.910000] mmc_host mmc0: Bus speed (slot 0) = 12000000Hz (slot req
> 25000000Hz, actual 12000000HZ div = 0)
> [ 5.930000] mmc0: new SDHC card at address 0007
> [ 5.950000] mmcblk0: mmc0:0007 SD08G 7.42 GiB
> [ 6.150000] clk: Not disabling unused clocks
> [ 81.240000] random: nonblocking pool is initialized
>
> And there it just hangs it seems.
>
>
> With patch reverted
> [ 5.810000] TCP: cubic registered
> [ 5.820000] NET: Registered protocol family 17
> [ 5.850000] lpc2k-rtc 40046000.rtc: hctosys: unable to read the hardware clock
> [ 6.100000] clk: Not disabling unused clocks
> [ 6.110000] RAMDISK: gzip image found at block 0
> [ 9.590000] VFS: Mounted root (ext2 filesystem) readonly on device 1:0.
> [ 9.600000] devtmpfs: mounted
> [ 9.610000] Freeing unused kernel memory: 68K (281e5000 - 281f6000)
>
> And then user space starts.
*blink* What happens to mmc-related messages on successful boot? And what
in that commit could've possibly lead to those not being produced?
Another question: what happens if you revert a half of that commit? There
are two separate parts, easy to isolate - one in follow_dotdot_rcu(), another
in path_init(). They deal with similar problems, but they are independent
from each other; which one is triggering that crap?
Al, really mystified...
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-09-26 20:58 ` Al Viro
@ 2014-09-26 21:28 ` Joachim Eastwood
2014-09-26 21:52 ` Joachim Eastwood
0 siblings, 1 reply; 188+ messages in thread
From: Joachim Eastwood @ 2014-09-26 21:28 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, linux-kernel@vger.kernel.org, linux-fsdevel
On 26 September 2014 22:58, Al Viro <viro@zeniv.linux.org.uk> wrote:
> On Fri, Sep 26, 2014 at 10:46:14PM +0200, Joachim Eastwood wrote:
>> On 14 September 2014 21:47, Al Viro <viro@zeniv.linux.org.uk> wrote:
>> > double iput() on failure exit in lustre, racy removal of spliced dentries
>> > from ->s_anon in __d_materialise_dentry() plus a bunch of assorted RCU pathwalk
>> > fixes. Please, pull from the usual place -
>> > git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
>> >
>> > Shortlog:
>> > Al Viro (5):
>> > [fix] lustre: d_make_root() does iput() on dentry allocation failure
>> > move the call of __d_drop(anon) into __d_materialise_unique(dentry, anon)
>> > fix bogus read_seqretry() checks introduced in b37199e
>> > don't bugger nd->seq on set_root_rcu() from follow_dotdot_rcu()
>> > be careful with nd->inode in path_init() and follow_dotdot_rcu()
>>
>> Hi,
>>
>> Commit 4023bfc9f351a7994 "be careful with nd->inode in path_init() and
>> follow_dotdot_rcu(), seem to hang my ARM no-MMU platform when mounting
>> the ramdisk.
>>
>> 3.17-rc4 - works
>> 3.17-rc5 - works with 4023bfc9f351a7994 reverted.
>>
>> Boot log with from rc5:
>> [ 5.810000] TCP: cubic registered
>> [ 5.820000] NET: Registered protocol family 17
>> [ 5.860000] lpc2k-rtc 40046000.rtc: hctosys: unable to read the hardware clock
>> [ 5.910000] mmc_host mmc0: Bus speed (slot 0) = 12000000Hz (slot req
>> 25000000Hz, actual 12000000HZ div = 0)
>> [ 5.930000] mmc0: new SDHC card at address 0007
>> [ 5.950000] mmcblk0: mmc0:0007 SD08G 7.42 GiB
>> [ 6.150000] clk: Not disabling unused clocks
>> [ 81.240000] random: nonblocking pool is initialized
>>
>> And there it just hangs it seems.
>>
>>
>> With patch reverted
>> [ 5.810000] TCP: cubic registered
>> [ 5.820000] NET: Registered protocol family 17
>> [ 5.850000] lpc2k-rtc 40046000.rtc: hctosys: unable to read the hardware clock
>> [ 6.100000] clk: Not disabling unused clocks
>> [ 6.110000] RAMDISK: gzip image found at block 0
>> [ 9.590000] VFS: Mounted root (ext2 filesystem) readonly on device 1:0.
>> [ 9.600000] devtmpfs: mounted
>> [ 9.610000] Freeing unused kernel memory: 68K (281e5000 - 281f6000)
>>
>> And then user space starts.
>
> *blink* What happens to mmc-related messages on successful boot? And what
> in that commit could've possibly lead to those not being produced?
Now I am puzzled too. I can not longer reproduce that hang.
I am guessing it was probably related to the mmc card being flaky or
something random like that.
Sorry for noise!
regards,
Joachim Eastwood
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-09-26 21:28 ` Joachim Eastwood
@ 2014-09-26 21:52 ` Joachim Eastwood
0 siblings, 0 replies; 188+ messages in thread
From: Joachim Eastwood @ 2014-09-26 21:52 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, linux-kernel@vger.kernel.org, linux-fsdevel
On 26 September 2014 23:28, Joachim Eastwood <manabian@gmail.com> wrote:
> On 26 September 2014 22:58, Al Viro <viro@zeniv.linux.org.uk> wrote:
>> On Fri, Sep 26, 2014 at 10:46:14PM +0200, Joachim Eastwood wrote:
>>> On 14 September 2014 21:47, Al Viro <viro@zeniv.linux.org.uk> wrote:
>>> > double iput() on failure exit in lustre, racy removal of spliced dentries
>>> > from ->s_anon in __d_materialise_dentry() plus a bunch of assorted RCU pathwalk
>>> > fixes. Please, pull from the usual place -
>>> > git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
>>> >
>>> > Shortlog:
>>> > Al Viro (5):
>>> > [fix] lustre: d_make_root() does iput() on dentry allocation failure
>>> > move the call of __d_drop(anon) into __d_materialise_unique(dentry, anon)
>>> > fix bogus read_seqretry() checks introduced in b37199e
>>> > don't bugger nd->seq on set_root_rcu() from follow_dotdot_rcu()
>>> > be careful with nd->inode in path_init() and follow_dotdot_rcu()
>>>
>>> Hi,
>>>
>>> Commit 4023bfc9f351a7994 "be careful with nd->inode in path_init() and
>>> follow_dotdot_rcu(), seem to hang my ARM no-MMU platform when mounting
>>> the ramdisk.
>>>
>>> 3.17-rc4 - works
>>> 3.17-rc5 - works with 4023bfc9f351a7994 reverted.
>>>
>>> Boot log with from rc5:
>>> [ 5.810000] TCP: cubic registered
>>> [ 5.820000] NET: Registered protocol family 17
>>> [ 5.860000] lpc2k-rtc 40046000.rtc: hctosys: unable to read the hardware clock
>>> [ 5.910000] mmc_host mmc0: Bus speed (slot 0) = 12000000Hz (slot req
>>> 25000000Hz, actual 12000000HZ div = 0)
>>> [ 5.930000] mmc0: new SDHC card at address 0007
>>> [ 5.950000] mmcblk0: mmc0:0007 SD08G 7.42 GiB
>>> [ 6.150000] clk: Not disabling unused clocks
>>> [ 81.240000] random: nonblocking pool is initialized
>>>
>>> And there it just hangs it seems.
>>>
>>>
>>> With patch reverted
>>> [ 5.810000] TCP: cubic registered
>>> [ 5.820000] NET: Registered protocol family 17
>>> [ 5.850000] lpc2k-rtc 40046000.rtc: hctosys: unable to read the hardware clock
>>> [ 6.100000] clk: Not disabling unused clocks
>>> [ 6.110000] RAMDISK: gzip image found at block 0
>>> [ 9.590000] VFS: Mounted root (ext2 filesystem) readonly on device 1:0.
>>> [ 9.600000] devtmpfs: mounted
>>> [ 9.610000] Freeing unused kernel memory: 68K (281e5000 - 281f6000)
>>>
>>> And then user space starts.
>>
>> *blink* What happens to mmc-related messages on successful boot? And what
>> in that commit could've possibly lead to those not being produced?
>
> Now I am puzzled too. I can not longer reproduce that hang.
>
> I am guessing it was probably related to the mmc card being flaky or
> something random like that.
>
> Sorry for noise!
Just to confirm what was happening:
I managed to trigger it again and removing the mmc driver makes the
problem go away. So this is an mmc issue and _not_ vfs.
But what is strange is that reverting 4023bfc9f351a also makes it boot
again... Which is what fooled me.
Here are the boot logs just in case you want to have a look.
Boot log with hang: http://slexy.org/raw/s2eRhKN3aG
Boot ok (4023bfc9f351a reverted): http://slexy.org/raw/s21NgzZkCA
mmc is behaving differently.
Sorry for prematurely blaming vfs.
regards,
Joachim Eastwood
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
@ 2014-03-24 22:58 Imre Deak
2014-03-25 7:21 ` Sedat Dilek
0 siblings, 1 reply; 188+ messages in thread
From: Imre Deak @ 2014-03-24 22:58 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, linux-kernel, linux-fsdevel
> [...]
> Shortlog:
> Al Viro (6):
> make prepend_name() work correctly when called with negative
*buflen
A proper attribution for the above fix would have been nice. Tracking
down the bug was the main thing after all:
https://lkml.org/lkml/2014/3/12/620
--Imre
^ permalink raw reply [flat|nested] 188+ messages in thread
* [git pull] vfs fixes
@ 2014-03-23 7:16 Al Viro
2014-03-23 10:57 ` Sedat Dilek
2014-03-23 16:36 ` Linus Torvalds
0 siblings, 2 replies; 188+ messages in thread
From: Al Viro @ 2014-03-23 7:16 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
Several fixes; first 4 commits are obvious fixes (a couple
of fdget_pos()-related ones from Eric Biggers, prepend_name() fix, missing
checks for false negatives from __lookup_mnt() in fs/namei.c), followed
by 4 commits dealing with the bug found by Max last week - switch of
mnt_hash to hlist, to avoid the fun with non-terminating __lookup_mnt().
I'm fairly comfortable with that pile, but whether its second part is OK
at this point is up to you; it seems to survive everything I'd thrown
at it, and it's quite straightforward. If you really feel that it's
too close to -final, well... alternative variant is to replace the last
4 with "if we are spinning too much in __lookup_mnt(), check mount_lock"
kludge like the one I've posted early in the "don't clobber mnt_hash.next"
thread. I'd rather go for "let's just use hlist", obviously...
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (6):
make prepend_name() work correctly when called with negative *buflen
rcuwalk: recheck mount_lock after mountpoint crossing attempts
resizable namespace.c hashes
keep shadowed vfsmounts together
don't bother with propagate_mnt() unless the target is shared
switch mnt_hash to hlist
Eric Biggers (2):
vfs: atomic f_pos access in llseek()
vfs: Don't let __fdget_pos() get FMODE_PATH files
Diffstat:
fs/dcache.c | 4 +-
fs/file.c | 19 ++----
fs/mount.h | 4 +-
fs/namei.c | 29 ++++-----
fs/namespace.c | 177 ++++++++++++++++++++++++++++++++++++-------------------
fs/pnode.c | 26 ++++----
fs/pnode.h | 4 +-
fs/read_write.c | 4 +-
8 files changed, 155 insertions(+), 112 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2014-03-23 7:16 Al Viro
@ 2014-03-23 10:57 ` Sedat Dilek
2014-03-23 15:35 ` Al Viro
2014-03-23 16:36 ` Linus Torvalds
1 sibling, 1 reply; 188+ messages in thread
From: Sedat Dilek @ 2014-03-23 10:57 UTC (permalink / raw)
To: Al Viro; +Cc: Linus Torvalds, LKML, linux-fsdevel
[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]
On Sun, Mar 23, 2014 at 8:16 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> Several fixes; first 4 commits are obvious fixes (a couple
> of fdget_pos()-related ones from Eric Biggers, prepend_name() fix, missing
> checks for false negatives from __lookup_mnt() in fs/namei.c), followed
> by 4 commits dealing with the bug found by Max last week - switch of
> mnt_hash to hlist, to avoid the fun with non-terminating __lookup_mnt().
> I'm fairly comfortable with that pile, but whether its second part is OK
> at this point is up to you; it seems to survive everything I'd thrown
> at it, and it's quite straightforward. If you really feel that it's
> too close to -final, well... alternative variant is to replace the last
> 4 with "if we are spinning too much in __lookup_mnt(), check mount_lock"
> kludge like the one I've posted early in the "don't clobber mnt_hash.next"
> thread. I'd rather go for "let's just use hlist", obviously...
>
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
>
> Shortlog:
> Al Viro (6):
> make prepend_name() work correctly when called with negative *buflen
> rcuwalk: recheck mount_lock after mountpoint crossing attempts
> resizable namespace.c hashes
> keep shadowed vfsmounts together
> don't bother with propagate_mnt() unless the target is shared
> switch mnt_hash to hlist
>
> Eric Biggers (2):
> vfs: atomic f_pos access in llseek()
> vfs: Don't let __fdget_pos() get FMODE_PATH files
>
> Diffstat:
> fs/dcache.c | 4 +-
> fs/file.c | 19 ++----
> fs/mount.h | 4 +-
> fs/namei.c | 29 ++++-----
> fs/namespace.c | 177 ++++++++++++++++++++++++++++++++++++-------------------
> fs/pnode.c | 26 ++++----
> fs/pnode.h | 4 +-
> fs/read_write.c | 4 +-
> 8 files changed, 155 insertions(+), 112 deletions(-)
>
Your branch on top of Linux v3.14-rc7-66-g774868c7094d is freezing my
Ubuntu/precise AMD64 (WUBI) system when running LTP.
$ cat /opt/ltp/Version
20140115
Vanilla unmodified Linux v3.14-rc7-66-g774868c7094d is OK here.
Dunno how and with which apps you tested, but please verify on your
own with latest LTP release.
My kernel-config and dmesg are attached.
( I have taken a screenshot of the frozen system if you wanna look at. )
Regards,
- Sedat -
[-- Attachment #2: dmesg_3.14.0-rc7-4-iniza-small.txt --]
[-- Type: text/plain, Size: 54636 bytes --]
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.14.0-rc7-4-iniza-small (sedat.dilek@gmail.com@fambox) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1 SMP Sun Mar 23 09:24:30 CET 2014
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz.upstream root=UUID=001AADA61AAD9964 loop=/ubuntu/disks/root.disk ro
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Disabled fast string operations
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000040200000-0x00000000d9c9efff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000d9c9f000-0x00000000dae7efff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000dae7f000-0x00000000daf9efff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000daf9f000-0x00000000daffefff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000dafff000-0x00000000daffffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000db000000-0x00000000df9fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed08000-0x00000000fed08fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffd80000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000011fdfffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.6 present.
[ 0.000000] DMI: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH/530U3BI/530U4BI/530U4BH, BIOS 13XK 03/28/2013
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] No AGP bridge found
[ 0.000000] e820: last_pfn = 0x11fe00 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 base 080000000 mask FC0000000 write-back
[ 0.000000] 2 base 0C0000000 mask FE0000000 write-back
[ 0.000000] 3 base 0DC000000 mask FFC000000 uncachable
[ 0.000000] 4 base 0DB000000 mask FFF000000 uncachable
[ 0.000000] 5 base 100000000 mask FE0000000 write-back
[ 0.000000] 6 base 11FE00000 mask FFFE00000 uncachable
[ 0.000000] 7 base 0FFC00000 mask FFFC00000 write-protect
[ 0.000000] 8 disabled
[ 0.000000] 9 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] e820: last_pfn = 0xdb000 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [mem 0x000f00e0-0x000f00ef] mapped at [ffff8800000f00e0]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000097000] 97000 size 24576
[ 0.000000] reserving inaccessible SNB gfx pages
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] BRK [0x01fc7000, 0x01fc7fff] PGTABLE
[ 0.000000] BRK [0x01fc8000, 0x01fc8fff] PGTABLE
[ 0.000000] BRK [0x01fc9000, 0x01fc9fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x11fc00000-0x11fdfffff]
[ 0.000000] [mem 0x11fc00000-0x11fdfffff] page 2M
[ 0.000000] BRK [0x01fca000, 0x01fcafff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x11c000000-0x11fbfffff]
[ 0.000000] [mem 0x11c000000-0x11fbfffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x100000000-0x11bffffff]
[ 0.000000] [mem 0x100000000-0x11bffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0x1fffffff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0x1fffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x20200000-0x3fffffff]
[ 0.000000] [mem 0x20200000-0x3fffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x40200000-0xd9c9efff]
[ 0.000000] [mem 0x40200000-0xd9bfffff] page 2M
[ 0.000000] [mem 0xd9c00000-0xd9c9efff] page 4k
[ 0.000000] BRK [0x01fcb000, 0x01fcbfff] PGTABLE
[ 0.000000] BRK [0x01fcc000, 0x01fccfff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0xdafff000-0xdaffffff]
[ 0.000000] [mem 0xdafff000-0xdaffffff] page 4k
[ 0.000000] RAMDISK: [mem 0x37958000-0x37ca3fff]
[ 0.000000] ACPI: RSDP 00000000000f0100 000024 (v02 SECCSD)
[ 0.000000] ACPI: XSDT 00000000daffe170 00008C (v01 SECCSD LH43STAR 00000002 PTEC 00000002)
[ 0.000000] ACPI: FACP 00000000dafef000 00010C (v05 SECCSD LH43STAR 00000002 PTL 00000002)
[ 0.000000] ACPI: DSDT 00000000daff2000 0083AC (v02 SECCSD SNB-CPT 00000000 INTL 20061109)
[ 0.000000] ACPI: FACS 00000000daf47000 000040
[ 0.000000] ACPI: SLIC 00000000daffd000 000176 (v01 SECCSD LH43STAR 00000002 PTEC 00000001)
[ 0.000000] ACPI: SSDT 00000000daffb000 001068 (v01 SECCSD PtidDevc 00001000 INTL 20061109)
[ 0.000000] ACPI: ASF! 00000000daff1000 0000A5 (v32 SECCSD LH43STAR 00000002 PTL 00000002)
[ 0.000000] ACPI: HPET 00000000dafee000 000038 (v01 SECCSD LH43STAR 00000002 PTL 00000002)
[ 0.000000] ACPI: APIC 00000000dafed000 000098 (v03 SECCSD LH43STAR 00000002 PTL 00000002)
[ 0.000000] ACPI: MCFG 00000000dafec000 00003C (v01 SECCSD LH43STAR 00000002 PTL 00000002)
[ 0.000000] ACPI: SSDT 00000000dafeb000 000804 (v01 PmRef Cpu0Ist 00003000 INTL 20061109)
[ 0.000000] ACPI: SSDT 00000000dafea000 000996 (v01 PmRef CpuPm 00003000 INTL 20061109)
[ 0.000000] ACPI: UEFI 00000000dafe9000 00003E (v01 SECCSD LH43STAR 00000002 PTL 00000002)
[ 0.000000] ACPI: UEFI 00000000dafe8000 000042 (v01 PTL COMBUF 00000001 PTL 00000001)
[ 0.000000] ACPI: UEFI 00000000dafe7000 00026A (v01 SECCSD LH43STAR 00000002 PTL 00000002)
[ 0.000000] ACPI: SSDT 00000000dafe6000 0000D0 (v01 Iffs IffsAsl 00003000 INTL 20061109)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000011fdfffff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x11fdfffff]
[ 0.000000] NODE_DATA [mem 0x11fdf9000-0x11fdfcfff]
[ 0.000000] [ffffea0000000000-ffffea0003ffffff] PMD -> [ffff88011b400000-ffff88011edfffff] on node 0
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal [mem 0x100000000-0x11fdfffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x0009cfff]
[ 0.000000] node 0: [mem 0x00100000-0x1fffffff]
[ 0.000000] node 0: [mem 0x20200000-0x3fffffff]
[ 0.000000] node 0: [mem 0x40200000-0xd9c9efff]
[ 0.000000] node 0: [mem 0xdafff000-0xdaffffff]
[ 0.000000] node 0: [mem 0x100000000-0x11fdfffff]
[ 0.000000] On node 0 totalpages: 1021500
[ 0.000000] DMA zone: 56 pages used for memmap
[ 0.000000] DMA zone: 156 pages reserved
[ 0.000000] DMA zone: 3996 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 12127 pages used for memmap
[ 0.000000] DMA32 zone: 886944 pages, LIFO batch:31
[ 0.000000] Normal zone: 1785 pages used for memmap
[ 0.000000] Normal zone: 130560 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x00] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x00] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 14, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a301 base: 0xfed00000
[ 0.000000] smpboot: Allowing 8 CPUs, 4 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x20000000-0x201fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x40000000-0x401fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xd9c9f000-0xdae7efff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdae7f000-0xdaf9efff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdaf9f000-0xdaffefff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdb000000-0xdf9fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdfa00000-0xf7ffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfed07fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed08000-0xfed08fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed09000-0xfed0ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed1a000-0xfed1bfff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xffd7ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xffd80000-0xffffffff]
[ 0.000000] e820: [mem 0xdfa00000-0xf7ffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:8 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 29 pages/cpu @ffff88011fa00000 s86464 r8192 d24128 u262144
[ 0.000000] pcpu-alloc: s86464 r8192 d24128 u262144 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3 4 5 6 7
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 1007376
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz.upstream root=UUID=001AADA61AAD9964 loop=/ubuntu/disks/root.disk ro
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 3939168K/4086000K available (7331K kernel code, 1042K rwdata, 3224K rodata, 1344K init, 1440K bss, 146832K reserved)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=8.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[ 0.000000] NR_IRQS:16640 nr_irqs:744 16
[ 0.000000] Console: colour VGA+ 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 16777216 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 1596.493 MHz processor
[ 0.000040] Calibrating delay loop (skipped), value calculated using timer frequency.. 3192.98 BogoMIPS (lpj=6385972)
[ 0.000117] pid_max: default: 32768 minimum: 301
[ 0.000163] ACPI: Core revision 20131218
[ 0.006561] ACPI: All ACPI Tables successfully acquired
[ 0.022111] Security Framework initialized
[ 0.022156] AppArmor: AppArmor initialized
[ 0.022192] Yama: becoming mindful.
[ 0.022592] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.023694] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.024182] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.024229] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.024504] Initializing cgroup subsys memory
[ 0.024546] Initializing cgroup subsys devices
[ 0.024584] Initializing cgroup subsys freezer
[ 0.024621] Initializing cgroup subsys blkio
[ 0.024658] Initializing cgroup subsys perf_event
[ 0.024697] Initializing cgroup subsys hugetlb
[ 0.024759] Disabled fast string operations
[ 0.024796] CPU: Physical Processor ID: 0
[ 0.024832] CPU: Processor Core ID: 0
[ 0.024871] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.024871] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.024937] mce: CPU supports 7 MCE banks
[ 0.024985] CPU0: Thermal monitoring enabled (TM1)
[ 0.025030] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
[ 0.025030] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
[ 0.025030] tlb_flushall_shift: 6
[ 0.025211] Freeing SMP alternatives memory: 28K (ffffffff81e56000 - ffffffff81e5d000)
[ 0.026514] ftrace: allocating 27722 entries in 109 pages
[ 0.042248] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.082449] smpboot: CPU0: Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz (fam: 06, model: 2a, stepping: 07)
[ 0.082562] TSC deadline timer enabled
[ 0.085172] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, full-width counters, Intel PMU driver.
[ 0.085320] ... version: 3
[ 0.085356] ... bit width: 48
[ 0.085392] ... generic registers: 4
[ 0.085428] ... value mask: 0000ffffffffffff
[ 0.085465] ... max period: 0000ffffffffffff
[ 0.085503] ... fixed-purpose events: 3
[ 0.085539] ... event mask: 000000070000000f
[ 0.086911] x86: Booting SMP configuration:
[ 0.086949] .... node #0, CPUs: #1
[ 0.098036] Disabled fast string operations
[ 0.100276] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.100528] #2
[ 0.111577] Disabled fast string operations
[ 0.113826] #3<6>[ 0.124941] Disabled fast string operations
[ 0.127072] x86: Booted up 1 node, 4 CPUs
[ 0.127149] smpboot: Total of 4 processors activated (12771.94 BogoMIPS)
[ 0.131025] devtmpfs: initialized
[ 0.133848] EVM: security.selinux
[ 0.133885] EVM: security.SMACK64
[ 0.133919] EVM: security.capability
[ 0.134007] PM: Registering ACPI NVS region [mem 0xdae7f000-0xdaf9efff] (1179648 bytes)
[ 0.135081] regulator-dummy: no parameters
[ 0.135180] NET: Registered protocol family 16
[ 0.135354] cpuidle: using governor ladder
[ 0.135390] cpuidle: using governor menu
[ 0.135465] ACPI: bus type PCI registered
[ 0.135583] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.135642] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[ 0.142390] PCI: Using configuration type 1 for base access
[ 0.144043] bio: create slab <bio-0> at 0
[ 0.144250] ACPI: Added _OSI(Module Device)
[ 0.144288] ACPI: Added _OSI(Processor Device)
[ 0.144325] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.144362] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.174847] ACPI: Executed 1 blocks of module-level executable AML code
[ 0.177923] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.188300] ACPI: SSDT 00000000dae70718 000688 (v01 PmRef Cpu0Cst 00003001 INTL 20061109)
[ 0.188837] ACPI: Dynamic OEM Table Load:
[ 0.188907] ACPI: SSDT (null) 000688 (v01 PmRef Cpu0Cst 00003001 INTL 20061109)
[ 0.203126] ACPI: SSDT 00000000dae71a98 000303 (v01 PmRef ApIst 00003000 INTL 20061109)
[ 0.203701] ACPI: Dynamic OEM Table Load:
[ 0.203770] ACPI: SSDT (null) 000303 (v01 PmRef ApIst 00003000 INTL 20061109)
[ 0.215251] ACPI: SSDT 00000000dae6fd98 000119 (v01 PmRef ApCst 00003000 INTL 20061109)
[ 0.215778] ACPI: Dynamic OEM Table Load:
[ 0.215847] ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20061109)
[ 0.232472] ACPI: Interpreter enabled
[ 0.232520] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131218/hwxface-580)
[ 0.232624] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.232661] ACPI: Using IOAPIC for interrupt routing
[ 0.232731] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.232963] ACPI: No dock devices found.
[ 0.253584] ACPI: Power Resource [FN00] (off)
[ 0.253736] ACPI: Power Resource [FN01] (off)
[ 0.253883] ACPI: Power Resource [FN02] (off)
[ 0.254030] ACPI: Power Resource [FN03] (off)
[ 0.254175] ACPI: Power Resource [FN04] (off)
[ 0.254918] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[ 0.254962] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.255215] \_SB_.PCI0:_OSC invalid UUID
[ 0.255217] _OSC request data:1 1f 0
[ 0.255221] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[ 0.255795] PCI host bridge to bus 0000:00
[ 0.255834] pci_bus 0000:00: root bus resource [bus 00-3e]
[ 0.255873] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.255914] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.255954] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.255996] pci_bus 0000:00: root bus resource [mem 0xdfa00000-0xfeafffff]
[ 0.256038] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff]
[ 0.256087] pci 0000:00:00.0: [8086:0104] type 00 class 0x060000
[ 0.256198] pci 0000:00:02.0: [8086:0116] type 00 class 0x030000
[ 0.256211] pci 0000:00:02.0: reg 0x10: [mem 0xf0000000-0xf03fffff 64bit]
[ 0.256218] pci 0000:00:02.0: reg 0x18: [mem 0xe0000000-0xefffffff 64bit pref]
[ 0.256224] pci 0000:00:02.0: reg 0x20: [io 0x3000-0x303f]
[ 0.256359] pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
[ 0.256385] pci 0000:00:16.0: reg 0x10: [mem 0xf0705000-0xf070500f 64bit]
[ 0.256469] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[ 0.256583] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
[ 0.256607] pci 0000:00:1a.0: reg 0x10: [mem 0xf070a000-0xf070a3ff]
[ 0.256707] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[ 0.256809] pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
[ 0.256829] pci 0000:00:1b.0: reg 0x10: [mem 0xf0700000-0xf0703fff 64bit]
[ 0.256913] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.256967] pci 0000:00:1b.0: System wakeup disabled by ACPI
[ 0.257055] pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
[ 0.257146] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.257201] pci 0000:00:1c.0: System wakeup disabled by ACPI
[ 0.257292] pci 0000:00:1c.3: [8086:1c16] type 01 class 0x060400
[ 0.257382] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
[ 0.257438] pci 0000:00:1c.3: System wakeup disabled by ACPI
[ 0.257524] pci 0000:00:1c.4: [8086:1c18] type 01 class 0x060400
[ 0.257612] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[ 0.257722] pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
[ 0.257746] pci 0000:00:1d.0: reg 0x10: [mem 0xf0709000-0xf07093ff]
[ 0.257846] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[ 0.257946] pci 0000:00:1f.0: [8086:1c49] type 00 class 0x060100
[ 0.258148] pci 0000:00:1f.2: [8086:1c03] type 00 class 0x010601
[ 0.258170] pci 0000:00:1f.2: reg 0x10: [io 0x3088-0x308f]
[ 0.258180] pci 0000:00:1f.2: reg 0x14: [io 0x3094-0x3097]
[ 0.258190] pci 0000:00:1f.2: reg 0x18: [io 0x3080-0x3087]
[ 0.258200] pci 0000:00:1f.2: reg 0x1c: [io 0x3090-0x3093]
[ 0.258209] pci 0000:00:1f.2: reg 0x20: [io 0x3060-0x307f]
[ 0.258219] pci 0000:00:1f.2: reg 0x24: [mem 0xf0708000-0xf07087ff]
[ 0.258271] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.258363] pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
[ 0.258381] pci 0000:00:1f.3: reg 0x10: [mem 0xf0704000-0xf07040ff 64bit]
[ 0.258404] pci 0000:00:1f.3: reg 0x20: [io 0xefa0-0xefbf]
[ 0.258729] pci 0000:01:00.0: [8086:0091] type 00 class 0x028000
[ 0.258910] pci 0000:01:00.0: reg 0x10: [mem 0xf0600000-0xf0601fff 64bit]
[ 0.259687] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[ 0.259843] pci 0000:01:00.0: System wakeup disabled by ACPI
[ 0.267246] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 0.267290] pci 0000:00:1c.0: bridge window [mem 0xf0600000-0xf06fffff]
[ 0.267441] pci 0000:02:00.0: [10ec:8168] type 00 class 0x020000
[ 0.267511] pci 0000:02:00.0: reg 0x10: [io 0x2000-0x20ff]
[ 0.267634] pci 0000:02:00.0: reg 0x18: [mem 0xf0404000-0xf0404fff 64bit pref]
[ 0.267709] pci 0000:02:00.0: reg 0x20: [mem 0xf0400000-0xf0403fff 64bit pref]
[ 0.268114] pci 0000:02:00.0: supports D1 D2
[ 0.268116] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.268236] pci 0000:02:00.0: System wakeup disabled by ACPI
[ 0.275177] pci 0000:00:1c.3: PCI bridge to [bus 02]
[ 0.275239] pci 0000:00:1c.3: bridge window [io 0x2000-0x2fff]
[ 0.275249] pci 0000:00:1c.3: bridge window [mem 0xf0400000-0xf04fffff 64bit pref]
[ 0.275347] pci 0000:03:00.0: [1b21:1042] type 00 class 0x0c0330
[ 0.275385] pci 0000:03:00.0: reg 0x10: [mem 0xf0500000-0xf0507fff 64bit]
[ 0.275598] pci 0000:03:00.0: PME# supported from D3hot D3cold
[ 0.283150] pci 0000:00:1c.4: PCI bridge to [bus 03]
[ 0.283226] pci 0000:00:1c.4: bridge window [mem 0xf0500000-0xf05fffff]
[ 0.283738] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 10 *11 12 14 15)
[ 0.284038] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
[ 0.284382] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 *10 11 12 14 15)
[ 0.284677] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 *10 11 12 14 15)
[ 0.284972] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 10 11 12 14 15) *9
[ 0.285298] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 10 11 12 14 15) *0, disabled.
[ 0.285640] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 10 *11 12 14 15)
[ 0.285935] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 10 11 12 14 15) *9
[ 0.286523] ACPI: Enabled 4 GPEs in block 00 to 3F
[ 0.286641] ACPI : EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
[ 0.286933] ACPI : EC: 0 stale EC events cleared
[ 0.287145] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.287204] vgaarb: loaded
[ 0.287237] vgaarb: bridge control possible 0000:00:02.0
[ 0.287539] SCSI subsystem initialized
[ 0.287638] libata version 3.00 loaded.
[ 0.287667] ACPI: bus type USB registered
[ 0.287727] usbcore: registered new interface driver usbfs
[ 0.287778] usbcore: registered new interface driver hub
[ 0.287844] usbcore: registered new device driver usb
[ 0.288013] PCI: Using ACPI for IRQ routing
[ 0.289714] PCI: pci_cache_line_size set to 64 bytes
[ 0.289822] e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
[ 0.289824] e820: reserve RAM buffer [mem 0xd9c9f000-0xdbffffff]
[ 0.289826] e820: reserve RAM buffer [mem 0xdb000000-0xdbffffff]
[ 0.289828] e820: reserve RAM buffer [mem 0x11fe00000-0x11fffffff]
[ 0.289948] NetLabel: Initializing
[ 0.289983] NetLabel: domain hash size = 128
[ 0.290019] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.290069] NetLabel: unlabeled traffic allowed by default
[ 0.290168] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[ 0.290357] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[ 0.292421] Switched to clocksource hpet
[ 0.299936] AppArmor: AppArmor Filesystem Enabled
[ 0.300001] pnp: PnP ACPI init
[ 0.300050] ACPI: bus type PNP registered
[ 0.300467] pnp 00:00: [dma 4]
[ 0.300497] pnp 00:00: Plug and Play ACPI device, IDs PNP0200 (active)
[ 0.300527] pnp 00:01: Plug and Play ACPI device, IDs INT0800 (active)
[ 0.300635] pnp 00:02: Plug and Play ACPI device, IDs PNP0103 (active)
[ 0.300674] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 0.300730] system 00:04: [io 0x0680-0x069f] has been reserved
[ 0.300772] system 00:04: [io 0x1000-0x100f] has been reserved
[ 0.300812] system 00:04: [io 0x5000-0x5003] has been reserved
[ 0.300853] system 00:04: [io 0xffff] has been reserved
[ 0.300892] system 00:04: [io 0x0400-0x0453] could not be reserved
[ 0.300934] system 00:04: [io 0x0458-0x047f] has been reserved
[ 0.300974] system 00:04: [io 0x0500-0x057f] has been reserved
[ 0.301014] system 00:04: [io 0x0a00-0x0a0f] has been reserved
[ 0.301056] system 00:04: [io 0x164e-0x164f] has been reserved
[ 0.301096] system 00:04: [io 0x5000-0x500f] could not be reserved
[ 0.301138] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.301170] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.301229] system 00:06: [io 0x0454-0x0457] has been reserved
[ 0.301270] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[ 0.301309] pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active)
[ 0.301365] pnp 00:08: Plug and Play ACPI device, IDs ETD0b00 SYN0002 PNP0f13 (active)
[ 0.301552] system 00:09: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 0.301594] system 00:09: [mem 0xfed10000-0xfed17fff] has been reserved
[ 0.301636] system 00:09: [mem 0xfed18000-0xfed18fff] has been reserved
[ 0.301678] system 00:09: [mem 0xfed19000-0xfed19fff] has been reserved
[ 0.301720] system 00:09: [mem 0xf8000000-0xfbffffff] has been reserved
[ 0.301762] system 00:09: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 0.301804] system 00:09: [mem 0xfed90000-0xfed93fff] has been reserved
[ 0.301846] system 00:09: [mem 0xfed45000-0xfed8ffff] has been reserved
[ 0.301888] system 00:09: [mem 0xff000000-0xffffffff] could not be reserved
[ 0.301931] system 00:09: [mem 0xfee00000-0xfeefffff] could not be reserved
[ 0.301974] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.302538] system 00:0a: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.302567] pnp: PnP ACPI: found 11 devices
[ 0.302603] ACPI: bus type PNP unregistered
[ 0.309444] pci 0000:00:1c.0: PCI bridge to [bus 01]
[ 0.309489] pci 0000:00:1c.0: bridge window [mem 0xf0600000-0xf06fffff]
[ 0.309539] pci 0000:00:1c.3: PCI bridge to [bus 02]
[ 0.309579] pci 0000:00:1c.3: bridge window [io 0x2000-0x2fff]
[ 0.309626] pci 0000:00:1c.3: bridge window [mem 0xf0400000-0xf04fffff 64bit pref]
[ 0.309686] pci 0000:00:1c.4: PCI bridge to [bus 03]
[ 0.309728] pci 0000:00:1c.4: bridge window [mem 0xf0500000-0xf05fffff]
[ 0.309779] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 0.309781] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 0.309783] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.309785] pci_bus 0000:00: resource 7 [mem 0xdfa00000-0xfeafffff]
[ 0.309787] pci_bus 0000:00: resource 8 [mem 0xfed40000-0xfed44fff]
[ 0.309789] pci_bus 0000:01: resource 1 [mem 0xf0600000-0xf06fffff]
[ 0.309791] pci_bus 0000:02: resource 0 [io 0x2000-0x2fff]
[ 0.309793] pci_bus 0000:02: resource 2 [mem 0xf0400000-0xf04fffff 64bit pref]
[ 0.309795] pci_bus 0000:03: resource 1 [mem 0xf0500000-0xf05fffff]
[ 0.309860] NET: Registered protocol family 2
[ 0.310087] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
[ 0.310239] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[ 0.310378] TCP: Hash tables configured (established 32768 bind 32768)
[ 0.310450] TCP: reno registered
[ 0.310493] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[ 0.310550] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[ 0.310680] NET: Registered protocol family 1
[ 0.310729] pci 0000:00:02.0: Boot video device
[ 0.311347] PCI: CLS 64 bytes, default 64
[ 0.311396] Trying to unpack rootfs image as initramfs...
[ 0.380869] Freeing initrd memory: 3376K (ffff880037958000 - ffff880037ca4000)
[ 0.380929] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.380971] software IO TLB [mem 0xd5c9f000-0xd9c9f000] (64MB) mapped at [ffff8800d5c9f000-ffff8800d9c9efff]
[ 0.381310] RAPL PMU detected, hw unit 2^-16 Joules, API unit is 2^-32 Joules, 3 fixed counters 163840 ms ovfl timer
[ 0.381418] microcode: CPU0 sig=0x206a7, pf=0x10, revision=0x28
[ 0.381465] microcode: CPU1 sig=0x206a7, pf=0x10, revision=0x28
[ 0.381516] microcode: CPU2 sig=0x206a7, pf=0x10, revision=0x28
[ 0.381565] microcode: CPU3 sig=0x206a7, pf=0x10, revision=0x28
[ 0.381663] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 0.381736] Scanning for low memory corruption every 60 seconds
[ 0.382670] futex hash table entries: 2048 (order: 5, 131072 bytes)
[ 0.382743] Initialise system trusted keyring
[ 0.382824] audit: initializing netlink subsys (disabled)
[ 0.382880] audit: type=2000 audit(1395566853.364:1): initialized
[ 0.414308] bounce pool size: 64 pages
[ 0.414357] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.414638] VFS: Disk quotas dquot_6.5.2
[ 0.414699] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.415085] fuse init (API version 7.22)
[ 0.415185] msgmni has been set to 7700
[ 0.415654] Key type asymmetric registered
[ 0.415692] Asymmetric key parser 'x509' registered
[ 0.415748] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.415840] io scheduler noop registered
[ 0.415878] io scheduler deadline registered (default)
[ 0.415934] io scheduler cfq registered
[ 0.416413] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.416469] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.416589] intel_idle: MWAIT substates: 0x21120
[ 0.416590] intel_idle: v0.4 model 0x2A
[ 0.416592] intel_idle: lapic_timer_reliable_states 0xffffffff
[ 0.417193] ACPI: AC Adapter [ADP1] (on-line)
[ 0.417440] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input0
[ 0.417707] ACPI: Lid Switch [LID0]
[ 0.417800] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
[ 0.417859] ACPI: Power Button [PWRB]
[ 0.417944] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 0.417999] ACPI: Power Button [PWRF]
[ 0.418102] ACPI: Fan [FAN0] (off)
[ 0.418169] ACPI: Fan [FAN1] (off)
[ 0.418235] ACPI: Fan [FAN2] (off)
[ 0.418299] ACPI: Fan [FAN3] (off)
[ 0.418366] ACPI: Fan [FAN4] (off)
[ 0.419446] thermal LNXTHERM:00: registered as thermal_zone0
[ 0.419487] ACPI: Thermal Zone [TZ00] (65 C)
[ 0.419761] thermal LNXTHERM:01: registered as thermal_zone1
[ 0.419801] ACPI: Thermal Zone [TZ01] (30 C)
[ 0.419869] GHES: HEST is not enabled!
[ 0.419999] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 0.423671] Linux agpgart interface v0.103
[ 0.425610] brd: module loaded
[ 0.426398] ACPI: Battery Slot [BAT1] (battery present)
[ 0.426609] loop: module loaded
[ 0.426829] mei_me 0000:00:16.0: irq 40 for MSI/MSI-X
[ 0.429765] ahci 0000:00:1f.2: version 3.0
[ 0.429882] ahci 0000:00:1f.2: irq 41 for MSI/MSI-X
[ 0.429915] ahci 0000:00:1f.2: SSS flag set, parallel bus scan disabled
[ 0.444351] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x1b impl SATA mode
[ 0.444407] ahci 0000:00:1f.2: flags: 64bit ncq sntf ilck stag pm led clo pio slum part ems sxs apst
[ 0.469142] scsi0 : ahci
[ 0.469479] scsi1 : ahci
[ 0.469713] scsi2 : ahci
[ 0.469933] scsi3 : ahci
[ 0.470109] scsi4 : ahci
[ 0.470287] scsi5 : ahci
[ 0.470377] ata1: SATA max UDMA/133 abar m2048@0xf0708000 port 0xf0708100 irq 41
[ 0.470430] ata2: SATA max UDMA/133 abar m2048@0xf0708000 port 0xf0708180 irq 41
[ 0.470481] ata3: DUMMY
[ 0.470514] ata4: SATA max UDMA/133 abar m2048@0xf0708000 port 0xf0708280 irq 41
[ 0.470567] ata5: SATA max UDMA/133 abar m2048@0xf0708000 port 0xf0708300 irq 41
[ 0.470618] ata6: DUMMY
[ 0.471094] libphy: Fixed MDIO Bus: probed
[ 0.471258] tun: Universal TUN/TAP device driver, 1.6
[ 0.471295] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 0.471406] PPP generic driver version 2.4.2
[ 0.471494] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.471535] ehci-pci: EHCI PCI platform driver
[ 0.471728] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 0.471771] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 0.471839] ehci-pci 0000:00:1a.0: debug port 2
[ 0.475782] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[ 0.475801] ehci-pci 0000:00:1a.0: irq 16, io mem 0xf070a000
[ 0.484306] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 0.484386] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.484428] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.484481] usb usb1: Product: EHCI Host Controller
[ 0.484519] usb usb1: Manufacturer: Linux 3.14.0-rc7-4-iniza-small ehci_hcd
[ 0.484560] usb usb1: SerialNumber: 0000:00:1a.0
[ 0.484740] hub 1-0:1.0: USB hub found
[ 0.484784] hub 1-0:1.0: 2 ports detected
[ 0.485034] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 0.485077] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 0.485144] ehci-pci 0000:00:1d.0: debug port 2
[ 0.489076] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 0.489093] ehci-pci 0000:00:1d.0: irq 23, io mem 0xf0709000
[ 0.500289] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 0.500362] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.500404] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.500457] usb usb2: Product: EHCI Host Controller
[ 0.500494] usb usb2: Manufacturer: Linux 3.14.0-rc7-4-iniza-small ehci_hcd
[ 0.500535] usb usb2: SerialNumber: 0000:00:1d.0
[ 0.500703] hub 2-0:1.0: USB hub found
[ 0.500745] hub 2-0:1.0: 2 ports detected
[ 0.500889] ehci-platform: EHCI generic platform driver
[ 0.500936] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.500981] ohci-pci: OHCI PCI platform driver
[ 0.501028] ohci-platform: OHCI generic platform driver
[ 0.501073] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.501216] xhci_hcd 0000:03:00.0: xHCI Host Controller
[ 0.501258] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 3
[ 0.511023] xhci_hcd 0000:03:00.0: irq 42 for MSI/MSI-X
[ 0.511029] xhci_hcd 0000:03:00.0: irq 43 for MSI/MSI-X
[ 0.511035] xhci_hcd 0000:03:00.0: irq 44 for MSI/MSI-X
[ 0.511041] xhci_hcd 0000:03:00.0: irq 45 for MSI/MSI-X
[ 0.511046] xhci_hcd 0000:03:00.0: irq 46 for MSI/MSI-X
[ 0.511187] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.511228] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.511282] usb usb3: Product: xHCI Host Controller
[ 0.511320] usb usb3: Manufacturer: Linux 3.14.0-rc7-4-iniza-small xhci_hcd
[ 0.511361] usb usb3: SerialNumber: 0000:03:00.0
[ 0.511525] hub 3-0:1.0: USB hub found
[ 0.511571] hub 3-0:1.0: 2 ports detected
[ 0.511705] xhci_hcd 0000:03:00.0: xHCI Host Controller
[ 0.511745] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 4
[ 0.511857] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 0.511898] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.511951] usb usb4: Product: xHCI Host Controller
[ 0.511989] usb usb4: Manufacturer: Linux 3.14.0-rc7-4-iniza-small xhci_hcd
[ 0.512030] usb usb4: SerialNumber: 0000:03:00.0
[ 0.512185] hub 4-0:1.0: USB hub found
[ 0.512231] hub 4-0:1.0: 2 ports detected
[ 0.512423] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:EPAD] at 0x60,0x64 irq 1,12
[ 0.518748] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.518790] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.518980] mousedev: PS/2 mouse device common for all mice
[ 0.519368] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
[ 0.519438] rtc_cmos 00:05: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[ 0.519533] device-mapper: uevent: version 1.0.3
[ 0.519635] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
[ 0.519696] Intel P-state driver initializing.
[ 0.519741] Intel pstate controlling: cpu 0
[ 0.519801] Intel pstate controlling: cpu 1
[ 0.519863] Intel pstate controlling: cpu 2
[ 0.519912] Intel pstate controlling: cpu 3
[ 0.519981] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.520240] ashmem: initialized
[ 0.520405] TCP: cubic registered
[ 0.520533] NET: Registered protocol family 10
[ 0.520767] NET: Registered protocol family 17
[ 0.520814] Key type dns_resolver registered
[ 0.521149] Loading compiled-in X.509 certificates
[ 0.522258] Loaded X.509 cert 'Magrathea: Glacier signing key: 85f5eebb1283fe0f9148fd35a674ea6dad1752c5'
[ 0.522328] registered taskstats version 1
[ 0.525075] Key type trusted registered
[ 0.526998] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[ 0.527531] Key type encrypted registered
[ 0.529986] AppArmor: AppArmor sha1 policy hashing enabled
[ 0.530347] regulator-dummy: disabling
[ 0.530515] rtc_cmos 00:05: setting system clock to 2014-03-23 09:27:34 UTC (1395566854)
[ 0.530642] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 0.530682] EDD information not available.
[ 0.788207] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 0.789380] ata1.00: ATA-8: Hitachi HTS545050A7E380, GG2OA6C0, max UDMA/133
[ 0.789461] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 0.790765] ata1.00: configured for UDMA/133
[ 0.791087] scsi 0:0:0:0: Direct-Access ATA Hitachi HTS54505 GG2O PQ: 0 ANSI: 5
[ 0.791332] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 0.791346] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 0.791463] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 0.791614] sd 0:0:0:0: [sda] Write Protect is off
[ 0.791662] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 0.791751] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 0.796097] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 0.809722] sda: sda1 sda2 sda3
[ 0.810503] sd 0:0:0:0: [sda] Attached SCSI disk
[ 0.928610] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[ 0.928670] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 0.929714] hub 1-1:1.0: USB hub found
[ 0.929881] hub 1-1:1.0: 6 ports detected
[ 1.040108] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 1.107980] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.108617] ata2.00: ATA-8: SanDisk iSSD P4 16GB, SSD 9.14, max UDMA/133
[ 1.108674] ata2.00: 31277232 sectors, multi 1: LBA48
[ 1.109384] ata2.00: configured for UDMA/133
[ 1.109678] scsi 1:0:0:0: Direct-Access ATA SanDisk iSSD P4 SSD PQ: 0 ANSI: 5
[ 1.109930] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 1.109950] sd 1:0:0:0: [sdb] 31277232 512-byte logical blocks: (16.0 GB/14.9 GiB)
[ 1.110105] sd 1:0:0:0: [sdb] Write Protect is off
[ 1.110161] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.110213] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.111113] sdb: sdb1 sdb2
[ 1.111510] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 1.172135] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[ 1.172178] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.172413] hub 2-1:1.0: USB hub found
[ 1.172508] hub 2-1:1.0: 6 ports detected
[ 1.287176] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 1.299973] usb 4-1: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 1.300552] usb 4-1: New USB device found, idVendor=174c, idProduct=55aa
[ 1.300592] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 1.300634] usb 4-1: Product: MEDION HDDrive-n-GO
[ 1.300671] usb 4-1: Manufacturer: MEDION
[ 1.300708] usb 4-1: SerialNumber: 3180000000000000092C
[ 1.371750] usb 1-1.4: new high-speed USB device number 3 using ehci-pci
[ 1.379664] tsc: Refined TSC clocksource calibration: 1596.374 MHz
[ 1.427658] ata4: SATA link down (SStatus 0 SControl 300)
[ 1.623309] usb 1-1.4: New USB device found, idVendor=2232, idProduct=1018
[ 1.623349] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.623401] usb 1-1.4: Product: WebCam SC-13HDL11431N
[ 1.623437] usb 1-1.4: Manufacturer: 123
[ 1.747427] ata5: SATA link down (SStatus 0 SControl 300)
[ 1.748708] Freeing unused kernel memory: 1344K (ffffffff81d06000 - ffffffff81e56000)
[ 1.748762] Write protecting the kernel read-only data: 12288k
[ 1.751029] Freeing unused kernel memory: 848K (ffff88000172c000 - ffff880001800000)
[ 1.753284] Freeing unused kernel memory: 872K (ffff880001b26000 - ffff880001c00000)
[ 1.771251] udevd[127]: starting version 175
[ 1.836112] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.836174] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.836690] r8169 0000:02:00.0: irq 47 for MSI/MSI-X
[ 1.836982] r8169 0000:02:00.0 eth0: RTL8168evl/8111evl at 0xffffc9000000e000, e8:03:9a:36:17:a9, XID 0c900800 IRQ 47
[ 1.837055] r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 1.851594] usb-storage 4-1:1.0: USB Mass Storage device detected
[ 1.853084] usb-storage 4-1:1.0: Quirks match for vid 174c pid 55aa: 400000
[ 1.853169] scsi6 : usb-storage 4-1:1.0
[ 1.853323] usbcore: registered new interface driver usb-storage
[ 1.867396] usb 2-1.4: new low-speed USB device number 3 using ehci-pci
[ 1.965082] usb 2-1.4: New USB device found, idVendor=046d, idProduct=c00e
[ 1.965168] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.965232] usb 2-1.4: Product: USB-PS/2 Optical Mouse
[ 1.965270] usb 2-1.4: Manufacturer: Logitech
[ 2.039473] usb 2-1.5: new full-speed USB device number 4 using ehci-pci
[ 2.135976] usb 2-1.5: New USB device found, idVendor=8086, idProduct=0189
[ 2.136056] usb 2-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.142841] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.148314] usbcore: registered new interface driver usbhid
[ 2.148356] usbhid: USB HID core driver
[ 2.151495] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/0003:046D:C00E.0001/input/input6
[ 2.151706] hid-generic 0003:046D:C00E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1.4/input0
[ 2.379076] Switched to clocksource tsc
[ 2.782797] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[ 2.850962] scsi 6:0:0:0: Direct-Access ASMT 2105 0 PQ: 0 ANSI: 6
[ 2.851353] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 2.851702] sd 6:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 2.851765] sd 6:0:0:0: [sdc] 4096-byte physical blocks
[ 2.852236] sd 6:0:0:0: [sdc] Write Protect is off
[ 2.852279] sd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 2.852699] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.854320] sdc: sdc1 sdc2 sdc3
[ 2.855731] sd 6:0:0:0: [sdc] Attached SCSI disk
[ 2.983956] random: nonblocking pool is initialized
[ 4.858482] init: ureadahead main process (339) terminated with status 5
[ 7.521695] Adding 262140k swap on /host/ubuntu/disks/swap.disk. Priority:-1 extents:1 across:262140k FS
[ 7.655401] EXT4-fs (loop0): re-mounted. Opts: errors=remount-ro
[ 7.828230] udevd[627]: starting version 175
[ 8.745447] lp: driver loaded but no devices found
[ 10.736880] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\PMIO) (20131218/utaddress-258)
[ 10.736891] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 10.736896] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
[ 10.736902] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 10.736904] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
[ 10.736909] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 10.736911] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20131218/utaddress-258)
[ 10.736915] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 10.736917] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 10.828234] samsung_laptop: detected SABI interface: SwSmi@
[ 10.828239] samsung_laptop: Backlight controlled by ACPI video driver
[ 10.835581] wmi: Mapper loaded
[ 11.231063] cfg80211: Calling CRDA to update world regulatory domain
[ 11.291487] [drm] Initialized drm 1.1.0 20060810
[ 11.373314] Bluetooth: Core ver 2.18
[ 11.373339] NET: Registered protocol family 31
[ 11.373341] Bluetooth: HCI device and connection manager initialized
[ 11.373349] Bluetooth: HCI socket layer initialized
[ 11.373351] Bluetooth: L2CAP socket layer initialized
[ 11.373362] Bluetooth: SCO socket layer initialized
[ 11.635589] usbcore: registered new interface driver btusb
[ 11.860767] Intel(R) Wireless WiFi driver for Linux, in-tree:
[ 11.860770] Copyright(c) 2003- 2014 Intel Corporation
[ 11.860958] iwlwifi 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 11.861113] iwlwifi 0000:01:00.0: irq 48 for MSI/MSI-X
[ 11.942332] Linux video capture interface: v2.00
[ 12.199308] psmouse serio1: elantech: assuming hardware version 3 (with firmware version 0x450f00)
[ 12.218596] psmouse serio1: elantech: Synaptics capabilities query result 0x08, 0x17, 0x0c.
[ 12.292677] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7
[ 12.766234] [drm] Memory usable by graphics device = 2048M
[ 12.819669] i915 0000:00:02.0: irq 49 for MSI/MSI-X
[ 12.819679] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 12.819680] [drm] Driver supports precise vblank timestamp query.
[ 12.819751] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 12.835791] [drm] Wrong MCH_SSKPD value: 0x16040307
[ 12.835795] [drm] This can cause pipe underruns and display issues.
[ 12.835797] [drm] Please upgrade your BIOS to fix this.
[ 12.849517] uvcvideo: Found UVC 1.00 device WebCam SC-13HDL11431N (2232:1018)
[ 12.849885] iwlwifi 0000:01:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm
[ 12.853445] fbcon: inteldrmfb (fb0) is primary device
[ 12.856230] cfg80211: World regulatory domain updated:
[ 12.856232] cfg80211: DFS Master region: unset
[ 12.856232] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 12.856233] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 12.856234] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 12.856235] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 12.856236] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 12.856236] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 12.868745] input: WebCam SC-13HDL11431N as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input8
[ 12.868834] usbcore: registered new interface driver uvcvideo
[ 12.868835] USB Video Class driver (1.1.1)
[ 13.187393] audit: type=1400 audit(1395563267.164:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=919 comm="apparmor_parser"
[ 13.187398] audit: type=1400 audit(1395563267.164:3): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=919 comm="apparmor_parser"
[ 13.187400] audit: type=1400 audit(1395563267.164:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=919 comm="apparmor_parser"
[ 13.187426] audit: type=1400 audit(1395563267.164:5): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=880 comm="apparmor_parser"
[ 13.187431] audit: type=1400 audit(1395563267.164:6): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=880 comm="apparmor_parser"
[ 13.187434] audit: type=1400 audit(1395563267.164:7): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=880 comm="apparmor_parser"
[ 13.188161] audit: type=1400 audit(1395563267.164:8): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=880 comm="apparmor_parser"
[ 13.188166] audit: type=1400 audit(1395563267.164:9): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=880 comm="apparmor_parser"
[ 13.188176] audit: type=1400 audit(1395563267.164:10): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=919 comm="apparmor_parser"
[ 13.188182] audit: type=1400 audit(1395563267.164:11): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=919 comm="apparmor_parser"
[ 13.893322] Console: switching to colour frame buffer device 170x48
[ 13.895645] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 13.895646] i915 0000:00:02.0: registered panic notifier
[ 13.907591] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[ 13.907887] acpi device:33: registered as cooling_device9
[ 13.907981] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input9
[ 13.908085] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 13.908308] snd_hda_intel 0000:00:1b.0: irq 50 for MSI/MSI-X
[ 14.580341] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 14.580459] input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 14.580563] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 14.774087] iwlwifi 0000:01:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 14.774093] iwlwifi 0000:01:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
[ 14.774096] iwlwifi 0000:01:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 14.774100] iwlwifi 0000:01:00.0: Detected Intel(R) Centrino(R) Advanced-N 6230 AGN, REV=0xB0
[ 14.774250] iwlwifi 0000:01:00.0: L1 Enabled; Disabling L0S
[ 14.830496] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 14.957064] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 14.963856] ppdev: user-space parallel port driver
[ 15.302492] Bluetooth: RFCOMM TTY layer initialized
[ 15.302505] Bluetooth: RFCOMM socket layer initialized
[ 15.302512] Bluetooth: RFCOMM ver 1.11
[ 15.430771] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.430776] Bluetooth: BNEP filters: protocol multicast
[ 15.430787] Bluetooth: BNEP socket layer initialized
[ 15.698030] init: failsafe main process (1029) killed by TERM signal
[ 20.116530] r8169 0000:02:00.0 eth0: link down
[ 20.116560] r8169 0000:02:00.0 eth0: link down
[ 20.116589] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.859616] r8169 0000:02:00.0 eth0: link up
[ 22.859626] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 47.599684] EXT4-fs (sdc3): mounted filesystem with ordered data mode. Opts: (null)
[ 47.611971] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[ 56.003427] usb 2-1.5: USB disconnect, device number 4
[-- Attachment #3: config-3.14.0-rc7-4-iniza-small --]
[-- Type: application/octet-stream, Size: 118275 bytes --]
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 3.14.0-rc7 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_ARCH_HAS_CPU_AUTOPROBE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ZONE_DMA32=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_HAVE_INTEL_TXT=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11"
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_FHANDLE=y
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y
#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_IRQ_DOMAIN=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y
#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
#
# CPU/Task time and stats accounting
#
CONFIG_VIRT_CPU_ACCOUNTING=y
# CONFIG_TICK_CPU_ACCOUNTING is not set
CONFIG_VIRT_CPU_ACCOUNTING_GEN=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_PREEMPT_RCU is not set
CONFIG_RCU_STALL_COMMON=y
CONFIG_CONTEXT_TRACKING=y
CONFIG_RCU_USER_QS=y
CONFIG_CONTEXT_TRACKING_FORCE=y
CONFIG_RCU_FANOUT=64
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_RCU_FAST_NO_HZ is not set
# CONFIG_TREE_RCU_TRACE is not set
CONFIG_RCU_NOCB_CPU=y
CONFIG_RCU_NOCB_CPU_NONE=y
# CONFIG_RCU_NOCB_CPU_ZERO is not set
# CONFIG_RCU_NOCB_CPU_ALL is not set
CONFIG_IKCONFIG=m
# CONFIG_IKCONFIG_PROC is not set
CONFIG_LOG_BUF_SHIFT=18
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_ARCH_SUPPORTS_INT128=y
CONFIG_ARCH_WANTS_PROT_NUMA_PROT_NONE=y
# CONFIG_NUMA_BALANCING is not set
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
# CONFIG_MEMCG_SWAP_ENABLED is not set
# CONFIG_MEMCG_KMEM is not set
CONFIG_CGROUP_HUGETLB=y
CONFIG_CGROUP_PERF=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CFS_BANDWIDTH=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not set
CONFIG_CHECKPOINT_RESTORE=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_SCHED_AUTOGROUP=y
CONFIG_MM_OWNER=y
# CONFIG_SYSFS_DEPRECATED is not set
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
# CONFIG_RD_LZ4 is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_HAVE_UID16=y
CONFIG_SYSCTL_EXCEPTION_TRACE=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
CONFIG_EXPERT=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_PCI_QUIRKS=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
# CONFIG_COMPAT_BRK is not set
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
CONFIG_TRACEPOINTS=y
# CONFIG_OPROFILE is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_OPROFILE_NMI_TIMER=y
CONFIG_KPROBES=y
CONFIG_JUMP_LABEL=y
CONFIG_OPTPROBES=y
CONFIG_KPROBES_ON_FTRACE=y
CONFIG_UPROBES=y
# CONFIG_HAVE_64BIT_ALIGNED_ACCESS is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_ARCH_USE_BUILTIN_BSWAP=y
CONFIG_KRETPROBES=y
CONFIG_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_KPROBES_ON_FTRACE=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
CONFIG_HAVE_CMPXCHG_LOCAL=y
CONFIG_HAVE_CMPXCHG_DOUBLE=y
CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y
CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP_FILTER=y
CONFIG_HAVE_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR is not set
CONFIG_CC_STACKPROTECTOR_NONE=y
# CONFIG_CC_STACKPROTECTOR_REGULAR is not set
# CONFIG_CC_STACKPROTECTOR_STRONG is not set
CONFIG_HAVE_CONTEXT_TRACKING=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
CONFIG_HAVE_ARCH_SOFT_DIRTY=y
CONFIG_MODULES_USE_ELF_RELA=y
CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=y
CONFIG_OLD_SIGSUSPEND3=y
CONFIG_COMPAT_OLD_SIGACTION=y
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_SYSTEM_TRUSTED_KEYRING=y
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set
CONFIG_MODULE_SIG_ALL=y
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not set
# CONFIG_MODULE_SIG_SHA256 is not set
# CONFIG_MODULE_SIG_SHA384 is not set
CONFIG_MODULE_SIG_SHA512=y
CONFIG_MODULE_SIG_HASH="sha512"
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_BSGLIB=y
CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_CMDLINE_PARSER is not set
#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
# CONFIG_ACORN_PARTITION_CUMANA is not set
# CONFIG_ACORN_PARTITION_EESOX is not set
CONFIG_ACORN_PARTITION_ICS=y
# CONFIG_ACORN_PARTITION_ADFS is not set
# CONFIG_ACORN_PARTITION_POWERTEC is not set
CONFIG_ACORN_PARTITION_RISCIX=y
# CONFIG_AIX_PARTITION is not set
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
CONFIG_SYSV68_PARTITION=y
# CONFIG_CMDLINE_PARTITION is not set
CONFIG_BLOCK_COMPAT=y
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_CFQ_GROUP_IOSCHED=y
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="deadline"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_ASN1=y
CONFIG_UNINLINE_SPIN_UNLOCK=y
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
CONFIG_INLINE_READ_UNLOCK=y
CONFIG_INLINE_READ_UNLOCK_IRQ=y
CONFIG_INLINE_WRITE_UNLOCK=y
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_FREEZER=y
#
# Processor type and features
#
CONFIG_ZONE_DMA=y
CONFIG_SMP=y
CONFIG_X86_X2APIC=y
CONFIG_X86_MPPARSE=y
CONFIG_X86_EXTENDED_PLATFORM=y
CONFIG_X86_NUMACHIP=y
# CONFIG_X86_VSMP is not set
# CONFIG_X86_UV is not set
# CONFIG_X86_INTEL_LPSS is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_HYPERVISOR_GUEST=y
CONFIG_PARAVIRT=y
# CONFIG_PARAVIRT_DEBUG is not set
CONFIG_PARAVIRT_SPINLOCKS=y
CONFIG_XEN=y
CONFIG_XEN_DOM0=y
CONFIG_XEN_PRIVILEGED_GUEST=y
CONFIG_XEN_PVHVM=y
CONFIG_XEN_MAX_DOMAIN_MEMORY=500
CONFIG_XEN_SAVE_RESTORE=y
# CONFIG_XEN_DEBUG_FS is not set
# CONFIG_XEN_PVH is not set
CONFIG_KVM_GUEST=y
# CONFIG_KVM_DEBUG_FS is not set
# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
CONFIG_PARAVIRT_CLOCK=y
CONFIG_NO_BOOTMEM=y
CONFIG_MEMTEST=y
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_INTERNODE_CACHE_SHIFT=6
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_PROCESSOR_SELECT=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
CONFIG_CALGARY_IOMMU=y
CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=256
CONFIG_SCHED_SMT=y
CONFIG_SCHED_MC=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
CONFIG_X86_THERMAL_VECTOR=y
# CONFIG_I8K is not set
CONFIG_MICROCODE=y
CONFIG_MICROCODE_INTEL=y
CONFIG_MICROCODE_AMD=y
CONFIG_MICROCODE_OLD_INTERFACE=y
CONFIG_MICROCODE_INTEL_EARLY=y
CONFIG_MICROCODE_AMD_EARLY=y
CONFIG_MICROCODE_EARLY=y
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
CONFIG_AMD_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set
CONFIG_NODES_SHIFT=6
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_MEMORY_PROBE=y
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_HAVE_MEMBLOCK=y
CONFIG_HAVE_MEMBLOCK_NODE_MAP=y
CONFIG_ARCH_DISCARD_MEMBLOCK=y
CONFIG_MEMORY_ISOLATION=y
# CONFIG_MOVABLE_NODE is not set
CONFIG_HAVE_BOOTMEM_INFO_NODE=y
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTPLUG_SPARSE=y
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y
CONFIG_COMPACTION=y
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_NEED_BOUNCE_POOL=y
CONFIG_VIRT_TO_BUS=y
CONFIG_MMU_NOTIFIER=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
CONFIG_MEMORY_FAILURE=y
# CONFIG_HWPOISON_INJECT is not set
CONFIG_TRANSPARENT_HUGEPAGE=y
# CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not set
CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_CLEANCACHE=y
CONFIG_FRONTSWAP=y
# CONFIG_CMA is not set
# CONFIG_ZBUD is not set
# CONFIG_ZSWAP is not set
# CONFIG_MEM_SOFT_DIRTY is not set
CONFIG_ZSMALLOC=y
# CONFIG_PGTABLE_MAPPING is not set
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
CONFIG_X86_RESERVE_LOW=64
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_ARCH_RANDOM=y
CONFIG_X86_SMAP=y
CONFIG_EFI=y
CONFIG_EFI_STUB=y
CONFIG_SECCOMP=y
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_SCHED_HRTICK=y
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y
CONFIG_KEXEC_JUMP=y
CONFIG_PHYSICAL_START=0x1000000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
# CONFIG_BOOTPARAM_HOTPLUG_CPU0 is not set
# CONFIG_DEBUG_HOTPLUG_CPU0 is not set
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
CONFIG_USE_PERCPU_NUMA_NODE_ID=y
#
# Power management and ACPI options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_HIBERNATE_CALLBACKS=y
CONFIG_HIBERNATION=y
CONFIG_PM_STD_PARTITION=""
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
CONFIG_PM_RUNTIME=y
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
CONFIG_ACPI=y
CONFIG_ACPI_SLEEP=y
# CONFIG_ACPI_PROCFS is not set
CONFIG_ACPI_EC_DEBUGFS=m
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_NUMA=y
CONFIG_ACPI_CUSTOM_DSDT_FILE=""
# CONFIG_ACPI_CUSTOM_DSDT is not set
# CONFIG_ACPI_INITRD_TABLE_OVERRIDE is not set
# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_HOTPLUG_MEMORY is not set
# CONFIG_ACPI_SBS is not set
CONFIG_ACPI_HED=y
# CONFIG_ACPI_CUSTOM_METHOD is not set
CONFIG_ACPI_BGRT=y
CONFIG_ACPI_APEI=y
CONFIG_ACPI_APEI_GHES=y
CONFIG_ACPI_APEI_PCIEAER=y
CONFIG_ACPI_APEI_MEMORY_FAILURE=y
# CONFIG_ACPI_APEI_EINJ is not set
# CONFIG_ACPI_APEI_ERST_DEBUG is not set
# CONFIG_ACPI_EXTLOG is not set
CONFIG_SFI=y
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_GOV_COMMON=y
CONFIG_CPU_FREQ_STAT=y
CONFIG_CPU_FREQ_STAT_DETAILS=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
#
# x86 CPU frequency scaling drivers
#
CONFIG_X86_INTEL_PSTATE=y
CONFIG_X86_PCC_CPUFREQ=y
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_X86_ACPI_CPUFREQ_CPB=y
CONFIG_X86_POWERNOW_K8=y
# CONFIG_X86_AMD_FREQ_SENSITIVITY is not set
CONFIG_X86_SPEEDSTEP_CENTRINO=y
# CONFIG_X86_P4_CLOCKMOD is not set
#
# shared options
#
# CONFIG_X86_SPEEDSTEP_LIB is not set
#
# CPU Idle
#
CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_MULTIPLE_DRIVERS is not set
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED is not set
CONFIG_INTEL_IDLE=y
#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set
#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_XEN=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not set
CONFIG_PCIE_PME=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
CONFIG_PCI_REALLOC_ENABLE_AUTO=y
# CONFIG_PCI_STUB is not set
# CONFIG_XEN_PCIDEV_FRONTEND is not set
CONFIG_HT_IRQ=y
CONFIG_PCI_ATS=y
CONFIG_PCI_IOV=y
CONFIG_PCI_PRI=y
CONFIG_PCI_PASID=y
CONFIG_PCI_IOAPIC=y
CONFIG_PCI_LABEL=y
#
# PCI host controller drivers
#
CONFIG_ISA_DMA_API=y
CONFIG_AMD_NB=y
# CONFIG_PCCARD is not set
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_ACPI is not set
CONFIG_HOTPLUG_PCI_CPCI=y
# CONFIG_HOTPLUG_PCI_CPCI_ZT5550 is not set
# CONFIG_HOTPLUG_PCI_CPCI_GENERIC is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set
CONFIG_RAPIDIO=y
CONFIG_RAPIDIO_TSI721=y
CONFIG_RAPIDIO_DISC_TIMEOUT=30
# CONFIG_RAPIDIO_ENABLE_RX_TX_PORTS is not set
CONFIG_RAPIDIO_DMA_ENGINE=y
# CONFIG_RAPIDIO_DEBUG is not set
# CONFIG_RAPIDIO_ENUM_BASIC is not set
#
# RapidIO Switch drivers
#
CONFIG_RAPIDIO_TSI57X=y
CONFIG_RAPIDIO_CPS_XX=y
CONFIG_RAPIDIO_TSI568=y
CONFIG_RAPIDIO_CPS_GEN2=y
# CONFIG_X86_SYSFB is not set
#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_BINFMT_SCRIPT=y
# CONFIG_HAVE_AOUT is not set
# CONFIG_BINFMT_MISC is not set
CONFIG_COREDUMP=y
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_AOUT is not set
CONFIG_X86_X32=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_KEYS_COMPAT=y
CONFIG_X86_DEV_DMA_OPS=y
CONFIG_NET=y
CONFIG_COMPAT_NETLINK_MESSAGES=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_DIAG is not set
CONFIG_UNIX=y
# CONFIG_UNIX_DIAG is not set
# CONFIG_XFRM_USER is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_FIB_TRIE_STATS=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
# CONFIG_IP_PNP_RARP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE_DEMUX is not set
# CONFIG_NET_IP_TUNNEL is not set
CONFIG_IP_MROUTE=y
# CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_LRO=y
# CONFIG_INET_DIAG is not set
CONFIG_TCP_CONG_ADVANCED=y
# CONFIG_TCP_CONG_BIC is not set
CONFIG_TCP_CONG_CUBIC=y
# CONFIG_TCP_CONG_WESTWOOD is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_HSTCP is not set
# CONFIG_TCP_CONG_HYBLA is not set
# CONFIG_TCP_CONG_VEGAS is not set
# CONFIG_TCP_CONG_SCALABLE is not set
# CONFIG_TCP_CONG_LP is not set
# CONFIG_TCP_CONG_VENO is not set
# CONFIG_TCP_CONG_YEAH is not set
# CONFIG_TCP_CONG_ILLINOIS is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET6_XFRM_MODE_TUNNEL is not set
# CONFIG_INET6_XFRM_MODE_BEET is not set
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
# CONFIG_IPV6_SIT is not set
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_GRE is not set
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
CONFIG_IPV6_PIMSM_V2=y
CONFIG_NETLABEL=y
CONFIG_NETWORK_SECMARK=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y
#
# Core Netfilter Configuration
#
# CONFIG_NETFILTER_NETLINK_ACCT is not set
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
# CONFIG_NETFILTER_NETLINK_LOG is not set
# CONFIG_NF_CONNTRACK is not set
# CONFIG_NF_TABLES is not set
# CONFIG_NETFILTER_XTABLES is not set
# CONFIG_IP_SET is not set
# CONFIG_IP_VS is not set
#
# IP: Netfilter Configuration
#
# CONFIG_NF_DEFRAG_IPV4 is not set
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES is not set
#
# IPv6: Netfilter Configuration
#
# CONFIG_NF_DEFRAG_IPV6 is not set
# CONFIG_IP6_NF_IPTABLES is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not set
CONFIG_HAVE_NET_DSA=y
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
CONFIG_6LOWPAN_IPHC=m
CONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
# CONFIG_NET_SCH_CBQ is not set
CONFIG_NET_SCH_HTB=m
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_MULTIQ is not set
# CONFIG_NET_SCH_RED is not set
# CONFIG_NET_SCH_SFB is not set
# CONFIG_NET_SCH_SFQ is not set
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_DRR is not set
# CONFIG_NET_SCH_MQPRIO is not set
# CONFIG_NET_SCH_CHOKE is not set
# CONFIG_NET_SCH_QFQ is not set
CONFIG_NET_SCH_CODEL=m
CONFIG_NET_SCH_FQ_CODEL=m
# CONFIG_NET_SCH_FQ is not set
# CONFIG_NET_SCH_HHF is not set
# CONFIG_NET_SCH_PIE is not set
# CONFIG_NET_SCH_INGRESS is not set
# CONFIG_NET_SCH_PLUG is not set
#
# Classification
#
CONFIG_NET_CLS=y
# CONFIG_NET_CLS_BASIC is not set
# CONFIG_NET_CLS_TCINDEX is not set
# CONFIG_NET_CLS_ROUTE4 is not set
# CONFIG_NET_CLS_FW is not set
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not set
# CONFIG_NET_CLS_CGROUP is not set
# CONFIG_NET_CLS_BPF is not set
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
# CONFIG_NET_EMATCH_CMP is not set
# CONFIG_NET_EMATCH_NBYTE is not set
# CONFIG_NET_EMATCH_U32 is not set
# CONFIG_NET_EMATCH_META is not set
# CONFIG_NET_EMATCH_TEXT is not set
CONFIG_NET_CLS_ACT=y
# CONFIG_NET_ACT_POLICE is not set
# CONFIG_NET_ACT_GACT is not set
# CONFIG_NET_ACT_MIRRED is not set
# CONFIG_NET_ACT_NAT is not set
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
# CONFIG_NET_ACT_SKBEDIT is not set
# CONFIG_NET_ACT_CSUM is not set
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
CONFIG_DNS_RESOLVER=y
# CONFIG_BATMAN_ADV is not set
# CONFIG_OPENVSWITCH is not set
# CONFIG_VSOCKETS is not set
# CONFIG_NETLINK_MMAP is not set
# CONFIG_NETLINK_DIAG is not set
# CONFIG_NET_MPLS_GSO is not set
# CONFIG_HSR is not set
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
# CONFIG_CGROUP_NET_PRIO is not set
# CONFIG_CGROUP_NET_CLASSID is not set
CONFIG_NET_RX_BUSY_POLL=y
CONFIG_BQL=y
CONFIG_BPF_JIT=y
CONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
# CONFIG_NET_DROP_MONITOR is not set
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#
# CONFIG_AX25 is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
CONFIG_BT=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
# CONFIG_BT_HIDP is not set
#
# Bluetooth device drivers
#
CONFIG_BT_HCIBTUSB=m
# CONFIG_BT_HCIBTSDIO is not set
# CONFIG_BT_HCIUART is not set
# CONFIG_BT_HCIBCM203X is not set
# CONFIG_BT_HCIBPA10X is not set
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_BT_MRVL is not set
# CONFIG_BT_ATH3K is not set
# CONFIG_AF_RXRPC is not set
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_CFG80211=m
CONFIG_NL80211_TESTMODE=y
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_REG_DEBUG is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not set
CONFIG_CFG80211_DEFAULT_PS=y
CONFIG_CFG80211_DEBUGFS=y
# CONFIG_CFG80211_INTERNAL_REGDB is not set
CONFIG_CFG80211_WEXT=y
# CONFIG_LIB80211 is not set
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_PID=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_MINSTREL_HT=y
# CONFIG_MAC80211_RC_DEFAULT_PID is not set
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
CONFIG_MAC80211_MESH=y
CONFIG_MAC80211_LEDS=y
CONFIG_MAC80211_DEBUGFS=y
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
# CONFIG_WIMAX is not set
CONFIG_RFKILL=y
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_REGULATOR is not set
# CONFIG_RFKILL_GPIO is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set
CONFIG_HAVE_BPF_JIT=y
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
# CONFIG_STANDALONE is not set
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
CONFIG_FW_LOADER_USER_HELPER=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
CONFIG_SYS_HYPERVISOR=y
# CONFIG_GENERIC_CPU_DEVICES is not set
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=y
CONFIG_REGMAP_SPI=y
CONFIG_REGMAP_IRQ=y
CONFIG_DMA_SHARED_BUFFER=y
#
# Bus devices
#
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
CONFIG_PARPORT=m
CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
CONFIG_PARPORT_PC=m
# CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PNP=y
# CONFIG_PNP_DEBUG_MESSAGES is not set
#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_NULL_BLK is not set
# CONFIG_BLK_DEV_FD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
# CONFIG_ZRAM is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_NVME is not set
# CONFIG_BLK_DEV_SKD is not set
# CONFIG_BLK_DEV_SX8 is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=65536
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_XEN_BLKDEV_FRONTEND=y
# CONFIG_XEN_BLKDEV_BACKEND is not set
CONFIG_VIRTIO_BLK=y
# CONFIG_BLK_DEV_HD is not set
# CONFIG_BLK_DEV_RBD is not set
# CONFIG_BLK_DEV_RSXX is not set
#
# Misc devices
#
# CONFIG_SENSORS_LIS3LV02D is not set
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_IBM_ASM is not set
# CONFIG_PHANTOM is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ATMEL_SSC is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not set
# CONFIG_APDS9802ALS is not set
# CONFIG_ISL29003 is not set
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1780 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_SENSORS_APDS990X is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_TI_DAC7512 is not set
# CONFIG_VMWARE_BALLOON is not set
# CONFIG_BMP085_I2C is not set
# CONFIG_BMP085_SPI is not set
# CONFIG_PCH_PHUB is not set
# CONFIG_USB_SWITCH_FSA9480 is not set
# CONFIG_LATTICE_ECP3_CONFIG is not set
# CONFIG_SRAM is not set
# CONFIG_C2PORT is not set
#
# EEPROM support
#
# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_LEGACY is not set
# CONFIG_EEPROM_MAX6875 is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_CB710_CORE is not set
#
# Texas Instruments shared transport line discipline
#
# CONFIG_TI_ST is not set
# CONFIG_SENSORS_LIS3_I2C is not set
#
# Altera FPGA firmware download module
#
# CONFIG_ALTERA_STAPL is not set
CONFIG_INTEL_MEI=y
CONFIG_INTEL_MEI_ME=y
# CONFIG_VMWARE_VMCI is not set
#
# Intel MIC Host Driver
#
# CONFIG_INTEL_MIC_HOST is not set
#
# Intel MIC Card Driver
#
# CONFIG_INTEL_MIC_CARD is not set
# CONFIG_GENWQE is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_CXGB4_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_SCSI_BNX2X_FCOE is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_MVUMI is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ESAS2R is not set
CONFIG_MEGARAID_NEWGEN=y
# CONFIG_MEGARAID_MM is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_MPT3SAS is not set
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_VMWARE_PVSCSI is not set
# CONFIG_LIBFC is not set
# CONFIG_LIBFCOE is not set
# CONFIG_FCOE is not set
# CONFIG_FCOE_FNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_ISCI is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_SCSI_BFA_FC is not set
# CONFIG_SCSI_VIRTIO is not set
# CONFIG_SCSI_CHELSIO_FCOE is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
# CONFIG_SATA_ZPODD is not set
CONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=y
# CONFIG_SATA_AHCI_PLATFORM is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not set
CONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#
CONFIG_ATA_PIIX=y
# CONFIG_SATA_HIGHBANK is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_RCAR is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARASAN_CF is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SCH is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
CONFIG_PATA_SIS=y
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PLATFORM is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#
CONFIG_PATA_ACPI=y
CONFIG_ATA_GENERIC=y
# CONFIG_PATA_LEGACY is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
# CONFIG_BCACHE is not set
CONFIG_BLK_DEV_DM_BUILTIN=y
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
# CONFIG_DM_CRYPT is not set
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_THIN_PROVISIONING is not set
# CONFIG_DM_CACHE is not set
# CONFIG_DM_MIRROR is not set
# CONFIG_DM_RAID is not set
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
CONFIG_DM_UEVENT=y
# CONFIG_DM_FLAKEY is not set
# CONFIG_DM_VERITY is not set
# CONFIG_DM_SWITCH is not set
# CONFIG_TARGET_CORE is not set
CONFIG_FUSION=y
# CONFIG_FUSION_SPI is not set
# CONFIG_FUSION_FC is not set
# CONFIG_FUSION_SAS is not set
CONFIG_FUSION_MAX_SGE=128
CONFIG_FUSION_LOGGING=y
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_FIREWIRE_NOSY is not set
# CONFIG_I2O is not set
CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=m
CONFIG_NETDEVICES=y
CONFIG_MII=m
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
# CONFIG_DUMMY is not set
# CONFIG_EQUALIZER is not set
CONFIG_NET_FC=y
# CONFIG_IFB is not set
# CONFIG_NET_TEAM is not set
# CONFIG_MACVLAN is not set
# CONFIG_VXLAN is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_RIONET is not set
CONFIG_TUN=y
# CONFIG_VETH is not set
CONFIG_VIRTIO_NET=y
# CONFIG_NLMON is not set
# CONFIG_ARCNET is not set
#
# CAIF transport drivers
#
# CONFIG_VHOST_NET is not set
#
# Distributed Switch Architecture drivers
#
# CONFIG_NET_DSA_MV88E6XXX is not set
# CONFIG_NET_DSA_MV88E6060 is not set
# CONFIG_NET_DSA_MV88E6XXX_NEED_PPU is not set
# CONFIG_NET_DSA_MV88E6131 is not set
# CONFIG_NET_DSA_MV88E6123_61_65 is not set
CONFIG_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
# CONFIG_VORTEX is not set
# CONFIG_TYPHOON is not set
CONFIG_NET_VENDOR_ADAPTEC=y
# CONFIG_ADAPTEC_STARFIRE is not set
CONFIG_NET_VENDOR_ALTEON=y
# CONFIG_ACENIC is not set
CONFIG_NET_VENDOR_AMD=y
# CONFIG_AMD8111_ETH is not set
# CONFIG_PCNET32 is not set
CONFIG_NET_VENDOR_ARC=y
CONFIG_NET_VENDOR_ATHEROS=y
# CONFIG_ATL2 is not set
# CONFIG_ATL1 is not set
# CONFIG_ATL1E is not set
# CONFIG_ATL1C is not set
# CONFIG_ALX is not set
CONFIG_NET_CADENCE=y
# CONFIG_ARM_AT91_ETHER is not set
# CONFIG_MACB is not set
CONFIG_NET_VENDOR_BROADCOM=y
# CONFIG_B44 is not set
# CONFIG_BNX2 is not set
# CONFIG_CNIC is not set
# CONFIG_TIGON3 is not set
# CONFIG_BNX2X is not set
CONFIG_NET_VENDOR_BROCADE=y
# CONFIG_BNA is not set
# CONFIG_NET_CALXEDA_XGMAC is not set
CONFIG_NET_VENDOR_CHELSIO=y
# CONFIG_CHELSIO_T1 is not set
# CONFIG_CHELSIO_T3 is not set
# CONFIG_CHELSIO_T4 is not set
# CONFIG_CHELSIO_T4VF is not set
CONFIG_NET_VENDOR_CISCO=y
# CONFIG_ENIC is not set
# CONFIG_DNET is not set
CONFIG_NET_VENDOR_DEC=y
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
# CONFIG_TULIP is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
CONFIG_NET_VENDOR_DLINK=y
# CONFIG_DL2K is not set
# CONFIG_SUNDANCE is not set
CONFIG_NET_VENDOR_EMULEX=y
# CONFIG_BE2NET is not set
CONFIG_NET_VENDOR_EXAR=y
# CONFIG_S2IO is not set
# CONFIG_VXGE is not set
CONFIG_NET_VENDOR_HP=y
# CONFIG_HP100 is not set
CONFIG_NET_VENDOR_INTEL=y
# CONFIG_E100 is not set
# CONFIG_E1000 is not set
# CONFIG_E1000E is not set
# CONFIG_IGB is not set
# CONFIG_IGBVF is not set
# CONFIG_IXGB is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGBEVF is not set
# CONFIG_I40E is not set
# CONFIG_I40EVF is not set
CONFIG_NET_VENDOR_I825XX=y
# CONFIG_IP1000 is not set
# CONFIG_JME is not set
CONFIG_NET_VENDOR_MARVELL=y
# CONFIG_MVMDIO is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
CONFIG_NET_VENDOR_MELLANOX=y
# CONFIG_MLX4_EN is not set
# CONFIG_MLX4_CORE is not set
# CONFIG_MLX5_CORE is not set
CONFIG_NET_VENDOR_MICREL=y
# CONFIG_KS8842 is not set
# CONFIG_KS8851 is not set
# CONFIG_KS8851_MLL is not set
# CONFIG_KSZ884X_PCI is not set
CONFIG_NET_VENDOR_MICROCHIP=y
# CONFIG_ENC28J60 is not set
CONFIG_NET_VENDOR_MYRI=y
# CONFIG_MYRI10GE is not set
# CONFIG_FEALNX is not set
CONFIG_NET_VENDOR_NATSEMI=y
# CONFIG_NATSEMI is not set
# CONFIG_NS83820 is not set
CONFIG_NET_VENDOR_8390=y
# CONFIG_NE2K_PCI is not set
CONFIG_NET_VENDOR_NVIDIA=y
# CONFIG_FORCEDETH is not set
CONFIG_NET_VENDOR_OKI=y
# CONFIG_PCH_GBE is not set
# CONFIG_ETHOC is not set
CONFIG_NET_PACKET_ENGINE=y
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_NET_VENDOR_QLOGIC=y
# CONFIG_QLA3XXX is not set
# CONFIG_QLCNIC is not set
# CONFIG_QLGE is not set
# CONFIG_NETXEN_NIC is not set
CONFIG_NET_VENDOR_REALTEK=y
# CONFIG_ATP is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
CONFIG_R8169=m
# CONFIG_SH_ETH is not set
CONFIG_NET_VENDOR_RDC=y
# CONFIG_R6040 is not set
CONFIG_NET_VENDOR_SEEQ=y
CONFIG_NET_VENDOR_SILAN=y
# CONFIG_SC92031 is not set
CONFIG_NET_VENDOR_SIS=y
# CONFIG_SIS900 is not set
# CONFIG_SIS190 is not set
# CONFIG_SFC is not set
CONFIG_NET_VENDOR_SMSC=y
# CONFIG_EPIC100 is not set
# CONFIG_SMSC911X is not set
# CONFIG_SMSC9420 is not set
CONFIG_NET_VENDOR_STMICRO=y
# CONFIG_STMMAC_ETH is not set
CONFIG_NET_VENDOR_SUN=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NIU is not set
CONFIG_NET_VENDOR_TEHUTI=y
# CONFIG_TEHUTI is not set
CONFIG_NET_VENDOR_TI=y
# CONFIG_TLAN is not set
CONFIG_NET_VENDOR_VIA=y
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_VELOCITY is not set
CONFIG_NET_VENDOR_WIZNET=y
# CONFIG_WIZNET_W5100 is not set
# CONFIG_WIZNET_W5300 is not set
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
# CONFIG_SKFP is not set
# CONFIG_HIPPI is not set
# CONFIG_NET_SB1000 is not set
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
CONFIG_AT803X_PHY=y
CONFIG_AMD_PHY=y
CONFIG_MARVELL_PHY=y
CONFIG_DAVICOM_PHY=y
CONFIG_QSEMI_PHY=y
CONFIG_LXT_PHY=y
CONFIG_CICADA_PHY=y
CONFIG_VITESSE_PHY=y
CONFIG_SMSC_PHY=y
CONFIG_BROADCOM_PHY=y
CONFIG_BCM87XX_PHY=y
CONFIG_ICPLUS_PHY=y
CONFIG_REALTEK_PHY=y
CONFIG_NATIONAL_PHY=y
CONFIG_STE10XP=y
CONFIG_LSI_ET1011C_PHY=y
CONFIG_MICREL_PHY=y
CONFIG_FIXED_PHY=y
CONFIG_MDIO_BITBANG=y
CONFIG_MDIO_GPIO=y
# CONFIG_MICREL_KS8995MA is not set
# CONFIG_PLIP is not set
CONFIG_PPP=y
# CONFIG_PPP_BSDCOMP is not set
# CONFIG_PPP_DEFLATE is not set
CONFIG_PPP_FILTER=y
# CONFIG_PPP_MPPE is not set
CONFIG_PPP_MULTILINK=y
# CONFIG_PPPOE is not set
# CONFIG_PPP_ASYNC is not set
# CONFIG_PPP_SYNC_TTY is not set
# CONFIG_SLIP is not set
CONFIG_SLHC=y
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_RTL8152 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_HSO is not set
# CONFIG_USB_IPHETH is not set
CONFIG_WLAN=y
# CONFIG_LIBERTAS_THINFIRM is not set
# CONFIG_AIRO is not set
# CONFIG_ATMEL is not set
# CONFIG_AT76C50X_USB is not set
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_RTL8180 is not set
# CONFIG_RTL8187 is not set
# CONFIG_ADM8211 is not set
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_MWL8K is not set
# CONFIG_ATH_CARDS is not set
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_BRCMSMAC is not set
# CONFIG_BRCMFMAC is not set
# CONFIG_HOSTAP is not set
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
CONFIG_IWLWIFI=m
CONFIG_IWLDVM=m
# CONFIG_IWLMVM is not set
CONFIG_IWLWIFI_OPMODE_MODULAR=y
#
# Debugging Options
#
# CONFIG_IWLWIFI_DEBUG is not set
CONFIG_IWLWIFI_DEBUGFS=y
CONFIG_IWLWIFI_DEVICE_TRACING=y
# CONFIG_IWL4965 is not set
# CONFIG_IWL3945 is not set
# CONFIG_LIBERTAS is not set
# CONFIG_HERMES is not set
# CONFIG_P54_COMMON is not set
# CONFIG_RT2X00 is not set
CONFIG_RTL_CARDS=m
# CONFIG_RTL8192CE is not set
# CONFIG_RTL8192SE is not set
# CONFIG_RTL8192DE is not set
# CONFIG_RTL8723AE is not set
# CONFIG_RTL8188EE is not set
# CONFIG_RTL8192CU is not set
CONFIG_WL_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not set
# CONFIG_ZD1211RW is not set
# CONFIG_MWIFIEX is not set
# CONFIG_CW1200 is not set
#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
CONFIG_WAN=y
# CONFIG_HDLC is not set
# CONFIG_DLCI is not set
# CONFIG_SBNI is not set
CONFIG_XEN_NETDEV_FRONTEND=y
# CONFIG_XEN_NETDEV_BACKEND is not set
# CONFIG_VMXNET3 is not set
CONFIG_ISDN=y
# CONFIG_ISDN_I4L is not set
# CONFIG_ISDN_CAPI is not set
# CONFIG_ISDN_DRV_GIGASET is not set
# CONFIG_HYSDN is not set
# CONFIG_MISDN is not set
#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set
# CONFIG_INPUT_SPARSEKMAP is not set
# CONFIG_INPUT_MATRIXKMAP is not set
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5520 is not set
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_STMPE is not set
# CONFIG_KEYBOARD_TC3589X is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_CYPRESS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_MOUSE_PS2_SENTELIC=y
CONFIG_MOUSE_PS2_TOUCHKIT=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_CYAPA is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_USB is not set
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_ZHENHUA is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_JOYSTICK_AS5011 is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
# CONFIG_JOYSTICK_XPAD is not set
# CONFIG_JOYSTICK_WALKERA0701 is not set
CONFIG_INPUT_TABLET=y
# CONFIG_TABLET_USB_ACECAD is not set
# CONFIG_TABLET_USB_AIPTEK is not set
# CONFIG_TABLET_USB_GTCO is not set
# CONFIG_TABLET_USB_HANWANG is not set
# CONFIG_TABLET_USB_KBTAB is not set
# CONFIG_TABLET_USB_WACOM is not set
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_88PM860X is not set
# CONFIG_TOUCHSCREEN_ADS7846 is not set
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_ATMEL_MXT is not set
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP4_CORE is not set
# CONFIG_TOUCHSCREEN_DA9034 is not set
# CONFIG_TOUCHSCREEN_DA9052 is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_WACOM_I2C is not set
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MCS5000 is not set
# CONFIG_TOUCHSCREEN_MMS114 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_WM831X is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2005 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_PCAP is not set
# CONFIG_TOUCHSCREEN_ST1232 is not set
# CONFIG_TOUCHSCREEN_STMPE is not set
# CONFIG_TOUCHSCREEN_SUR40 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_88PM860X_ONKEY is not set
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_BMA150 is not set
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_MAX8925_ONKEY is not set
# CONFIG_INPUT_MMA8450 is not set
# CONFIG_INPUT_MPU3050 is not set
# CONFIG_INPUT_APANEL is not set
# CONFIG_INPUT_GP2A is not set
# CONFIG_INPUT_GPIO_TILT_POLLED is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_KXTJ9 is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
# CONFIG_INPUT_TWL6040_VIBRA is not set
CONFIG_INPUT_UINPUT=y
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_GPIO_ROTARY_ENCODER is not set
# CONFIG_INPUT_DA9052_ONKEY is not set
# CONFIG_INPUT_DA9055_ONKEY is not set
# CONFIG_INPUT_WM831X_ON is not set
# CONFIG_INPUT_PCAP is not set
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_IMS_PCU is not set
# CONFIG_INPUT_CMA3000 is not set
# CONFIG_INPUT_XEN_KBDDEV_FRONTEND is not set
# CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_GAMEPORT is not set
#
# Character devices
#
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=0
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_NOZOMI is not set
# CONFIG_ISI is not set
# CONFIG_N_HDLC is not set
# CONFIG_N_GSM is not set
# CONFIG_TRACE_SINK is not set
# CONFIG_DEVKMEM is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_DEPRECATED_OPTIONS=y
CONFIG_SERIAL_8250_PNP=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_DMA=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_NR_UARTS=48
CONFIG_SERIAL_8250_RUNTIME_UARTS=32
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
CONFIG_SERIAL_8250_RSA=y
# CONFIG_SERIAL_8250_DW is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_KGDB_NMI=y
# CONFIG_SERIAL_MAX3100 is not set
CONFIG_SERIAL_MAX310X=y
# CONFIG_SERIAL_MFD_HSU is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_CONSOLE_POLL=y
# CONFIG_SERIAL_JSM is not set
CONFIG_SERIAL_SCCNXP=y
CONFIG_SERIAL_SCCNXP_CONSOLE=y
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not set
# CONFIG_SERIAL_PCH_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
CONFIG_TTY_PRINTK=y
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IRQ=y
CONFIG_HVC_XEN=y
CONFIG_HVC_XEN_FRONTEND=y
# CONFIG_VIRTIO_CONSOLE is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_HW_RANDOM_INTEL is not set
# CONFIG_HW_RANDOM_AMD is not set
# CONFIG_HW_RANDOM_VIA is not set
# CONFIG_HW_RANDOM_VIRTIO is not set
# CONFIG_HW_RANDOM_TPM is not set
# CONFIG_NVRAM is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
CONFIG_HPET_MMAP_DEFAULT=y
# CONFIG_HANGCHECK_TIMER is not set
CONFIG_TCG_TPM=y
# CONFIG_TCG_TIS is not set
# CONFIG_TCG_TIS_I2C_ATMEL is not set
# CONFIG_TCG_TIS_I2C_INFINEON is not set
# CONFIG_TCG_TIS_I2C_NUVOTON is not set
# CONFIG_TCG_NSC is not set
# CONFIG_TCG_ATMEL is not set
# CONFIG_TCG_INFINEON is not set
# CONFIG_TCG_ST33_I2C is not set
# CONFIG_TCG_XEN is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
# CONFIG_I2C_CHARDEV is not set
CONFIG_I2C_MUX=m
#
# Multiplexer I2C Chip support
#
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=m
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_ISMT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# ACPI drivers
#
# CONFIG_I2C_SCMI is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_CBUS_GPIO is not set
# CONFIG_I2C_DESIGNWARE_PLATFORM is not set
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_EG20T is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_PXA_PCI is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_BUTTERFLY is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_LM70_LLP is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_PXA2XX_PCI is not set
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_TOPCLIFF_PCH is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_DESIGNWARE is not set
#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_HSI is not set
#
# PPS support
#
# CONFIG_PPS is not set
#
# PPS generators support
#
#
# PTP clock support
#
# CONFIG_PTP_1588_CLOCK is not set
#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks.
#
# CONFIG_PTP_1588_CLOCK_PCH is not set
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
CONFIG_GPIOLIB=y
CONFIG_GPIO_DEVRES=y
CONFIG_GPIO_ACPI=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set
# CONFIG_GPIO_DA9052 is not set
# CONFIG_GPIO_DA9055 is not set
#
# Memory mapped GPIO drivers:
#
# CONFIG_GPIO_GENERIC_PLATFORM is not set
# CONFIG_GPIO_IT8761E is not set
# CONFIG_GPIO_F7188X is not set
# CONFIG_GPIO_SCH311X is not set
# CONFIG_GPIO_TS5500 is not set
# CONFIG_GPIO_SCH is not set
# CONFIG_GPIO_ICH is not set
# CONFIG_GPIO_VX855 is not set
# CONFIG_GPIO_LYNXPOINT is not set
#
# I2C GPIO expanders:
#
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCF857X is not set
CONFIG_GPIO_RC5T583=y
CONFIG_GPIO_SX150X=y
CONFIG_GPIO_STMPE=y
CONFIG_GPIO_TC3589X=y
# CONFIG_GPIO_TPS65912 is not set
# CONFIG_GPIO_TWL6040 is not set
# CONFIG_GPIO_WM831X is not set
# CONFIG_GPIO_WM8350 is not set
# CONFIG_GPIO_WM8994 is not set
# CONFIG_GPIO_ADP5520 is not set
# CONFIG_GPIO_ADP5588 is not set
#
# PCI GPIO expanders:
#
# CONFIG_GPIO_BT8XX is not set
# CONFIG_GPIO_AMD8111 is not set
# CONFIG_GPIO_INTEL_MID is not set
# CONFIG_GPIO_PCH is not set
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_RDC321X is not set
#
# SPI GPIO expanders:
#
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
#
# AC97 GPIO expanders:
#
#
# LPC GPIO expanders:
#
#
# MODULbus GPIO expanders:
#
# CONFIG_GPIO_PALMAS is not set
CONFIG_GPIO_TPS6586X=y
CONFIG_GPIO_TPS65910=y
#
# USB GPIO expanders:
#
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_MAX8925_POWER is not set
# CONFIG_WM831X_BACKUP is not set
# CONFIG_WM831X_POWER is not set
# CONFIG_WM8350_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_88PM860X is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_DA9030 is not set
# CONFIG_BATTERY_DA9052 is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
CONFIG_CHARGER_MANAGER=y
# CONFIG_CHARGER_BQ2415X is not set
# CONFIG_CHARGER_BQ24190 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_SMB347 is not set
# CONFIG_CHARGER_TPS65090 is not set
# CONFIG_POWER_RESET is not set
CONFIG_POWER_AVS=y
CONFIG_HWMON=y
# CONFIG_HWMON_VID is not set
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7314 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADCXX is not set
# CONFIG_SENSORS_ADM1021 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7310 is not set
# CONFIG_SENSORS_ADT7410 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_K10TEMP is not set
# CONFIG_SENSORS_FAM15H_POWER is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_DS620 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_DA9052_ADC is not set
# CONFIG_SENSORS_DA9055 is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
# CONFIG_SENSORS_HTU21 is not set
CONFIG_SENSORS_CORETEMP=m
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_JC42 is not set
# CONFIG_SENSORS_LINEAGE is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM70 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LTC4151 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LTC4261 is not set
# CONFIG_SENSORS_LM95234 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_LM95245 is not set
# CONFIG_SENSORS_MAX1111 is not set
# CONFIG_SENSORS_MAX16065 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6642 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MCP3021 is not set
# CONFIG_SENSORS_NCT6775 is not set
# CONFIG_SENSORS_NTC_THERMISTOR is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_SHT15 is not set
# CONFIG_SENSORS_SHT21 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SCH56XX_COMMON is not set
# CONFIG_SENSORS_SCH5627 is not set
# CONFIG_SENSORS_SCH5636 is not set
# CONFIG_SENSORS_ADS1015 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_ADS7871 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_INA209 is not set
# CONFIG_SENSORS_INA2XX is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_VIA_CPUTEMP is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_WM831X is not set
# CONFIG_SENSORS_WM8350 is not set
# CONFIG_SENSORS_APPLESMC is not set
#
# ACPI drivers
#
# CONFIG_SENSORS_ACPI_POWER is not set
# CONFIG_SENSORS_ATK0110 is not set
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set
# CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set
# CONFIG_THERMAL_GOV_FAIR_SHARE is not set
CONFIG_THERMAL_GOV_STEP_WISE=y
CONFIG_THERMAL_GOV_USER_SPACE=y
# CONFIG_THERMAL_EMULATION is not set
# CONFIG_INTEL_POWERCLAMP is not set
CONFIG_X86_PKG_TEMP_THERMAL=m
# CONFIG_ACPI_INT3403_THERMAL is not set
#
# Texas Instruments thermal drivers
#
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
# CONFIG_WATCHDOG_NOWAYOUT is not set
#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_DA9052_WATCHDOG is not set
# CONFIG_DA9055_WATCHDOG is not set
# CONFIG_WM831X_WATCHDOG is not set
# CONFIG_WM8350_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_F71808E_WDT is not set
# CONFIG_SP5100_TCO is not set
# CONFIG_SC520_WDT is not set
# CONFIG_SBC_FITPC2_WATCHDOG is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_IBMASR is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_IE6XX_WDT is not set
# CONFIG_ITCO_WDT is not set
# CONFIG_IT8712F_WDT is not set
# CONFIG_IT87_WDT is not set
# CONFIG_HP_WATCHDOG is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not set
# CONFIG_NV_TCO is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SBC8360_WDT is not set
# CONFIG_CPU5_WDT is not set
# CONFIG_SMSC_SCH311X_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_VIA_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83697HF_WDT is not set
# CONFIG_W83697UG_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_MACHZ_WDT is not set
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
# CONFIG_MEN_A21_WDT is not set
# CONFIG_XEN_WDT is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_BCMA_POSSIBLE=y
#
# Broadcom specific AMBA
#
# CONFIG_BCMA is not set
#
# Multifunction device drivers
#
CONFIG_MFD_CORE=y
# CONFIG_MFD_CS5535 is not set
# CONFIG_MFD_AS3711 is not set
CONFIG_PMIC_ADP5520=y
CONFIG_MFD_AAT2870_CORE=y
# CONFIG_MFD_CROS_EC is not set
CONFIG_PMIC_DA903X=y
CONFIG_PMIC_DA9052=y
CONFIG_MFD_DA9052_SPI=y
CONFIG_MFD_DA9052_I2C=y
CONFIG_MFD_DA9055=y
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_HTC_PASIC3 is not set
CONFIG_HTC_I2CPLD=y
CONFIG_LPC_ICH=m
# CONFIG_LPC_SCH is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
CONFIG_MFD_88PM860X=y
# CONFIG_MFD_MAX14577 is not set
CONFIG_MFD_MAX77686=y
CONFIG_MFD_MAX77693=y
# CONFIG_MFD_MAX8907 is not set
CONFIG_MFD_MAX8925=y
CONFIG_MFD_MAX8997=y
CONFIG_MFD_MAX8998=y
CONFIG_EZX_PCAP=y
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RTSX_PCI is not set
CONFIG_MFD_RC5T583=y
CONFIG_MFD_SEC_CORE=y
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SM501 is not set
CONFIG_MFD_SMSC=y
CONFIG_ABX500_CORE=y
CONFIG_AB3100_CORE=y
# CONFIG_AB3100_OTP is not set
CONFIG_MFD_STMPE=y
#
# STMicroelectronics STMPE Interface Drivers
#
CONFIG_STMPE_I2C=y
CONFIG_STMPE_SPI=y
# CONFIG_MFD_SYSCON is not set
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
CONFIG_MFD_LP8788=y
CONFIG_MFD_PALMAS=y
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
CONFIG_MFD_TPS65090=y
# CONFIG_MFD_TPS65217 is not set
CONFIG_MFD_TPS6586X=y
CONFIG_MFD_TPS65910=y
CONFIG_MFD_TPS65912=y
CONFIG_MFD_TPS65912_I2C=y
CONFIG_MFD_TPS65912_SPI=y
# CONFIG_MFD_TPS80031 is not set
# CONFIG_TWL4030_CORE is not set
CONFIG_TWL6040_CORE=y
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TIMBERDALE is not set
CONFIG_MFD_TC3589X=y
# CONFIG_MFD_TMIO is not set
# CONFIG_MFD_VX855 is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
CONFIG_MFD_WM8400=y
CONFIG_MFD_WM831X=y
CONFIG_MFD_WM831X_I2C=y
CONFIG_MFD_WM831X_SPI=y
CONFIG_MFD_WM8350=y
CONFIG_MFD_WM8350_I2C=y
CONFIG_MFD_WM8994=y
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
# CONFIG_REGULATOR_FIXED_VOLTAGE is not set
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
CONFIG_REGULATOR_88PM8607=y
# CONFIG_REGULATOR_ACT8865 is not set
# CONFIG_REGULATOR_AD5398 is not set
# CONFIG_REGULATOR_AAT2870 is not set
# CONFIG_REGULATOR_AB3100 is not set
# CONFIG_REGULATOR_DA903X is not set
# CONFIG_REGULATOR_DA9052 is not set
# CONFIG_REGULATOR_DA9055 is not set
# CONFIG_REGULATOR_DA9210 is not set
# CONFIG_REGULATOR_FAN53555 is not set
# CONFIG_REGULATOR_GPIO is not set
# CONFIG_REGULATOR_ISL6271A is not set
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_LP3972 is not set
CONFIG_REGULATOR_LP872X=y
# CONFIG_REGULATOR_LP8755 is not set
CONFIG_REGULATOR_LP8788=y
# CONFIG_REGULATOR_MAX1586 is not set
# CONFIG_REGULATOR_MAX8649 is not set
# CONFIG_REGULATOR_MAX8660 is not set
# CONFIG_REGULATOR_MAX8925 is not set
# CONFIG_REGULATOR_MAX8952 is not set
# CONFIG_REGULATOR_MAX8973 is not set
# CONFIG_REGULATOR_MAX8997 is not set
# CONFIG_REGULATOR_MAX8998 is not set
# CONFIG_REGULATOR_MAX77686 is not set
# CONFIG_REGULATOR_MAX77693 is not set
# CONFIG_REGULATOR_PALMAS is not set
# CONFIG_REGULATOR_PCAP is not set
# CONFIG_REGULATOR_PFUZE100 is not set
# CONFIG_REGULATOR_RC5T583 is not set
# CONFIG_REGULATOR_S2MPS11 is not set
# CONFIG_REGULATOR_S5M8767 is not set
# CONFIG_REGULATOR_TPS51632 is not set
# CONFIG_REGULATOR_TPS62360 is not set
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
# CONFIG_REGULATOR_TPS65090 is not set
# CONFIG_REGULATOR_TPS6524X is not set
# CONFIG_REGULATOR_TPS6586X is not set
# CONFIG_REGULATOR_TPS65910 is not set
# CONFIG_REGULATOR_TPS65912 is not set
# CONFIG_REGULATOR_WM831X is not set
# CONFIG_REGULATOR_WM8350 is not set
# CONFIG_REGULATOR_WM8400 is not set
# CONFIG_REGULATOR_WM8994 is not set
CONFIG_MEDIA_SUPPORT=m
#
# Multimedia core support
#
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y
CONFIG_MEDIA_RADIO_SUPPORT=y
CONFIG_MEDIA_RC_SUPPORT=y
# CONFIG_MEDIA_CONTROLLER is not set
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_V4L2=m
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_MEMOPS=m
CONFIG_VIDEOBUF2_VMALLOC=m
CONFIG_DVB_CORE=m
CONFIG_DVB_NET=y
# CONFIG_TTPCI_EEPROM is not set
CONFIG_DVB_MAX_ADAPTERS=8
CONFIG_DVB_DYNAMIC_MINORS=y
#
# Media drivers
#
CONFIG_RC_CORE=m
# CONFIG_RC_MAP is not set
CONFIG_RC_DECODERS=y
# CONFIG_LIRC is not set
# CONFIG_IR_NEC_DECODER is not set
# CONFIG_IR_RC5_DECODER is not set
# CONFIG_IR_RC6_DECODER is not set
# CONFIG_IR_JVC_DECODER is not set
# CONFIG_IR_SONY_DECODER is not set
# CONFIG_IR_RC5_SZ_DECODER is not set
# CONFIG_IR_SANYO_DECODER is not set
# CONFIG_IR_MCE_KBD_DECODER is not set
CONFIG_RC_DEVICES=y
# CONFIG_RC_ATI_REMOTE is not set
# CONFIG_IR_ENE is not set
# CONFIG_IR_IMON is not set
# CONFIG_IR_MCEUSB is not set
# CONFIG_IR_ITE_CIR is not set
# CONFIG_IR_FINTEK is not set
# CONFIG_IR_NUVOTON is not set
# CONFIG_IR_REDRAT3 is not set
# CONFIG_IR_STREAMZAP is not set
# CONFIG_IR_WINBOND_CIR is not set
# CONFIG_IR_IGUANA is not set
# CONFIG_IR_TTUSBIR is not set
# CONFIG_RC_LOOPBACK is not set
# CONFIG_IR_GPIO_CIR is not set
CONFIG_MEDIA_USB_SUPPORT=y
#
# Webcam devices
#
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
# CONFIG_USB_GSPCA is not set
# CONFIG_USB_PWC is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_USB_S2255 is not set
# CONFIG_VIDEO_USBTV is not set
#
# Analog TV USB devices
#
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_HDPVR is not set
# CONFIG_VIDEO_TLG2300 is not set
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_VIDEO_STK1160_COMMON is not set
#
# Analog/digital TV USB devices
#
# CONFIG_VIDEO_AU0828 is not set
# CONFIG_VIDEO_CX231XX is not set
# CONFIG_VIDEO_TM6000 is not set
#
# Digital TV USB devices
#
# CONFIG_DVB_USB is not set
# CONFIG_DVB_USB_V2 is not set
# CONFIG_DVB_TTUSB_BUDGET is not set
# CONFIG_DVB_TTUSB_DEC is not set
# CONFIG_SMS_USB_DRV is not set
# CONFIG_DVB_B2C2_FLEXCOP_USB is not set
#
# Webcam, TV (analog/digital) USB devices
#
# CONFIG_VIDEO_EM28XX is not set
CONFIG_MEDIA_PCI_SUPPORT=y
#
# Media capture support
#
#
# Media capture/analog TV support
#
# CONFIG_VIDEO_IVTV is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_MXB is not set
#
# Media capture/analog/hybrid TV support
#
# CONFIG_VIDEO_CX18 is not set
# CONFIG_VIDEO_CX23885 is not set
# CONFIG_VIDEO_CX25821 is not set
# CONFIG_VIDEO_CX88 is not set
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_SAA7164 is not set
#
# Media digital TV PCI Adapters
#
# CONFIG_DVB_AV7110 is not set
# CONFIG_DVB_BUDGET_CORE is not set
# CONFIG_DVB_B2C2_FLEXCOP_PCI is not set
# CONFIG_DVB_PLUTO2 is not set
# CONFIG_DVB_DM1105 is not set
# CONFIG_DVB_PT1 is not set
# CONFIG_MANTIS_CORE is not set
# CONFIG_DVB_NGENE is not set
# CONFIG_DVB_DDBRIDGE is not set
CONFIG_V4L_PLATFORM_DRIVERS=y
# CONFIG_VIDEO_CAFE_CCIC is not set
# CONFIG_VIDEO_TIMBERDALE is not set
# CONFIG_SOC_CAMERA is not set
CONFIG_V4L_MEM2MEM_DRIVERS=y
# CONFIG_VIDEO_MEM2MEM_DEINTERLACE is not set
# CONFIG_VIDEO_SH_VEU is not set
CONFIG_V4L_TEST_DRIVERS=y
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_MEM2MEM_TESTDEV is not set
#
# Supported MMC/SDIO adapters
#
# CONFIG_SMS_SDIO_DRV is not set
CONFIG_MEDIA_PARPORT_SUPPORT=y
# CONFIG_VIDEO_BWQCAM is not set
# CONFIG_VIDEO_CQCAM is not set
# CONFIG_VIDEO_W9966 is not set
CONFIG_RADIO_ADAPTERS=y
CONFIG_RADIO_SI470X=y
# CONFIG_USB_SI470X is not set
# CONFIG_I2C_SI470X is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_MR800 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_SHARK is not set
# CONFIG_RADIO_SHARK2 is not set
# CONFIG_USB_KEENE is not set
# CONFIG_USB_RAREMONO is not set
# CONFIG_USB_MA901 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_SAA7706H is not set
# CONFIG_RADIO_TEF6862 is not set
# CONFIG_RADIO_WL1273 is not set
#
# Texas Instruments WL128x FM driver (ST based)
#
# CONFIG_RADIO_WL128X is not set
# CONFIG_CYPRESS_FIRMWARE is not set
#
# Media ancillary drivers (tuners, sensors, i2c, frontends)
#
CONFIG_MEDIA_SUBDRV_AUTOSELECT=y
CONFIG_MEDIA_ATTACH=y
CONFIG_VIDEO_IR_I2C=m
#
# Audio decoders, processors and mixers
#
#
# RDS decoders
#
#
# Video decoders
#
#
# Video and audio decoders
#
#
# Video encoders
#
#
# Camera sensor devices
#
#
# Flash devices
#
#
# Video improvement chips
#
#
# Audio/Video compression chips
#
#
# Miscellaneous helper chips
#
#
# Sensors used on soc_camera driver
#
CONFIG_MEDIA_TUNER=m
CONFIG_MEDIA_TUNER_SIMPLE=m
CONFIG_MEDIA_TUNER_TDA8290=m
CONFIG_MEDIA_TUNER_TDA827X=m
CONFIG_MEDIA_TUNER_TDA18271=m
CONFIG_MEDIA_TUNER_TDA9887=m
CONFIG_MEDIA_TUNER_TEA5761=m
CONFIG_MEDIA_TUNER_TEA5767=m
CONFIG_MEDIA_TUNER_MT20XX=m
CONFIG_MEDIA_TUNER_XC2028=m
CONFIG_MEDIA_TUNER_XC5000=m
CONFIG_MEDIA_TUNER_XC4000=m
CONFIG_MEDIA_TUNER_MC44S803=m
#
# Multistandard (satellite) frontends
#
#
# Multistandard (cable + terrestrial) frontends
#
#
# DVB-S (satellite) frontends
#
#
# DVB-T (terrestrial) frontends
#
#
# DVB-C (cable) frontends
#
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
#
#
# ISDB-T (terrestrial) frontends
#
#
# Digital terrestrial only tuners/PLL
#
#
# SEC control devices for DVB-S
#
#
# Tools to develop new frontends
#
# CONFIG_DVB_DUMMY_FE is not set
#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
# CONFIG_AGP_SIS is not set
CONFIG_AGP_VIA=y
CONFIG_INTEL_GTT=y
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
CONFIG_VGA_SWITCHEROO=y
CONFIG_DRM=m
CONFIG_DRM_KMS_HELPER=m
CONFIG_DRM_KMS_FB_HELPER=y
CONFIG_DRM_LOAD_EDID_FIRMWARE=y
#
# I2C encoder or helper chips
#
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_NOUVEAU is not set
# CONFIG_DRM_I810 is not set
CONFIG_DRM_I915=m
CONFIG_DRM_I915_KMS=y
CONFIG_DRM_I915_FBDEV=y
# CONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT is not set
# CONFIG_DRM_I915_UMS is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_DRM_VMWGFX is not set
# CONFIG_DRM_GMA500 is not set
# CONFIG_DRM_UDL is not set
# CONFIG_DRM_AST is not set
# CONFIG_DRM_MGAG200 is not set
# CONFIG_DRM_CIRRUS_QEMU is not set
# CONFIG_DRM_QXL is not set
# CONFIG_DRM_BOCHS is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_HDMI=y
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
CONFIG_FB_ASILIANT=y
CONFIG_FB_IMSTT=y
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
# CONFIG_FB_VESA is not set
CONFIG_FB_EFI=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_TMIO is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_GOLDFISH is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_XEN_FBDEV_FRONTEND is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
# CONFIG_FB_AUO_K190X is not set
# CONFIG_FB_SIMPLE is not set
CONFIG_EXYNOS_VIDEO=y
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
# CONFIG_BACKLIGHT_PWM is not set
# CONFIG_BACKLIGHT_DA903X is not set
# CONFIG_BACKLIGHT_DA9052 is not set
# CONFIG_BACKLIGHT_MAX8925 is not set
# CONFIG_BACKLIGHT_APPLE is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_WM831X is not set
# CONFIG_BACKLIGHT_ADP5520 is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_88PM860X is not set
# CONFIG_BACKLIGHT_AAT2870 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LP855X is not set
# CONFIG_BACKLIGHT_LP8788 is not set
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_LOGO is not set
CONFIG_SOUND=m
# CONFIG_SOUND_OSS_CORE is not set
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_JACK=y
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
# CONFIG_SND_MIXER_OSS is not set
# CONFIG_SND_PCM_OSS is not set
# CONFIG_SND_SEQUENCER_OSS is not set
# CONFIG_SND_HRTIMER is not set
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_MAX_CARDS=32
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_KCTL_JACK=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_RAWMIDI_SEQ=m
# CONFIG_SND_OPL3_LIB_SEQ is not set
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
# CONFIG_SND_EMU10K1_SEQ is not set
CONFIG_SND_DRIVERS=y
# CONFIG_SND_PCSP is not set
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_ALOOP is not set
CONFIG_SND_VIRMIDI=m
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_PORTMAN2X4 is not set
CONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ASIHPI is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_CTXFI is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDA_INTEL=m
CONFIG_SND_HDA_PREALLOC_SIZE=64
CONFIG_SND_HDA_HWDEP=y
CONFIG_SND_HDA_RECONFIG=y
CONFIG_SND_HDA_INPUT_BEEP=y
CONFIG_SND_HDA_INPUT_BEEP_MODE=0
CONFIG_SND_HDA_INPUT_JACK=y
CONFIG_SND_HDA_PATCH_LOADER=y
CONFIG_SND_HDA_CODEC_REALTEK=m
CONFIG_SND_HDA_CODEC_ANALOG=m
CONFIG_SND_HDA_CODEC_SIGMATEL=m
CONFIG_SND_HDA_CODEC_VIA=m
CONFIG_SND_HDA_CODEC_HDMI=m
CONFIG_SND_HDA_I915=y
CONFIG_SND_HDA_CODEC_CIRRUS=m
CONFIG_SND_HDA_CODEC_CONEXANT=m
CONFIG_SND_HDA_CODEC_CA0110=m
CONFIG_SND_HDA_CODEC_CA0132=m
# CONFIG_SND_HDA_CODEC_CA0132_DSP is not set
CONFIG_SND_HDA_CODEC_CMEDIA=m
CONFIG_SND_HDA_CODEC_SI3054=m
CONFIG_SND_HDA_GENERIC=m
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_LOLA is not set
# CONFIG_SND_LX6464ES is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_SPI=y
CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_UA101 is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_US122L is not set
# CONFIG_SND_USB_6FIRE is not set
# CONFIG_SND_USB_HIFACE is not set
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
#
# HID support
#
CONFIG_HID=m
CONFIG_HIDRAW=y
# CONFIG_UHID is not set
CONFIG_HID_GENERIC=m
#
# Special HID drivers
#
# CONFIG_HID_A4TECH is not set
# CONFIG_HID_ACRUX is not set
# CONFIG_HID_APPLE is not set
# CONFIG_HID_APPLEIR is not set
# CONFIG_HID_AUREAL is not set
# CONFIG_HID_BELKIN is not set
# CONFIG_HID_CHERRY is not set
# CONFIG_HID_CHICONY is not set
# CONFIG_HID_PRODIKEYS is not set
# CONFIG_HID_CYPRESS is not set
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_ELO is not set
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_HUION is not set
# CONFIG_HID_KEYTOUCH is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_ICADE is not set
# CONFIG_HID_TWINHAN is not set
# CONFIG_HID_KENSINGTON is not set
# CONFIG_HID_LCPOWER is not set
# CONFIG_HID_LENOVO_TPKBD is not set
# CONFIG_HID_LOGITECH is not set
# CONFIG_HID_MAGICMOUSE is not set
# CONFIG_HID_MICROSOFT is not set
# CONFIG_HID_MONTEREY is not set
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_SAITEK is not set
# CONFIG_HID_SAMSUNG is not set
# CONFIG_HID_SONY is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_STEELSERIES is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_THINGM is not set
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_WACOM is not set
# CONFIG_HID_WIIMOTE is not set
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set
#
# USB HID support
#
CONFIG_USB_HID=m
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
#
# I2C HID support
#
# CONFIG_I2C_HID is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
#
# Miscellaneous USB options
#
CONFIG_USB_DEFAULT_PERSIST=y
CONFIG_USB_DYNAMIC_MINORS=y
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
CONFIG_USB_MON=m
# CONFIG_USB_WUSB_CBAF is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_XHCI_HCD=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
CONFIG_USB_EHCI_HCD_PLATFORM=y
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
# CONFIG_USB_FUSBH200_HCD is not set
# CONFIG_USB_FOTG210_HCD is not set
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_PCI=y
CONFIG_USB_OHCI_HCD_PLATFORM=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HCD_TEST_MODE is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_REALTEK is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_STORAGE_ENE_UB6250 is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not set
# CONFIG_USB_DWC2 is not set
# CONFIG_USB_CHIPIDEA is not set
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_EHSET_TEST_FIXTURE is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_EZUSB_FX2 is not set
# CONFIG_USB_HSIC_USB3503 is not set
#
# USB Physical Layer drivers
#
# CONFIG_USB_PHY is not set
# CONFIG_USB_OTG_FSM is not set
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_SAMSUNG_USB2PHY is not set
# CONFIG_SAMSUNG_USB3PHY is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ISP1301 is not set
# CONFIG_USB_RCAR_PHY is not set
# CONFIG_USB_GADGET is not set
# CONFIG_UWB is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
# CONFIG_MMC_CLKGATE is not set
#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_MINORS=8
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PCI=m
# CONFIG_MMC_RICOH_MMC is not set
# CONFIG_MMC_SDHCI_ACPI is not set
# CONFIG_MMC_SDHCI_PLTFM is not set
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_MMC_SPI is not set
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
# CONFIG_MMC_VUB300 is not set
# CONFIG_MMC_USHC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
#
# LED drivers
#
# CONFIG_LEDS_88PM860X is not set
# CONFIG_LEDS_LM3530 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not set
# CONFIG_LEDS_LP3944 is not set
# CONFIG_LEDS_LP5521 is not set
# CONFIG_LEDS_LP5523 is not set
# CONFIG_LEDS_LP5562 is not set
# CONFIG_LEDS_LP8501 is not set
# CONFIG_LEDS_LP8788 is not set
# CONFIG_LEDS_CLEVO_MAIL is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_PCA9685 is not set
# CONFIG_LEDS_WM831X_STATUS is not set
# CONFIG_LEDS_WM8350 is not set
# CONFIG_LEDS_DA903X is not set
# CONFIG_LEDS_DA9052 is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_PWM is not set
# CONFIG_LEDS_REGULATOR is not set
# CONFIG_LEDS_BD2802 is not set
# CONFIG_LEDS_INTEL_SS4200 is not set
# CONFIG_LEDS_LT3593 is not set
# CONFIG_LEDS_ADP5520 is not set
# CONFIG_LEDS_DELL_NETBOOKS is not set
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_MAX8997 is not set
# CONFIG_LEDS_LM355x is not set
# CONFIG_LEDS_OT200 is not set
# CONFIG_LEDS_BLINKM is not set
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_ONESHOT is not set
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
CONFIG_LEDS_TRIGGER_CPU=y
# CONFIG_LEDS_TRIGGER_GPIO is not set
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set
#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_LEDS_TRIGGER_TRANSIENT is not set
# CONFIG_LEDS_TRIGGER_CAMERA is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y
CONFIG_EDAC_LEGACY_SYSFS=y
# CONFIG_EDAC_DEBUG is not set
# CONFIG_EDAC_DECODE_MCE is not set
# CONFIG_EDAC_MM_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_88PM860X is not set
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_LP8788 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_MAX8925 is not set
# CONFIG_RTC_DRV_MAX8998 is not set
# CONFIG_RTC_DRV_MAX8997 is not set
# CONFIG_RTC_DRV_MAX77686 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_ISL12057 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PALMAS is not set
# CONFIG_RTC_DRV_PCF2127 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_TPS6586X is not set
# CONFIG_RTC_DRV_TPS65910 is not set
# CONFIG_RTC_DRV_RC5T583 is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set
# CONFIG_RTC_DRV_S5M is not set
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_DS3234 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_RX4581 is not set
#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DA9052 is not set
# CONFIG_RTC_DRV_DA9055 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
# CONFIG_RTC_DRV_DS2404 is not set
# CONFIG_RTC_DRV_WM831X is not set
# CONFIG_RTC_DRV_WM8350 is not set
# CONFIG_RTC_DRV_AB3100 is not set
#
# on-CPU RTC drivers
#
# CONFIG_RTC_DRV_PCAP is not set
# CONFIG_RTC_DRV_MOXART is not set
#
# HID Sensor RTC drivers
#
# CONFIG_RTC_DRV_HID_SENSOR_TIME is not set
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#
# CONFIG_INTEL_MID_DMAC is not set
# CONFIG_INTEL_IOATDMA is not set
# CONFIG_DW_DMAC_CORE is not set
# CONFIG_DW_DMAC is not set
# CONFIG_DW_DMAC_PCI is not set
# CONFIG_TIMB_DMA is not set
# CONFIG_PCH_DMA is not set
CONFIG_DMA_ENGINE=y
CONFIG_DMA_ACPI=y
#
# DMA Clients
#
# CONFIG_ASYNC_TX_DMA is not set
# CONFIG_DMATEST is not set
CONFIG_AUXDISPLAY=y
# CONFIG_KS0108 is not set
# CONFIG_UIO is not set
# CONFIG_VFIO is not set
CONFIG_VIRT_DRIVERS=y
CONFIG_VIRTIO=y
#
# Virtio drivers
#
CONFIG_VIRTIO_PCI=y
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_VIRTIO_MMIO is not set
#
# Microsoft Hyper-V guest support
#
# CONFIG_HYPERV is not set
#
# Xen driver support
#
CONFIG_XEN_BALLOON=y
CONFIG_XEN_SELFBALLOONING=y
CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y
CONFIG_XEN_SCRUB_PAGES=y
# CONFIG_XEN_DEV_EVTCHN is not set
CONFIG_XEN_BACKEND=y
# CONFIG_XENFS is not set
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_XEN_XENBUS_FRONTEND=y
# CONFIG_XEN_GNTDEV is not set
# CONFIG_XEN_GRANT_DEV_ALLOC is not set
CONFIG_SWIOTLB_XEN=y
CONFIG_XEN_TMEM=m
# CONFIG_XEN_PCIDEV_BACKEND is not set
CONFIG_XEN_PRIVCMD=m
CONFIG_XEN_ACPI_PROCESSOR=y
CONFIG_XEN_MCE_LOG=y
CONFIG_XEN_HAVE_PVMMU=y
CONFIG_STAGING=y
# CONFIG_ET131X is not set
# CONFIG_SLICOSS is not set
# CONFIG_USBIP_CORE is not set
# CONFIG_W35UND is not set
# CONFIG_PRISM2_USB is not set
# CONFIG_ECHO is not set
# CONFIG_COMEDI is not set
# CONFIG_PANEL is not set
# CONFIG_R8187SE is not set
# CONFIG_RTL8192U is not set
# CONFIG_RTLLIB is not set
# CONFIG_R8712U is not set
# CONFIG_R8188EU is not set
# CONFIG_R8821AE is not set
# CONFIG_RTS5139 is not set
# CONFIG_RTS5208 is not set
# CONFIG_TRANZPORT is not set
# CONFIG_IDE_PHISON is not set
# CONFIG_LINE6_USB is not set
# CONFIG_VT6655 is not set
# CONFIG_VT6656 is not set
# CONFIG_DX_SEP is not set
# CONFIG_FB_SM7XX is not set
# CONFIG_CRYSTALHD is not set
# CONFIG_FB_XGI is not set
# CONFIG_ACPI_QUICKSTART is not set
# CONFIG_USB_ENESTORAGE is not set
# CONFIG_BCM_WIMAX is not set
# CONFIG_FT1000 is not set
#
# Speakup console speech
#
# CONFIG_SPEAKUP is not set
# CONFIG_TOUCHSCREEN_CLEARPAD_TM1217 is not set
# CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4 is not set
CONFIG_STAGING_MEDIA=y
# CONFIG_DVB_AS102 is not set
# CONFIG_I2C_BCM2048 is not set
# CONFIG_DVB_CXD2099 is not set
# CONFIG_VIDEO_DT3155 is not set
# CONFIG_VIDEO_GO7007 is not set
# CONFIG_USB_MSI3101 is not set
# CONFIG_VIDEO_TCM825X is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_SOLO6X10 is not set
#
# Android
#
CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ASHMEM=y
# CONFIG_ANDROID_LOGGER is not set
CONFIG_ANDROID_TIMED_OUTPUT=y
# CONFIG_ANDROID_TIMED_GPIO is not set
CONFIG_ANDROID_LOW_MEMORY_KILLER=y
CONFIG_ANDROID_INTF_ALARM_DEV=y
# CONFIG_SYNC is not set
# CONFIG_ION is not set
# CONFIG_USB_WPAN_HCD is not set
# CONFIG_WIMAX_GDM72XX is not set
# CONFIG_LTE_GDM724X is not set
CONFIG_NET_VENDOR_SILICOM=y
# CONFIG_SBYPASS is not set
# CONFIG_BPCTL is not set
# CONFIG_CED1401 is not set
# CONFIG_DGRP is not set
# CONFIG_LUSTRE_FS is not set
# CONFIG_XILLYBUS is not set
# CONFIG_DGNC is not set
# CONFIG_DGAP is not set
CONFIG_X86_PLATFORM_DEVICES=y
# CONFIG_ACER_WMI is not set
# CONFIG_ACERHDF is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_DELL_WMI is not set
# CONFIG_DELL_WMI_AIO is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_FUJITSU_TABLET is not set
# CONFIG_AMILO_RFKILL is not set
# CONFIG_HP_ACCEL is not set
# CONFIG_HP_WIRELESS is not set
# CONFIG_HP_WMI is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_PANASONIC_LAPTOP is not set
# CONFIG_COMPAL_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_IDEAPAD_LAPTOP is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_INTEL_MENLOW is not set
# CONFIG_EEEPC_LAPTOP is not set
# CONFIG_ASUS_WMI is not set
CONFIG_ACPI_WMI=m
# CONFIG_MSI_WMI is not set
# CONFIG_TOPSTAR_LAPTOP is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_TOSHIBA_BT_RFKILL is not set
# CONFIG_ACPI_CMPC is not set
# CONFIG_INTEL_IPS is not set
# CONFIG_IBM_RTL is not set
# CONFIG_XO15_EBOOK is not set
CONFIG_SAMSUNG_LAPTOP=m
# CONFIG_MXM_WMI is not set
# CONFIG_INTEL_OAKTRAIL is not set
# CONFIG_SAMSUNG_Q10 is not set
# CONFIG_APPLE_GMUX is not set
# CONFIG_INTEL_RST is not set
# CONFIG_INTEL_SMARTCONNECT is not set
# CONFIG_PVPANIC is not set
# CONFIG_CHROME_PLATFORMS is not set
#
# Hardware Spinlock drivers
#
CONFIG_CLKEVT_I8253=y
CONFIG_I8253_LOCK=y
CONFIG_CLKBLD_I8253=y
# CONFIG_MAILBOX is not set
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_STATS=y
# CONFIG_AMD_IOMMU_V2 is not set
CONFIG_DMAR_TABLE=y
CONFIG_INTEL_IOMMU=y
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
CONFIG_INTEL_IOMMU_FLOPPY_WA=y
CONFIG_IRQ_REMAP=y
#
# Remoteproc drivers
#
# CONFIG_STE_MODEM_RPROC is not set
#
# Rpmsg drivers
#
CONFIG_PM_DEVFREQ=y
#
# DEVFREQ Governors
#
CONFIG_DEVFREQ_GOV_SIMPLE_ONDEMAND=y
CONFIG_DEVFREQ_GOV_PERFORMANCE=y
CONFIG_DEVFREQ_GOV_POWERSAVE=y
CONFIG_DEVFREQ_GOV_USERSPACE=y
#
# DEVFREQ Drivers
#
CONFIG_EXTCON=y
#
# Extcon Device Drivers
#
# CONFIG_EXTCON_GPIO is not set
# CONFIG_EXTCON_MAX77693 is not set
# CONFIG_EXTCON_MAX8997 is not set
# CONFIG_EXTCON_PALMAS is not set
CONFIG_MEMORY=y
# CONFIG_IIO is not set
# CONFIG_NTB is not set
# CONFIG_VME_BUS is not set
CONFIG_PWM=y
CONFIG_PWM_SYSFS=y
# CONFIG_IPACK_BUS is not set
# CONFIG_RESET_CONTROLLER is not set
# CONFIG_FMC is not set
#
# PHY Subsystem
#
# CONFIG_GENERIC_PHY is not set
# CONFIG_PHY_EXYNOS_MIPI_VIDEO is not set
# CONFIG_POWERCAP is not set
#
# Firmware Drivers
#
CONFIG_EDD=y
CONFIG_EDD_OFF=y
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
# CONFIG_DMI_SYSFS is not set
CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y
CONFIG_ISCSI_IBFT_FIND=y
# CONFIG_ISCSI_IBFT is not set
# CONFIG_GOOGLE_FIRMWARE is not set
#
# EFI (Extensible Firmware Interface) Support
#
CONFIG_EFI_VARS=y
CONFIG_EFI_VARS_PSTORE=y
# CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE is not set
CONFIG_EFI_RUNTIME_MAP=y
CONFIG_UEFI_CPER=y
#
# File systems
#
CONFIG_DCACHE_WORD_ACCESS=y
# CONFIG_EXT2_FS is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_DEFAULTS_TO_ORDERED=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT23=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_XFS_FS=m
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
# CONFIG_XFS_WARN is not set
# CONFIG_XFS_DEBUG is not set
# CONFIG_GFS2_FS is not set
CONFIG_BTRFS_FS=m
CONFIG_BTRFS_FS_POSIX_ACL=y
# CONFIG_BTRFS_FS_CHECK_INTEGRITY is not set
# CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set
# CONFIG_BTRFS_DEBUG is not set
# CONFIG_BTRFS_ASSERT is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_EXPORTFS=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
# CONFIG_PRINT_QUOTA_WARNING is not set
# CONFIG_QUOTA_DEBUG is not set
# CONFIG_QFMT_V1 is not set
# CONFIG_QFMT_V2 is not set
CONFIG_QUOTACTL=y
CONFIG_QUOTACTL_COMPAT=y
# CONFIG_AUTOFS4_FS is not set
CONFIG_FUSE_FS=y
# CONFIG_CUSE is not set
#
# Caches
#
# CONFIG_FSCACHE is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
# CONFIG_MSDOS_FS is not set
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
CONFIG_HUGETLBFS=y
CONFIG_HUGETLB_PAGE=y
# CONFIG_CONFIGFS_FS is not set
CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
CONFIG_ECRYPT_FS=y
# CONFIG_ECRYPT_FS_MESSAGING is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_LOGFS is not set
# CONFIG_CRAMFS is not set
CONFIG_SQUASHFS=m
CONFIG_SQUASHFS_FILE_CACHE=y
# CONFIG_SQUASHFS_FILE_DIRECT is not set
CONFIG_SQUASHFS_DECOMP_SINGLE=y
# CONFIG_SQUASHFS_DECOMP_MULTI is not set
# CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU is not set
CONFIG_SQUASHFS_XATTR=y
CONFIG_SQUASHFS_ZLIB=y
CONFIG_SQUASHFS_LZO=y
CONFIG_SQUASHFS_XZ=y
# CONFIG_SQUASHFS_4K_DEVBLK_SIZE is not set
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_PSTORE=y
# CONFIG_PSTORE_CONSOLE is not set
# CONFIG_PSTORE_FTRACE is not set
# CONFIG_PSTORE_RAM is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_F2FS_FS is not set
# CONFIG_EFIVAR_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
# CONFIG_NLS_UTF8 is not set
#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
CONFIG_DEFAULT_MESSAGE_LOGLEVEL=4
CONFIG_BOOT_PRINTK_DELAY=y
# CONFIG_DYNAMIC_DEBUG is not set
#
# Compile-time checks and compiler options
#
# CONFIG_DEBUG_INFO is not set
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
CONFIG_FRAME_WARN=1024
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_READABLE_ASM is not set
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
CONFIG_MAGIC_SYSRQ=y
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1
CONFIG_DEBUG_KERNEL=y
#
# Memory Debugging
#
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_MEMORY_INIT is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
CONFIG_HAVE_DEBUG_STACKOVERFLOW=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_DEBUG_SHIRQ is not set
#
# Debug Lockups and Hangs
#
CONFIG_LOCKUP_DETECTOR=y
CONFIG_HARDLOCKUP_DETECTOR=y
# CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=0
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
# CONFIG_PANIC_ON_OOPS is not set
CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_PANIC_TIMEOUT=0
CONFIG_SCHED_DEBUG=y
CONFIG_SCHEDSTATS=y
CONFIG_TIMER_STATS=y
#
# Lock Debugging (spinlocks, mutexes, etc...)
#
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_WRITECOUNT is not set
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
#
# RCU Debugging
#
# CONFIG_SPARSE_RCU_POINTER is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=60
# CONFIG_RCU_CPU_STALL_INFO is not set
# CONFIG_RCU_TRACE is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_LATENCYTOP=y
CONFIG_ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS=y
# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_FENTRY=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACER_MAX_TRACE=y
CONFIG_TRACE_CLOCK=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
CONFIG_FUNCTION_TRACER=y
CONFIG_FUNCTION_GRAPH_TRACER=y
# CONFIG_IRQSOFF_TRACER is not set
CONFIG_SCHED_TRACER=y
CONFIG_FTRACE_SYSCALLS=y
CONFIG_TRACER_SNAPSHOT=y
# CONFIG_TRACER_SNAPSHOT_PER_CPU_SWAP is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
CONFIG_STACK_TRACER=y
CONFIG_BLK_DEV_IO_TRACE=y
CONFIG_KPROBE_EVENT=y
CONFIG_UPROBE_EVENT=y
CONFIG_PROBE_EVENTS=y
CONFIG_DYNAMIC_FTRACE=y
CONFIG_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_FUNCTION_PROFILER=y
CONFIG_FTRACE_MCOUNT_RECORD=y
# CONFIG_FTRACE_STARTUP_TEST is not set
CONFIG_MMIOTRACE=y
# CONFIG_MMIOTRACE_TEST is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
# CONFIG_RING_BUFFER_STARTUP_TEST is not set
#
# Runtime Testing
#
# CONFIG_LKDTM is not set
# CONFIG_TEST_LIST_SORT is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_RBTREE_TEST is not set
# CONFIG_INTERVAL_TREE_TEST is not set
# CONFIG_PERCPU_TEST is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_TEST_STRING_HELPERS is not set
# CONFIG_TEST_KSTRTOX is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_TEST_MODULE is not set
# CONFIG_TEST_USER_COPY is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
# CONFIG_KGDB_TESTS is not set
CONFIG_KGDB_LOW_LEVEL_TRAP=y
CONFIG_KGDB_KDB=y
CONFIG_KDB_KEYBOARD=y
CONFIG_KDB_CONTINUE_CATASTROPHIC=0
CONFIG_STRICT_DEVMEM=y
# CONFIG_X86_VERBOSE_BOOTUP is not set
CONFIG_EARLY_PRINTK=y
CONFIG_EARLY_PRINTK_DBGP=y
# CONFIG_EARLY_PRINTK_EFI is not set
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
# CONFIG_DEBUG_RODATA_TEST is not set
CONFIG_DEBUG_SET_MODULE_RONX=y
# CONFIG_DEBUG_NX_TEST is not set
CONFIG_DOUBLEFAULT=y
# CONFIG_DEBUG_TLBFLUSH is not set
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
# CONFIG_X86_DECODER_SELFTEST is not set
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
# CONFIG_IO_DELAY_0X80 is not set
CONFIG_IO_DELAY_0XED=y
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=1
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
CONFIG_OPTIMIZE_INLINING=y
# CONFIG_DEBUG_NMI_SELFTEST is not set
# CONFIG_X86_DEBUG_STATIC_CPU_HAS is not set
#
# Security options
#
CONFIG_KEYS=y
# CONFIG_PERSISTENT_KEYRINGS is not set
# CONFIG_BIG_KEYS is not set
CONFIG_TRUSTED_KEYS=y
CONFIG_ENCRYPTED_KEYS=y
# CONFIG_KEYS_DEBUG_PROC_KEYS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_PATH=y
CONFIG_INTEL_TXT=y
CONFIG_LSM_MMAP_MIN_ADDR=0
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0
CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
# CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set
CONFIG_SECURITY_SMACK=y
CONFIG_SECURITY_TOMOYO=y
CONFIG_SECURITY_TOMOYO_MAX_ACCEPT_ENTRY=2048
CONFIG_SECURITY_TOMOYO_MAX_AUDIT_LOG=1024
# CONFIG_SECURITY_TOMOYO_OMIT_USERSPACE_LOADER is not set
CONFIG_SECURITY_TOMOYO_POLICY_LOADER="/sbin/tomoyo-init"
CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER="/sbin/init"
CONFIG_SECURITY_APPARMOR=y
CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
CONFIG_SECURITY_APPARMOR_HASH=y
CONFIG_SECURITY_YAMA=y
CONFIG_SECURITY_YAMA_STACKED=y
CONFIG_INTEGRITY=y
CONFIG_INTEGRITY_SIGNATURE=y
CONFIG_INTEGRITY_AUDIT=y
# CONFIG_INTEGRITY_ASYMMETRIC_KEYS is not set
# CONFIG_IMA is not set
CONFIG_EVM=y
CONFIG_EVM_HMAC_VERSION=2
# CONFIG_DEFAULT_SECURITY_SELINUX is not set
# CONFIG_DEFAULT_SECURITY_SMACK is not set
# CONFIG_DEFAULT_SECURITY_TOMOYO is not set
CONFIG_DEFAULT_SECURITY_APPARMOR=y
# CONFIG_DEFAULT_SECURITY_YAMA is not set
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_DEFAULT_SECURITY="apparmor"
CONFIG_XOR_BLOCKS=m
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_USER is not set
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
CONFIG_CRYPTO_GF128MUL=m
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_PCRYPT is not set
CONFIG_CRYPTO_WORKQUEUE=y
CONFIG_CRYPTO_CRYPTD=m
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_TEST is not set
CONFIG_CRYPTO_ABLK_HELPER=m
CONFIG_CRYPTO_GLUE_HELPER_X86=m
#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
# CONFIG_CRYPTO_GCM is not set
CONFIG_CRYPTO_SEQIV=m
#
# Block modes
#
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_CTR=m
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_LRW=m
# CONFIG_CRYPTO_PCBC is not set
CONFIG_CRYPTO_XTS=m
#
# Hash modes
#
# CONFIG_CRYPTO_CMAC is not set
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set
#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_CRC32C_INTEL=y
# CONFIG_CRYPTO_CRC32 is not set
# CONFIG_CRYPTO_CRC32_PCLMUL is not set
CONFIG_CRYPTO_CRCT10DIF=y
# CONFIG_CRYPTO_CRCT10DIF_PCLMUL is not set
# CONFIG_CRYPTO_GHASH is not set
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA1_SSSE3 is not set
# CONFIG_CRYPTO_SHA256_SSSE3 is not set
# CONFIG_CRYPTO_SHA512_SSSE3 is not set
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set
CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m
#
# Ciphers
#
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_X86_64=m
CONFIG_CRYPTO_AES_NI_INTEL=m
# CONFIG_CRYPTO_ANUBIS is not set
CONFIG_CRYPTO_ARC4=m
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_BLOWFISH_X86_64 is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAMELLIA_X86_64 is not set
# CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64 is not set
# CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64 is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST5_AVX_X86_64 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_CAST6_AVX_X86_64 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_SERPENT_SSE2_X86_64 is not set
# CONFIG_CRYPTO_SERPENT_AVX_X86_64 is not set
# CONFIG_CRYPTO_SERPENT_AVX2_X86_64 is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set
# CONFIG_CRYPTO_TWOFISH_X86_64_3WAY is not set
# CONFIG_CRYPTO_TWOFISH_AVX_X86_64 is not set
#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_ZLIB is not set
CONFIG_CRYPTO_LZO=y
# CONFIG_CRYPTO_LZ4 is not set
# CONFIG_CRYPTO_LZ4HC is not set
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
CONFIG_CRYPTO_HASH_INFO=y
CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=y
# CONFIG_CRYPTO_DEV_PADLOCK_AES is not set
# CONFIG_CRYPTO_DEV_PADLOCK_SHA is not set
# CONFIG_CRYPTO_DEV_CCP is not set
CONFIG_ASYMMETRIC_KEY_TYPE=y
CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y
CONFIG_PUBLIC_KEY_ALGO_RSA=y
CONFIG_X509_CERTIFICATE_PARSER=y
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_HAVE_KVM_IRQ_ROUTING=y
CONFIG_HAVE_KVM_EVENTFD=y
CONFIG_KVM_APIC_ARCHITECTURE=y
CONFIG_KVM_MMIO=y
CONFIG_KVM_ASYNC_PF=y
CONFIG_HAVE_KVM_MSI=y
CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=y
CONFIG_KVM_VFIO=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
# CONFIG_KVM_AMD is not set
# CONFIG_KVM_MMU_AUDIT is not set
CONFIG_KVM_DEVICE_ASSIGNMENT=y
CONFIG_BINARY_PRINTF=y
#
# Library routines
#
CONFIG_RAID6_PQ=m
CONFIG_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_NET_UTILS=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_IO=y
CONFIG_PERCPU_RWSEM=y
CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
# CONFIG_CRC_CCITT is not set
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=m
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=m
# CONFIG_CRC8 is not set
# CONFIG_RANDOM32_SELFTEST is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_ASSOCIATIVE_ARRAY=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_NLATTR=y
CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE=y
CONFIG_AVERAGE=y
CONFIG_CLZ_TAB=y
# CONFIG_CORDIC is not set
CONFIG_DDR=y
CONFIG_MPILIB=y
CONFIG_SIGNATURE=y
CONFIG_OID_REGISTRY=y
CONFIG_UCS2_STRING=y
CONFIG_FONT_SUPPORT=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-03-23 10:57 ` Sedat Dilek
@ 2014-03-23 15:35 ` Al Viro
2014-03-23 16:56 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2014-03-23 15:35 UTC (permalink / raw)
To: Sedat Dilek; +Cc: Linus Torvalds, LKML, linux-fsdevel
On Sun, Mar 23, 2014 at 11:57:16AM +0100, Sedat Dilek wrote:
> Your branch on top of Linux v3.14-rc7-66-g774868c7094d is freezing my
> Ubuntu/precise AMD64 (WUBI) system when running LTP.
Which test?
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-03-23 15:35 ` Al Viro
@ 2014-03-23 16:56 ` Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2014-03-23 16:56 UTC (permalink / raw)
To: Sedat Dilek; +Cc: Linus Torvalds, LKML, linux-fsdevel
On Sun, Mar 23, 2014 at 03:35:05PM +0000, Al Viro wrote:
> On Sun, Mar 23, 2014 at 11:57:16AM +0100, Sedat Dilek wrote:
>
> > Your branch on top of Linux v3.14-rc7-66-g774868c7094d is freezing my
> > Ubuntu/precise AMD64 (WUBI) system when running LTP.
>
> Which test?
Argh... I see what's going on; could you check if the following fixes all
the problems you are seeing?
diff --git a/fs/namespace.c b/fs/namespace.c
index d6e6daf..2ffc5a2 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -746,7 +746,7 @@ static void detach_mnt(struct mount *mnt, struct path *old_path)
mnt->mnt_parent = mnt;
mnt->mnt_mountpoint = mnt->mnt.mnt_root;
list_del_init(&mnt->mnt_child);
- hlist_del_rcu(&mnt->mnt_hash);
+ hlist_del_init_rcu(&mnt->mnt_hash);
put_mountpoint(mnt->mnt_mp);
mnt->mnt_mp = NULL;
}
@@ -1236,7 +1236,7 @@ void umount_tree(struct mount *mnt, int how)
struct mount *last = NULL;
for (p = mnt; p; p = next_mnt(p, mnt)) {
- hlist_del_rcu(&p->mnt_hash);
+ hlist_del_init_rcu(&p->mnt_hash);
hlist_add_head(&p->mnt_hash, &tmp_list);
}
diff --git a/fs/pnode.c b/fs/pnode.c
index 72aa2b7..88396df 100644
--- a/fs/pnode.c
+++ b/fs/pnode.c
@@ -341,7 +341,7 @@ static void __propagate_umount(struct mount *mnt)
* other children
*/
if (child && list_empty(&child->mnt_mounts)) {
- hlist_del_rcu(&child->mnt_hash);
+ hlist_del_init_rcu(&child->mnt_hash);
hlist_add_before_rcu(&child->mnt_hash, &mnt->mnt_hash);
}
}
^ permalink raw reply related [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-03-23 7:16 Al Viro
2014-03-23 10:57 ` Sedat Dilek
@ 2014-03-23 16:36 ` Linus Torvalds
2014-03-23 16:45 ` Al Viro
1 sibling, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2014-03-23 16:36 UTC (permalink / raw)
To: Al Viro; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Sun, Mar 23, 2014 at 12:16 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> Several fixes; first 4 commits are obvious fixes (a couple
> of fdget_pos()-related ones from Eric Biggers, prepend_name() fix, missing
> checks for false negatives from __lookup_mnt() in fs/namei.c)
I'm not seeing the obvious fix in the prepend_name() thing, and I
think it's horrible to *update* the name-len to negative like it now
does.
Why is anybody calling it with a negative buffer length in the first
place? *That* is the bug. Making the buflen become negative just makes
the bug worse, imnsho.
So I'm not pulling this, since the obvious fixes don't all look
obvious to me, and Sedat reports there are problems with it.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2014-03-23 16:36 ` Linus Torvalds
@ 2014-03-23 16:45 ` Al Viro
2014-03-23 17:01 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2014-03-23 16:45 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Sun, Mar 23, 2014 at 09:36:28AM -0700, Linus Torvalds wrote:
> On Sun, Mar 23, 2014 at 12:16 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > Several fixes; first 4 commits are obvious fixes (a couple
> > of fdget_pos()-related ones from Eric Biggers, prepend_name() fix, missing
> > checks for false negatives from __lookup_mnt() in fs/namei.c)
>
> I'm not seeing the obvious fix in the prepend_name() thing, and I
> think it's horrible to *update* the name-len to negative like it now
> does.
>
> Why is anybody calling it with a negative buffer length in the first
> place? *That* is the bug. Making the buflen become negative just makes
> the bug worse, imnsho.
It's easier to skip checking the overflow on prepend() of "\0" in the
beginning of the whole thing and just let the next operation to fail.
That's where the corner case comes from.
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-03-23 16:45 ` Al Viro
@ 2014-03-23 17:01 ` Linus Torvalds
2014-03-24 8:52 ` Sedat Dilek
0 siblings, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2014-03-23 17:01 UTC (permalink / raw)
To: Al Viro; +Cc: Linux Kernel Mailing List, linux-fsdevel
On Sun, Mar 23, 2014 at 9:45 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> It's easier to skip checking the overflow on prepend() of "\0" in the
> beginning of the whole thing and just let the next operation to fail.
> That's where the corner case comes from.
Ok, I'll buy the first four commits. Let's wait for Sedat's report on the rest.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2014-03-23 17:01 ` Linus Torvalds
@ 2014-03-24 8:52 ` Sedat Dilek
2014-03-25 0:46 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Sedat Dilek @ 2014-03-24 8:52 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Al Viro, Linux Kernel Mailing List, linux-fsdevel
On Sun, Mar 23, 2014 at 6:01 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Sun, Mar 23, 2014 at 9:45 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>>
>> It's easier to skip checking the overflow on prepend() of "\0" in the
>> beginning of the whole thing and just let the next operation to fail.
>> That's where the corner case comes from.
>
> Ok, I'll buy the first four commits. Let's wait for Sedat's report on the rest.
>
> Linus
>
Hi,
I have tested w/ Al's patch from [1].
AFAICS this changes are now updated in vfs.git#for-linus branch as
commit 9d25fe7e232b ("switch mnt_hash to hlist").
I had a 2nd trouble w/ the old code, installing a Debian package
resulted also in a freeze.
This now works.
The LTP test is still running... and my -5 kernel with Al's fix seems
to hit the 700+ KiB barrier in my logs.
$ LC_ALL=C ls -l /opt/ltp/runltp-log_3.14.0-rc7-[0-9]*-iniza-small.txt
-rw-r--r-- 1 root root 733184 Mar 23 09:51
/opt/ltp/runltp-log_3.14.0-rc7-4-iniza-small.txt
-rw-r--r-- 1 root root 822533 Mar 24 09:51
/opt/ltp/runltp-log_3.14.0-rc7-5-iniza-small.txt
-rw-r--r-- 1 root root 1142248 Mar 23 11:44
/opt/ltp/runltp-log_3.14.0-rc7-66-iniza-small.txt
[ NOTE ]
-66: vanilla Linus-tree
-4: -66 plus old vfs-fixes
-5: -66 plus old vfs-fixes plus Al's fix from [1]
If you like give the usual credits.
Regards,
- Sedat -
P.S.: [Off-topic] With vanilla -66 kernel I have some OOPS in the
oom[1..5] tests of LTP. Whom to adress? mm-folks?
[1] http://marc.info/?l=linux-kernel&m=139559379906251&w=2
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2014-03-24 8:52 ` Sedat Dilek
@ 2014-03-25 0:46 ` Linus Torvalds
2014-03-26 16:36 ` Sedat Dilek
0 siblings, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2014-03-25 0:46 UTC (permalink / raw)
To: Sedat Dilek; +Cc: Al Viro, Linux Kernel Mailing List, linux-fsdevel
Just to clarify: the current vfs tree from Al works for you, no new issues?
I was delaying the release first a day, and now I think I'll just do
an rc8 after all (and do the final 3.14 next weekend), but I'd like to
be sure what the status of Al's tree is.
Al, can you send a new pull request with fixed information (assuming I
understood correctly and everything in vfs-land works for Sedat).
> P.S.: [Off-topic] With vanilla -66 kernel I have some OOPS in the
> oom[1..5] tests of LTP. Whom to adress? mm-folks?
Yes, please send to -mm (and cc lkml and me).
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2014-03-25 0:46 ` Linus Torvalds
@ 2014-03-26 16:36 ` Sedat Dilek
2014-03-26 20:55 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Sedat Dilek @ 2014-03-26 16:36 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Al Viro, Linux Kernel Mailing List, linux-fsdevel
On Tue, Mar 25, 2014 at 1:46 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> Just to clarify: the current vfs tree from Al works for you, no new issues?
>
> I was delaying the release first a day, and now I think I'll just do
> an rc8 after all (and do the final 3.14 next weekend), but I'd like to
> be sure what the status of Al's tree is.
>
> Al, can you send a new pull request with fixed information (assuming I
> understood correctly and everything in vfs-land works for Sedat).
>
Looking at [1] you did not pull-in the new changes.
Are you waiting for a new pull-request?
- Sedat -
[1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3e79d97828841305e3369ad1e07cfed5bf5989ef
>> P.S.: [Off-topic] With vanilla -66 kernel I have some OOPS in the
>> oom[1..5] tests of LTP. Whom to adress? mm-folks?
>
> Yes, please send to -mm (and cc lkml and me).
>
> Linus
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-03-26 16:36 ` Sedat Dilek
@ 2014-03-26 20:55 ` Linus Torvalds
2014-03-27 6:14 ` Sedat Dilek
2014-03-30 20:33 ` Al Viro
0 siblings, 2 replies; 188+ messages in thread
From: Linus Torvalds @ 2014-03-26 20:55 UTC (permalink / raw)
To: Sedat Dilek; +Cc: Al Viro, Linux Kernel Mailing List, linux-fsdevel
On Wed, Mar 26, 2014 at 9:36 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>
> Looking at [1] you did not pull-in the new changes.
> Are you waiting for a new pull-request?
Yeah, with the top commit updated, I'd like to make sure I get the right pull.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2014-03-26 20:55 ` Linus Torvalds
@ 2014-03-27 6:14 ` Sedat Dilek
2014-03-30 20:33 ` Al Viro
1 sibling, 0 replies; 188+ messages in thread
From: Sedat Dilek @ 2014-03-27 6:14 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Al Viro, Linux Kernel Mailing List, linux-fsdevel
On Wed, Mar 26, 2014 at 9:55 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Wed, Mar 26, 2014 at 9:36 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>
>> Looking at [1] you did not pull-in the new changes.
>> Are you waiting for a new pull-request?
>
> Yeah, with the top commit updated, I'd like to make sure I get the right pull.
>
AFAICS, it was a typo...
s/hlist_del_rcu()/hlist_del_init_rcu()
- Sedat -
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-03-26 20:55 ` Linus Torvalds
2014-03-27 6:14 ` Sedat Dilek
@ 2014-03-30 20:33 ` Al Viro
2014-03-30 20:55 ` Al Viro
1 sibling, 1 reply; 188+ messages in thread
From: Al Viro @ 2014-03-30 20:33 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Sedat Dilek, Linux Kernel Mailing List, linux-fsdevel
On Wed, Mar 26, 2014 at 01:55:51PM -0700, Linus Torvalds wrote:
> On Wed, Mar 26, 2014 at 9:36 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> >
> > Looking at [1] you did not pull-in the new changes.
> > Are you waiting for a new pull-request?
>
> Yeah, with the top commit updated, I'd like to make sure I get the right pull.
Will do in a few. Sorry about delay (and even more about the reasons for it -
the lack of sleep from redeye flight was to be expected, of course, but catching
stomach flu was not ;-/)
Al, finally back to life and digging himself from under ~5e3 mails in l-k
mailbox...
^ permalink raw reply [flat|nested] 188+ messages in thread
* Re: [git pull] vfs fixes
2014-03-30 20:33 ` Al Viro
@ 2014-03-30 20:55 ` Al Viro
2014-03-30 22:39 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2014-03-30 20:55 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Sedat Dilek, Linux Kernel Mailing List, linux-fsdevel
On Sun, Mar 30, 2014 at 09:33:07PM +0100, Al Viro wrote:
> Al, finally back to life and digging himself from under ~5e3 mails in l-k
> mailbox...
Several fixes; a couple of fdget_pos()-related ones from Eric Biggers,
prepend_name() fix (bug was reported by many people, Imre and Jan being the
ones I'd been able to find addresses of), plus a series of fixes for bug
found by Max Kellermann - missing checks for false negatives from
__lookup_mnt() in fs/namei.c + switching mnt_hash to hlist, turning
the races between __lookup_mnt() and hash modifications into
false negatives from __lookup_mnt() (instead of hangs).
Please, pull from the usual place -
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Commit ID of that branch should be 7fc5aaa083922420e2dec5d985420cb5f959b1ce;
diffs are the same as what sat there since last Sunday, commit messages
got updated a bit. Should've propagated by now...
Shortlog:
Al Viro (6):
make prepend_name() work correctly when called with negative *buflen
rcuwalk: recheck mount_lock after mountpoint crossing attempts
resizable namespace.c hashes
keep shadowed vfsmounts together
don't bother with propagate_mnt() unless the target is shared
switch mnt_hash to hlist
Eric Biggers (2):
vfs: atomic f_pos access in llseek()
vfs: Don't let __fdget_pos() get FMODE_PATH files
Diffstat:
fs/dcache.c | 4 +-
fs/file.c | 19 ++----
fs/mount.h | 4 +-
fs/namei.c | 29 ++++-----
fs/namespace.c | 177 ++++++++++++++++++++++++++++++++++++-------------------
fs/pnode.c | 26 ++++----
fs/pnode.h | 4 +-
fs/read_write.c | 4 +-
8 files changed, 155 insertions(+), 112 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2014-03-30 20:55 ` Al Viro
@ 2014-03-30 22:39 ` Linus Torvalds
2014-03-30 23:21 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2014-03-30 22:39 UTC (permalink / raw)
To: Al Viro; +Cc: Sedat Dilek, Linux Kernel Mailing List, linux-fsdevel
On Sun, Mar 30, 2014 at 1:55 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> Commit ID of that branch should be 7fc5aaa083922420e2dec5d985420cb5f959b1ce;
> diffs are the same as what sat there since last Sunday, commit messages
> got updated a bit.
Ugh. You have apparently rebased the parts that I already pulled too,
which is annoying and causes duplicate commits.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2014-03-30 22:39 ` Linus Torvalds
@ 2014-03-30 23:21 ` Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2014-03-30 23:21 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Sedat Dilek, Linux Kernel Mailing List, linux-fsdevel
On Sun, Mar 30, 2014 at 03:39:33PM -0700, Linus Torvalds wrote:
> On Sun, Mar 30, 2014 at 1:55 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > Commit ID of that branch should be 7fc5aaa083922420e2dec5d985420cb5f959b1ce;
> > diffs are the same as what sat there since last Sunday, commit messages
> > got updated a bit.
>
> Ugh. You have apparently rebased the parts that I already pulled too,
> which is annoying and causes duplicate commits.
Sorry, I'd only noticed your pull after sending that... Missing commits
on top of linux.git#master are in vfs.git#for-linus-2, so if you prefer
to grab them from there, it's
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus-2
Shortlog:
Al Viro (4):
resizable namespace.c hashes
keep shadowed vfsmounts together
don't bother with propagate_mnt() unless the target is shared
switch mnt_hash to hlist
Diffstat:
fs/mount.h | 4 +--
fs/namespace.c | 177 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------------------
fs/pnode.c | 26 +++++++++------
fs/pnode.h | 4 +--
4 files changed, 134 insertions(+), 77 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread
* [git pull] vfs fixes
@ 2013-06-22 7:16 Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2013-06-22 7:16 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
Several fixes for bugs caught while looking through f_pos (ab)users.
Please, pull from the usual place -
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (3):
mconsole: we'd better initialize pos before passing it to vfs_read()...
splice: don't pass the address of ->f_pos to methods
aout32 coredump compat fix
Diffstat:
arch/um/drivers/mconsole_kern.c | 2 +-
arch/x86/ia32/ia32_aout.c | 2 +-
fs/internal.h | 6 ++++++
fs/read_write.c | 24 ++++++++++++++++--------
fs/splice.c | 31 ++++++++++++++++++-------------
include/linux/fs.h | 2 --
include/linux/splice.h | 1 +
7 files changed, 43 insertions(+), 25 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [git pull] vfs fixes
@ 2013-03-27 0:36 Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2013-03-27 0:36 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
-stable fodder; assorted deadlock fixes. Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (3):
Don't bother with redoing rw_verify_area() from default_file_splice_from()
Nest rename_lock inside vfsmount_lock
vt: synchronize_rcu() under spinlock is not nice...
Diffstat:
drivers/tty/vt/vc_screen.c | 6 ++++--
fs/dcache.c | 16 +++++++++++-----
fs/internal.h | 5 +++++
fs/read_write.c | 25 +++++++++++++++++++++++++
fs/splice.c | 4 +++-
5 files changed, 48 insertions(+), 8 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* [git pull] vfs fixes
@ 2012-03-10 21:30 Al Viro
2012-03-10 21:49 ` Linus Torvalds
0 siblings, 1 reply; 188+ messages in thread
From: Al Viro @ 2012-03-10 21:30 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
A bunch of assorted fixes; Jan's freezing stuff still _not_
in there and neither is mm fun ;-/ Please, pull from usual place -
git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Jan Kara (2):
udf: Fix deadlock in udf_release_file()
vfs: Fix missed wakeup in I_NEW handling
Miklos Szeredi (2):
vfs: fix double put after complete_walk()
vfs: fix return value from do_last()
Tyler Hicks (1):
vfs: Correctly set the dir i_mutex lockdep class
Diffstat:
fs/inode.c | 25 +++++++++++++++++++++++--
fs/namei.c | 4 ++--
fs/udf/file.c | 2 --
include/linux/writeback.h | 5 -----
4 files changed, 25 insertions(+), 11 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2012-03-10 21:30 Al Viro
@ 2012-03-10 21:49 ` Linus Torvalds
2012-03-10 22:14 ` Al Viro
0 siblings, 1 reply; 188+ messages in thread
From: Linus Torvalds @ 2012-03-10 21:49 UTC (permalink / raw)
To: Al Viro; +Cc: linux-kernel, linux-fsdevel
On Sat, Mar 10, 2012 at 1:30 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> Jan Kara (2):
> vfs: Fix missed wakeup in I_NEW handling
Christ. This one is too ugly to live.
I'm not pulling crap like this. It's f*^&ing stupid to take a lock,
calculate a bitqueue, and just generally be an absolute ass-hat about
things for waiting for a bit that is already set 99.999% of the time.
May I suggest just reverting that commit 250df6ed instead. It added
all these insane things for no good reason. The comment said they are
going away, but if they are just multiplying in ways like this, I
really think the damn thing needs to be reverted. Any change that
causes code like this is by definition not a good change.
Linus
^ permalink raw reply [flat|nested] 188+ messages in thread* Re: [git pull] vfs fixes
2012-03-10 21:49 ` Linus Torvalds
@ 2012-03-10 22:14 ` Al Viro
0 siblings, 0 replies; 188+ messages in thread
From: Al Viro @ 2012-03-10 22:14 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel, linux-fsdevel
On Sat, Mar 10, 2012 at 01:49:21PM -0800, Linus Torvalds wrote:
> On Sat, Mar 10, 2012 at 1:30 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > Jan Kara (2):
> > ? ? ?vfs: Fix missed wakeup in I_NEW handling
>
> Christ. This one is too ugly to live.
>
> I'm not pulling crap like this. It's f*^&ing stupid to take a lock,
> calculate a bitqueue, and just generally be an absolute ass-hat about
> things for waiting for a bit that is already set 99.999% of the time.
>
> May I suggest just reverting that commit 250df6ed instead. It added
> all these insane things for no good reason. The comment said they are
> going away, but if they are just multiplying in ways like this, I
> really think the damn thing needs to be reverted. Any change that
> causes code like this is by definition not a good change.
You mean the part that removed smp_mb() on cleaning I_NEW? OK by me -
definitely saner than what this variant is doing. AFAICS, evict()
does _not_ need it - only unlock_new_inode(); in case of evict() the
change of ->i_state is separated from that wake_up_bit() by spin_unlock
followed by spin_lock and that ought to provide the barrier...
Done and pushed to the same branch;
Shortlog:
Al Viro (1):
restore smp_mb() in unlock_new_inode()
Jan Kara (1):
udf: Fix deadlock in udf_release_file()
Miklos Szeredi (2):
vfs: fix double put after complete_walk()
vfs: fix return value from do_last()
Tyler Hicks (1):
vfs: Correctly set the dir i_mutex lockdep class
Diffstat:
fs/inode.c | 4 ++--
fs/namei.c | 4 ++--
fs/udf/file.c | 2 --
3 files changed, 4 insertions(+), 6 deletions(-)
^ permalink raw reply [flat|nested] 188+ messages in thread
end of thread, other threads:[~2025-08-19 17:33 UTC | newest]
Thread overview: 188+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAHk-=wgdsv1UA+QtgiJM8KQAG7N7_9iK_edchnzZYyj+nxmfLA@mail.gmail.com>
[not found] ` <20200113195448.GT8904@ZenIV.linux.org.uk>
[not found] ` <CAHk-=whn5qk-e-KnYr6HNe5hp45v+XyDbsA2+szXvK3gC06A2w@mail.gmail.com>
2020-01-15 6:41 ` [git pull] vfs fixes Al Viro
2020-01-15 19:35 ` pr-tracker-bot
2025-08-19 12:46 [GIT PULL] " Christian Brauner
2025-08-19 17:33 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-07-25 8:54 Christian Brauner
2025-07-25 15:39 ` pr-tracker-bot
2025-07-19 10:59 Christian Brauner
2025-07-19 18:29 ` pr-tracker-bot
2025-07-04 8:36 Christian Brauner
2025-07-04 17:36 ` pr-tracker-bot
2025-06-16 8:20 Christian Brauner
2025-06-16 16:12 ` pr-tracker-bot
2025-06-02 9:02 Christian Brauner
2025-06-02 22:58 ` pr-tracker-bot
2025-05-23 10:26 Christian Brauner
2025-05-23 14:56 ` pr-tracker-bot
2025-05-12 11:01 Christian Brauner
2025-05-13 3:33 ` pr-tracker-bot
2025-04-25 21:22 Christian Brauner
2025-04-25 23:35 ` pr-tracker-bot
2025-04-19 21:04 Christian Brauner
2025-04-19 21:38 ` pr-tracker-bot
2025-04-14 10:44 Christian Brauner
2025-04-14 17:41 ` pr-tracker-bot
2025-04-02 15:46 Christian Brauner
2025-04-03 0:11 ` pr-tracker-bot
2025-03-20 15:22 Christian Brauner
2025-03-20 21:21 ` pr-tracker-bot
2025-03-13 9:13 Christian Brauner
2025-03-13 19:04 ` pr-tracker-bot
2025-03-06 10:13 Christian Brauner
2025-03-06 18:20 ` pr-tracker-bot
2025-02-25 11:51 Christian Brauner
2025-02-25 17:52 ` pr-tracker-bot
2025-02-17 10:37 Christian Brauner
2025-02-17 18:44 ` pr-tracker-bot
2025-02-07 10:52 Christian Brauner
2025-02-07 22:25 ` pr-tracker-bot
2025-01-10 15:16 Christian Brauner
2025-01-10 18:12 ` pr-tracker-bot
2025-01-06 15:32 Christian Brauner
2025-01-06 18:40 ` pr-tracker-bot
2024-11-27 15:41 Christian Brauner
2024-11-27 16:14 ` Linus Torvalds
2024-11-27 16:15 ` pr-tracker-bot
2024-11-01 12:43 Christian Brauner
2024-11-01 17:48 ` pr-tracker-bot
2024-10-21 11:46 Christian Brauner
2024-10-21 18:27 ` pr-tracker-bot
2024-10-03 9:00 Christian Brauner
2024-10-03 16:53 ` pr-tracker-bot
2024-09-30 13:46 Christian Brauner
2024-09-30 20:21 ` pr-tracker-bot
2024-09-04 12:03 Christian Brauner
2024-09-04 16:46 ` pr-tracker-bot
2024-08-26 15:25 Christian Brauner
2024-08-27 5:04 ` pr-tracker-bot
2024-08-14 13:29 Christian Brauner
2024-08-14 16:28 ` pr-tracker-bot
2024-07-27 9:05 Christian Brauner
2024-07-27 22:37 ` pr-tracker-bot
2024-07-24 9:19 Christian Brauner
2024-07-24 17:19 ` pr-tracker-bot
2024-07-18 9:01 Christian Brauner
2024-07-19 1:04 ` pr-tracker-bot
2024-07-11 5:09 Christian Brauner
2024-07-11 19:24 ` pr-tracker-bot
2024-07-02 19:44 Christian Brauner
2024-07-02 20:56 ` pr-tracker-bot
2024-07-01 11:53 Christian Brauner
2024-07-01 16:49 ` pr-tracker-bot
2024-06-10 14:09 Christian Brauner
2024-06-11 19:15 ` Linus Torvalds
2024-06-12 11:30 ` Christian Brauner
2024-06-11 23:42 ` pr-tracker-bot
2024-05-27 11:55 Christian Brauner
2024-05-27 15:30 ` pr-tracker-bot
2024-04-26 14:59 Christian Brauner
2024-04-26 18:09 ` pr-tracker-bot
2024-04-05 11:22 Christian Brauner
2024-04-05 17:09 ` pr-tracker-bot
2024-03-18 12:19 Christian Brauner
2024-03-18 16:48 ` pr-tracker-bot
2024-03-18 19:14 ` Linus Torvalds
2024-03-18 19:41 ` Linus Torvalds
2024-03-19 6:58 ` Christian Brauner
2024-03-20 10:21 ` Christian Brauner
2024-03-06 15:45 Christian Brauner
2024-03-06 16:33 ` pr-tracker-bot
2024-03-01 12:45 Christian Brauner
2024-03-01 20:37 ` pr-tracker-bot
2024-02-22 14:03 Christian Brauner
2024-02-22 18:18 ` pr-tracker-bot
2024-02-12 13:00 Christian Brauner
2024-02-12 17:03 ` pr-tracker-bot
2024-01-13 12:31 Christian Brauner
2024-01-17 20:03 ` pr-tracker-bot
2023-11-24 10:27 Christian Brauner
2023-11-24 18:25 ` Linus Torvalds
2023-11-24 18:52 ` Linus Torvalds
2023-11-24 20:12 ` Linus Torvalds
2023-11-25 13:05 ` Christian Brauner
2023-11-25 13:10 ` Christian Brauner
2023-11-25 13:28 ` Omar Sandoval
2023-11-25 14:04 ` Christian Brauner
2023-11-24 18:26 ` pr-tracker-bot
2023-10-19 10:07 Christian Brauner
2023-10-19 16:37 ` Linus Torvalds
2023-10-20 11:14 ` Christian Brauner
2023-10-19 18:36 ` pr-tracker-bot
2023-09-26 10:39 Christian Brauner
2023-09-26 16:14 ` pr-tracker-bot
2023-07-06 11:52 Christian Brauner
2023-07-07 2:27 ` pr-tracker-bot
2023-07-02 11:28 Christian Brauner
2023-07-02 18:53 ` pr-tracker-bot
2023-05-25 12:22 Christian Brauner
2023-05-25 18:18 ` pr-tracker-bot
2023-05-12 15:31 Christian Brauner
2023-05-12 22:14 ` pr-tracker-bot
2023-04-03 11:04 Christian Brauner
2023-04-03 16:51 ` pr-tracker-bot
2023-03-12 12:18 Christian Brauner
2023-03-12 16:20 ` pr-tracker-bot
2020-09-22 21:29 [git pull] " Al Viro
2020-09-22 22:15 ` pr-tracker-bot
2018-07-01 12:31 Al Viro
2018-07-01 19:36 ` Linus Torvalds
2018-07-01 20:05 ` Al Viro
2018-07-01 20:25 ` Linus Torvalds
2018-04-20 15:58 Al Viro
2018-04-20 18:29 ` Andrew Morton
2018-04-20 19:09 ` Al Viro
2018-04-20 19:57 ` Andrew Morton
2017-06-17 2:56 Al Viro
2017-04-09 5:40 Al Viro
2017-04-11 6:10 ` Linus Torvalds
2017-04-11 6:48 ` Al Viro
2017-04-11 21:02 ` Andreas Dilger
2017-04-12 7:00 ` Linus Torvalds
2017-04-15 6:41 ` Vegard Nossum
2017-04-15 16:51 ` Linus Torvalds
2017-04-15 17:08 ` Al Viro
2017-04-02 17:01 Al Viro
2017-04-02 23:59 ` Linus Torvalds
2017-04-03 0:10 ` Linus Torvalds
2017-04-03 0:30 ` Al Viro
2017-04-03 0:43 ` Al Viro
2017-04-03 0:58 ` Linus Torvalds
2017-04-03 2:21 ` Al Viro
2017-04-03 6:00 ` Eric W. Biederman
2017-04-03 7:46 ` Al Viro
2017-04-04 0:22 ` Ian Kent
2017-04-04 0:47 ` Ian Kent
2017-04-03 0:20 ` Al Viro
2016-06-17 20:50 Q. hlist_bl_add_head_rcu() in d_alloc_parallel() J. R. Okajima
2016-06-17 22:16 ` Al Viro
2016-06-19 5:24 ` J. R. Okajima
2016-06-19 16:55 ` Al Viro
2016-06-20 4:34 ` J. R. Okajima
2016-06-20 5:35 ` Al Viro
2016-06-20 14:51 ` Al Viro
2016-06-20 17:14 ` [git pull] vfs fixes Al Viro
2016-06-08 2:12 Al Viro
2016-05-28 0:10 Al Viro
2016-02-28 1:09 Al Viro
2014-09-14 19:47 Al Viro
2014-09-26 20:38 ` Joachim Eastwood
2014-09-26 20:46 ` Joachim Eastwood
2014-09-26 20:58 ` Al Viro
2014-09-26 21:28 ` Joachim Eastwood
2014-09-26 21:52 ` Joachim Eastwood
2014-03-24 22:58 Imre Deak
2014-03-25 7:21 ` Sedat Dilek
2014-03-23 7:16 Al Viro
2014-03-23 10:57 ` Sedat Dilek
2014-03-23 15:35 ` Al Viro
2014-03-23 16:56 ` Al Viro
2014-03-23 16:36 ` Linus Torvalds
2014-03-23 16:45 ` Al Viro
2014-03-23 17:01 ` Linus Torvalds
2014-03-24 8:52 ` Sedat Dilek
2014-03-25 0:46 ` Linus Torvalds
2014-03-26 16:36 ` Sedat Dilek
2014-03-26 20:55 ` Linus Torvalds
2014-03-27 6:14 ` Sedat Dilek
2014-03-30 20:33 ` Al Viro
2014-03-30 20:55 ` Al Viro
2014-03-30 22:39 ` Linus Torvalds
2014-03-30 23:21 ` Al Viro
2013-06-22 7:16 Al Viro
2013-03-27 0:36 Al Viro
2012-03-10 21:30 Al Viro
2012-03-10 21:49 ` Linus Torvalds
2012-03-10 22:14 ` Al Viro
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).