From: John Groves <John@Groves.net>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Cc: John Groves <John@Groves.net>, John Groves <jgroves@micron.com>,
john@jagalactic.com, John Groves <john@groves.net>
Subject: [PATCH 0/1] sget_dev() minor bug fix
Date: Tue, 9 Apr 2024 18:31:30 -0500 [thread overview]
Message-ID: <cover.1712704849.git.john@groves.net> (raw)
I found this small mess while working on applying Christian Brauner's
very helpful suggestions for get_tree() handling in famfs (for which
v2 is coming soon).
John Groves (1):
sget_dev() bug fix: dev_t passed by value but stored via stack address
fs/super.c | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
base-commit: fec50db7033ea478773b159e0e2efb135270e3b7
--
2.43.0
next reply other threads:[~2024-04-09 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 23:31 John Groves [this message]
2024-04-09 23:31 ` [PATCH 1/1] sget_dev() bug fix: dev_t passed by value but stored via stack address John Groves
2024-04-10 9:18 ` kernel test robot
2024-04-10 10:16 ` Christian Brauner
2024-04-10 13:38 ` John Groves
2024-04-10 15:23 ` Christian Brauner
2024-04-10 21:24 ` John Groves
2024-04-17 5:06 ` kernel test robot
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=cover.1712704849.git.john@groves.net \
--to=john@groves.net \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jgroves@micron.com \
--cc=john@jagalactic.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).