From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 013EEC77B73 for ; Tue, 2 May 2023 15:32:43 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 81FCB6B009B; Tue, 2 May 2023 11:32:43 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 7C3576B009C; Tue, 2 May 2023 11:32:43 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 6B30E6B009D; Tue, 2 May 2023 11:32:43 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from mail-ed1-f46.google.com (mail-ed1-f46.google.com [209.85.208.46]) by kanga.kvack.org (Postfix) with ESMTP id 16BB36B009B for ; Tue, 2 May 2023 11:32:43 -0400 (EDT) Received: by mail-ed1-f46.google.com with SMTP id 4fb4d7f45d1cf-50bc3a5f462so4802a12.1 for ; Tue, 02 May 2023 08:32:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1683041562; x=1685633562; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=9RYJXTMkjo99MefNou3S1yVA+HChQgATz9a2fAIHiP8=; b=FX/WMECV6QjQv7Oc2a03MwclFFLtaQtfrBU83sNAG5/NovOV31sz8ix9MFBv6Je1T3 RIGPKJoCuKEhOrrrLJjq0+EW6R/OJfGHDqXuH+kqMvRHW+t0pNLUr/RDohVS0v7ohMiL uzhGFRX79QHUnjPxU5YalxfkxnRJ/pyfP5L/cggfHe2HJA2QjB/PagqIHIQABJCqFUgW 1weitJLKGmmyhwMV7shTyQN0zyYw0TQU38bPeswvBiKoRTM6jcTr5wK/WKzGvuqiU2yW kOZr+mp3Zk0f2unrV8p+nkNKWsRsjli/4reV5zhSGlbSDYScfGJnIFEvIRwo6hFYY0Kc UNHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683041562; x=1685633562; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=9RYJXTMkjo99MefNou3S1yVA+HChQgATz9a2fAIHiP8=; b=Hqq1cKOvYLJ1qklMh9Y4S2Au9eoD+Bp99YTDQ3kRxRDab2u1+f1UMnPiehn4PCid0I WLnRQo+DifXpWpwJ4AaFeUbbJRCWGkpNDTObq4ODtWfxXjxE2A4OAGR7oeohKJRPT+RW rNyjjAjocZnaWIQeaDjtOBF8XQrvmFTxWJx9NMRuIMd6cQcVnYo+qXXY+vsgxl3CO31l 2aUGKX0jA+Bmv51begHNsu4hsWPgc+yluKWq+KLgfB9dEe+9uT3xqDhd0967RohYcRMf 1oIxoZAjtZaV1vep0iCRvIR0PPIpSf2UQjmLrP/Fwb/fY3uwNYdjg0ih03S19+BaG9qC Am9g== X-Gm-Message-State: AC+VfDz1XKKjeLIMVaVs6LS+RyBmEbkTW7cExVn9Sg20zR99v0GrtY3G pHcu/bLf8yWCVIantGpq1TCzsZuTjvu1nRqYekfoEi3vgrK/c91Yab8kWw== X-Google-Smtp-Source: ACHHUZ7q2XyFfQBq2zl1Oop/t0Vfx9oeA1lce6FEy5SaCdIxYMRSYq/PIxn3sg1WawZ0EpFcNf6c5Xk6XkJvWSinwWY= X-Received: by 2002:a05:6512:239a:b0:4ed:b131:3449 with SMTP id c26-20020a056512239a00b004edb1313449mr99041lfv.7.1683008005115; Mon, 01 May 2023 23:13:25 -0700 (PDT) MIME-Version: 1.0 References: <0000000000007337c705fa1060e2@google.com> In-Reply-To: From: Dmitry Vyukov Date: Tue, 2 May 2023 08:13:11 +0200 Message-ID: Subject: Re: [syzbot] [mm?] KCSAN: data-race in generic_fillattr / shmem_mknod (2) To: Tetsuo Handa Cc: linux-fsdevel , Alexander Viro , akpm@linux-foundation.org, hughd@google.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, syzbot Content-Type: text/plain; charset="UTF-8" X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, 1 May 2023 at 07:16, Tetsuo Handa wrote: > > On 2023/04/24 17:26, Dmitry Vyukov wrote: > >> HEAD commit: 457391b03803 Linux 6.3 > >> git tree: upstream > >> console output: https://syzkaller.appspot.com/x/log.txt?x=13226cf0280000 > >> kernel config: https://syzkaller.appspot.com/x/.config?x=8c81c9a3d360ebcf > >> dashboard link: https://syzkaller.appspot.com/bug?extid=702361cf7e3d95758761 > >> compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 > > > > I think shmem_mknod() needs to use i_size_write() to update the size. > > Writes to i_size are not assumed to be atomic throughout the kernel > > code. > > > > I don't think that using i_size_{read,write}() alone is sufficient, > for I think that i_size_{read,write}() needs data_race() annotation. Agree. Or better proper READ/WRITE_ONCE. data_race() is just an annotation, it does not fix the actual data race bug that is present there. I see there are lots of uses of i_size_read() in complex scenarios that involve comparisons of the size. All such racy uses are subject to the TOCTOU bug at least. > include/linux/fs.h | 13 +++++++++++-- > mm/shmem.c | 12 ++++++------ > 2 files changed, 17 insertions(+), 8 deletions(-) > > diff --git a/include/linux/fs.h b/include/linux/fs.h > index 21a981680856..0d067bbe3ee9 100644 > --- a/include/linux/fs.h > +++ b/include/linux/fs.h > @@ -860,6 +860,13 @@ void filemap_invalidate_unlock_two(struct address_space *mapping1, > * the read or for example on x86 they can be still implemented as a > * cmpxchg8b without the need of the lock prefix). For SMP compiles > * and 64bit archs it makes no difference if preempt is enabled or not. > + * > + * However, when KCSAN is enabled, CPU being capable of reading/updating > + * naturally aligned 8 bytes of memory atomically is not sufficient for > + * avoiding KCSAN warning, for KCSAN checks whether value has changed between > + * before and after of a read operation. But since we don't want to introduce > + * seqcount overhead only for suppressing KCSAN warning, tell KCSAN that data > + * race on accessing i_size field is acceptable. > */ > static inline loff_t i_size_read(const struct inode *inode) > { > @@ -880,7 +887,8 @@ static inline loff_t i_size_read(const struct inode *inode) > preempt_enable(); > return i_size; > #else > - return inode->i_size; > + /* See comment above. */ > + return data_race(inode->i_size); > #endif > } > > @@ -902,7 +910,8 @@ static inline void i_size_write(struct inode *inode, loff_t i_size) > inode->i_size = i_size; > preempt_enable(); > #else > - inode->i_size = i_size; > + /* See comment above. */ > + data_race(inode->i_size = i_size); > #endif > } > > diff --git a/mm/shmem.c b/mm/shmem.c > index e40a08c5c6d7..a2f20297fb59 100644 > --- a/mm/shmem.c > +++ b/mm/shmem.c > @@ -2951,7 +2951,7 @@ shmem_mknod(struct mnt_idmap *idmap, struct inode *dir, > goto out_iput; > > error = 0; > - dir->i_size += BOGO_DIRENT_SIZE; > + i_size_write(dir, i_size_read(dir) + BOGO_DIRENT_SIZE); > dir->i_ctime = dir->i_mtime = current_time(dir); > inode_inc_iversion(dir); > d_instantiate(dentry, inode); > @@ -3027,7 +3027,7 @@ static int shmem_link(struct dentry *old_dentry, struct inode *dir, struct dentr > goto out; > } > > - dir->i_size += BOGO_DIRENT_SIZE; > + i_size_write(dir, i_size_read(dir) + BOGO_DIRENT_SIZE); > inode->i_ctime = dir->i_ctime = dir->i_mtime = current_time(inode); > inode_inc_iversion(dir); > inc_nlink(inode); > @@ -3045,7 +3045,7 @@ static int shmem_unlink(struct inode *dir, struct dentry *dentry) > if (inode->i_nlink > 1 && !S_ISDIR(inode->i_mode)) > shmem_free_inode(inode->i_sb); > > - dir->i_size -= BOGO_DIRENT_SIZE; > + i_size_write(dir, i_size_read(dir) - BOGO_DIRENT_SIZE); > inode->i_ctime = dir->i_ctime = dir->i_mtime = current_time(inode); > inode_inc_iversion(dir); > drop_nlink(inode); > @@ -3132,8 +3132,8 @@ static int shmem_rename2(struct mnt_idmap *idmap, > inc_nlink(new_dir); > } > > - old_dir->i_size -= BOGO_DIRENT_SIZE; > - new_dir->i_size += BOGO_DIRENT_SIZE; > + i_size_write(old_dir, i_size_read(old_dir) - BOGO_DIRENT_SIZE); > + i_size_write(new_dir, i_size_read(new_dir) + BOGO_DIRENT_SIZE); > old_dir->i_ctime = old_dir->i_mtime = > new_dir->i_ctime = new_dir->i_mtime = > inode->i_ctime = current_time(old_dir); > @@ -3189,7 +3189,7 @@ static int shmem_symlink(struct mnt_idmap *idmap, struct inode *dir, > folio_unlock(folio); > folio_put(folio); > } > - dir->i_size += BOGO_DIRENT_SIZE; > + i_size_write(dir, i_size_read(dir) + BOGO_DIRENT_SIZE); > dir->i_ctime = dir->i_mtime = current_time(dir); > inode_inc_iversion(dir); > d_instantiate(dentry, inode); > > Maybe we want i_size_add() ? > > Also, there was a similar report on updating i_{ctime,mtime} to current_time() > which means that i_size is not the only field that is causing data race. > https://syzkaller.appspot.com/bug?id=067d40ab9ab23a6fa0a8156857ed54e295062a29 > > Hmm, where is the serialization that avoids concurrent > shmem_mknod()/shmem_mknod() or shmem_mknod()/shmem_unlink() ? > i_size_write() says "need locking around it (normally i_mutex)"... >