From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] Driver core fixes for 5.0-rc6
Date: Fri, 8 Feb 2019 09:39:04 +0100 [thread overview]
Message-ID: <20190208083904.GA27008@kroah.com> (raw)
The following changes since commit 1c7fc5cbc33980acd13d668f1c8f0313d6ae9fd8:
Linux 5.0-rc2 (2019-01-14 10:41:12 +1200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-5.0-rc6
for you to fetch changes up to 36991ca68db9dd43bac7f3519f080ee3939263ef:
blk-mq: protect debugfs_create_files() from failures (2019-01-31 14:07:59 +0100)
----------------------------------------------------------------
Driver core fixes for 5.0-rc6
Here are some driver core fixes for 5.0-rc6.
Well, not so much "driver core" as "debugfs". There's a lot of
outstanding debugfs cleanup patches coming in through different
subsystem trees, and in that process the debugfs core was found that it
really should return errors when something bad happens, to prevent
random files from showing up in the root of debugfs afterward. So
debugfs was fixed up to handle this properly, and then two fixes for
the relay and blk-mq code was needed as it was making invalid
assumptions about debugfs return values.
There's also a cacheinfo fix in here that resolves a tiny issue.
All of these have been in linux-next for over a week with no reported
problems.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Greg Kroah-Hartman (5):
debugfs: fix debugfs_rename parameter checking
debugfs: return error values, not NULL
debugfs: debugfs_lookup() should return NULL if not found
relay: check return of create_buf_file() properly
blk-mq: protect debugfs_create_files() from failures
Huacai Chen (1):
cacheinfo: Keep the old value if of_property_read_u32 fails
block/blk-mq-debugfs.c | 3 +++
drivers/base/cacheinfo.c | 6 ++----
fs/debugfs/inode.c | 36 ++++++++++++++++++++++++------------
kernel/relay.c | 4 +++-
4 files changed, 32 insertions(+), 17 deletions(-)
next reply other threads:[~2019-02-08 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 8:39 Greg KH [this message]
2019-02-08 19:45 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190208083904.GA27008@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®