Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1229661 > unrolled thread

Re: Possible Bug in move_encrypted_block

Started byJaegeuk Kim <jaegeuk@kernel.org>
First post2015-09-21 21:00 +0200
Last post2015-09-21 21:00 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Possible Bug in move_encrypted_block Jaegeuk Kim <jaegeuk@kernel.org> - 2015-09-21 21:00 +0200

#1229661 — Re: Possible Bug in move_encrypted_block

FromJaegeuk Kim <jaegeuk@kernel.org>
Date2015-09-21 21:00 +0200
SubjectRe: Possible Bug in move_encrypted_block
Message-ID<qbetI-6Kf-35@gated-at.bofh.it>
Hi,

On Sat, Sep 19, 2015 at 01:36:08PM -0400, nick wrote:
> Greetings Jaeguek and others.
> Below are the lines fora possible bug in  move_encrypted_block:
> err = get_dnode_of_data(&dn, bidx, LOOKUP_NODE);
>         if (err)
>                 goto out;
> Also calls of get_dnode_of_data need to hold the semaphone for the superblock
> this call is being done on to avoid concurrent access on data being received

IIUC, the f2fs_lock_op() is not neeeded here. Do you mean this?
To be honest, I can't catch your point.

Thanks,

> here from the superblock and file system on disk. In addition unless I get a
> reply to this I will not be sending in a bug fix for this.
> Nick
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web