From: Ritesh Harjani <ritesh.list@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Jan Kara <jack@suse.com>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [RFC 1/3] jbd2: Drop useless return value of submit_bh
Date: Mon, 18 Jul 2022 23:25:46 +0530 [thread overview]
Message-ID: <20220718175546.zqrtnsuf72dgpexn@riteshh-domain> (raw)
In-Reply-To: <20220704090144.hdj3fpaaqyj35yt3@riteshh-domain>
On 22/07/04 02:31PM, Ritesh Harjani wrote:
> On 22/06/21 02:39AM, Matthew Wilcox wrote:
> > On Mon, Jun 20, 2022 at 11:28:40AM +0530, Ritesh Harjani wrote:
> > > @@ -1636,14 +1636,12 @@ static int jbd2_write_superblock(journal_t *journal, int write_flags)
> > > sb->s_checksum = jbd2_superblock_csum(journal, sb);
> > > get_bh(bh);
> > > bh->b_end_io = end_buffer_write_sync;
> > > - ret = submit_bh(REQ_OP_WRITE, write_flags, bh);
> > > + submit_bh(REQ_OP_WRITE, write_flags, bh);
> > > wait_on_buffer(bh);
> > > if (buffer_write_io_error(bh)) {
> > > clear_buffer_write_io_error(bh);
> > > set_buffer_uptodate(bh);
> > > ret = -EIO;
> > > - }
> > > - if (ret) {
> > > printk(KERN_ERR "JBD2: Error %d detected when updating "
> > > "journal superblock for %s.\n", ret,
> > > journal->j_devname);
> >
> > Maybe rephrase the error message? And join it together to match the
> > current preferred style.
> >
> > printk(KERN_ERR "JBD2: I/O error when updating journal superblock for %s.\n",
> > journal->j_devname);
>
> Sure, I will update the printk message like above and send out a v3
> (since I haven't receieved any other comments so I think v3 should be good to be
> picked up now)
We were planning to send this patch series via ext4 tree.
But it seems this might conflict with the below mentioned patches sitting in
linux-next. So let me rebase my patches on top of these and maybe hold to this
series until the current set of changes land in linux tree to avoid any merge
conflicts later.
But either ways do let me know if you would like to take any other preferred
route. Since this is not critical, so I am fine with either ways you suggest.
-ritesh
author Bart Van Assche <bvanassche@acm.org> Thu Jul 14 11:07:13 2022 -0700
fs/buffer: Combine two submit_bh() and ll_rw_block() arguments
Both submit_bh() and ll_rw_block() accept a request operation type and
request flags as their first two arguments. Micro-optimize these two
functions by combining these first two arguments into a single argument.
This patch does not change the behavior of any of the modified code.
next prev parent reply other threads:[~2022-07-18 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 5:58 [RFC 0/3] submit_bh: Drop unnecessary return values and API users Ritesh Harjani
2022-06-20 5:58 ` [RFC 1/3] jbd2: Drop useless return value of submit_bh Ritesh Harjani
2022-06-20 6:39 ` Christoph Hellwig
2022-06-20 9:39 ` Jan Kara
2022-06-21 1:39 ` Matthew Wilcox
2022-07-04 9:01 ` Ritesh Harjani
2022-07-18 17:55 ` Ritesh Harjani [this message]
2022-06-20 5:58 ` [RFC 2/3] fs/buffer: " Ritesh Harjani
2022-06-20 6:39 ` Christoph Hellwig
2022-06-20 9:40 ` Jan Kara
2022-06-20 5:58 ` [RFC 3/3] fs/buffer: Make submit_bh & submit_bh_wbc return type as void Ritesh Harjani
2022-06-20 6:40 ` Christoph Hellwig
2022-06-20 9:41 ` Jan Kara
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=20220718175546.zqrtnsuf72dgpexn@riteshh-domain \
--to=ritesh.list@gmail.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--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