mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Cc: Eric Biggers <ebiggers@google.com>
Subject: Re: [f2fs-dev] [PATCH 4/6] f2fs: fix the f2fs_file_write_iter tracepoint
Date: Thu, 2 Dec 2021 10:59:09 +0800	[thread overview]
Message-ID: <f1c6e1f5-e2c7-a704-9a3d-5012ba3e9be2@kernel.org> (raw)
In-Reply-To: <20211116214510.2934905-4-jaegeuk@kernel.org>

On 2021/11/17 5:45, Jaegeuk Kim wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> Pass in the original position and count rather than the position and
> count that were updated by the write.  Also use the correct types for
> all arguments, in particular the file offset which was being truncated
> to 32 bits on 32-bit platforms.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,

  reply	other threads:[~2021-12-02  2:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 21:45 [PATCH 1/6] f2fs: rework write preallocations Jaegeuk Kim
2021-11-16 21:45 ` [PATCH 2/6] f2fs: do not expose unwritten blocks to user by DIO Jaegeuk Kim
2021-11-17 15:16   ` [f2fs-dev] " Chao Yu
2021-11-17 19:32     ` Jaegeuk Kim
2021-11-23  6:59   ` [f2fs] e029ce2460: aim7.jobs-per-min -35.8% regression kernel test robot
2021-12-02  2:39   ` [f2fs-dev] [PATCH 2/6] f2fs: do not expose unwritten blocks to user by DIO Chao Yu
2021-12-02 18:13     ` Jaegeuk Kim
2021-12-03  6:43       ` Chao Yu
2021-12-03 22:53         ` Jaegeuk Kim
2021-12-04 19:01     ` [f2fs-dev] [PATCH 2/6 v2] " Jaegeuk Kim
2021-11-16 21:45 ` [PATCH 3/6] f2fs: reduce indentation in f2fs_file_write_iter() Jaegeuk Kim
2021-12-02  2:58   ` [f2fs-dev] " Chao Yu
2021-11-16 21:45 ` [PATCH 4/6] f2fs: fix the f2fs_file_write_iter tracepoint Jaegeuk Kim
2021-12-02  2:59   ` Chao Yu [this message]
2021-11-16 21:45 ` [PATCH 5/6] f2fs: implement iomap operations Jaegeuk Kim
2021-12-02  3:10   ` [f2fs-dev] " Chao Yu
2021-12-02  4:15     ` Eric Biggers
2021-12-02 14:04       ` Chao Yu
2021-12-02 18:25         ` Eric Biggers
2021-12-02 18:57           ` Jaegeuk Kim
2021-12-02 19:00             ` Jaegeuk Kim
2021-12-02 20:57               ` Eric Biggers
2021-12-02 21:19                 ` Jaegeuk Kim
2021-12-02 21:28                   ` Jaegeuk Kim
2021-12-03  6:51                     ` Chao Yu
2021-12-30  6:43                     ` Chao Yu
2022-01-04 21:15                       ` Jaegeuk Kim
2021-11-16 21:45 ` [PATCH 6/6] f2fs: use iomap for direct I/O Jaegeuk Kim
2021-12-10 23:58   ` Jaegeuk Kim
2021-11-17 13:31 ` [f2fs-dev] [PATCH 1/6] f2fs: rework write preallocations Chao Yu
2021-11-17 19:27   ` Jaegeuk Kim
2021-11-18  6:47     ` Chao Yu

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=f1c6e1f5-e2c7-a704-9a3d-5012ba3e9be2@kernel.org \
    --to=chao@kernel.org \
    --cc=ebiggers@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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
Powered by JetHome