linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Tetsuhiro Kohada'" <kohada.t2@gmail.com>
Cc: <kohada.tetsuhiro@dc.mitsubishielectric.co.jp>,
	<mori.takahiro@ab.mitsubishielectric.co.jp>,
	"'Sungjong Seo'" <sj1557.seo@samsung.com>,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 2/2] exfat: aggregate dir-entry updates into __exfat_write_inode().
Date: Fri, 16 Oct 2020 16:57:05 +0900	[thread overview]
Message-ID: <018b01d6a391$f06fc310$d14f4930$@samsung.com> (raw)
In-Reply-To: <20201002060528.27519-1-kohada.t2@gmail.com>

> *inode)  static int exfat_map_cluster(struct inode *inode, unsigned int clu_offset,
>  		unsigned int *clu, int create)
>  {
> -	int ret, modified = false;
> +	int ret;
>  	unsigned int last_clu;
>  	struct exfat_chain new_clu;
>  	struct super_block *sb = inode->i_sb;
> @@ -184,6 +185,11 @@ static int exfat_map_cluster(struct inode *inode, unsigned int clu_offset,
>  			return -EIO;
>  		}
> 
> +		exfat_warn(sb, "alloc[%lu]@map: %lld (%d - %08x)",
> +			   inode->i_ino, i_size_read(inode),
> +			   (clu_offset << sbi->sect_per_clus_bits) * 512,
> +			   last_clu);
Is this leftover print from debugging?


  reply	other threads:[~2020-10-16  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20201002060539epcas1p4efa16130724ad15a3f105f62dd78d018@epcas1p4.samsung.com>
2020-10-02  6:05 ` [PATCH v3 2/2] exfat: aggregate dir-entry updates into __exfat_write_inode() Tetsuhiro Kohada
2020-10-16  7:57   ` Namjae Jeon [this message]
2020-10-19  0:47     ` Tetsuhiro Kohada

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='018b01d6a391$f06fc310$d14f4930$@samsung.com' \
    --to=namjae.jeon@samsung.com \
    --cc=kohada.t2@gmail.com \
    --cc=kohada.tetsuhiro@dc.mitsubishielectric.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mori.takahiro@ab.mitsubishielectric.co.jp \
    --cc=sj1557.seo@samsung.com \
    /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).