Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date:   Sun, 12 Mar 2023 11:38:31 +0100
Message-Id: <CR4C8V5T7751.HT9WYT9LB7X1@vincent-arch>
From:   "Vincenzo Palazzo" <vincenzopalazzodev@gmail.com>
To:     "Ivan Orlov" <ivan.orlov0322@gmail.com>,
        "David Kahurani" <k.kahurani@gmail.com>
Cc:     <lucho@ionkov.net>, <ericvh@gmail.com>, <asmadeus@codewreck.org>,
        <linux_oss@crudebyte.com>, <linux-kernel@vger.kernel.org>,
        <syzbot+cb1d16facb3cc90de5fb@syzkaller.appspotmail.com>,
        <v9fs-developer@lists.sourceforge.net>,
        <linux-kernel-mentees@lists.linuxfoundation.org>
Subject: Re: [PATCH] 9P FS: Fix wild-memory-access write in v9fs_get_acl
References: <20230310202619.433269-1-ivan.orlov0322@gmail.com>
 <CAAZOf24yhpSBd1926v7T=qDwqvFfLsWMJeMKTafeZ=69hJ4rdw@mail.gmail.com>
 <d5bb5ff0-1102-c7cd-c21b-c3a7f4f31717@gmail.com>
In-Reply-To: <d5bb5ff0-1102-c7cd-c21b-c3a7f4f31717@gmail.com>
Precedence: bulk

On Sat Mar 11, 2023 at 6:35 PM CET, Ivan Orlov wrote:
>
> > I'm not sure what are the rules around here but I prefer to use bracket=
s=20
> > more generously.
>
> I think in this particular case they can just make the code less=20
> readable (considering they will not change the behavior in any way).=20
> However, this is eternal discussion and I saw examples of both in the=20
> kernel sources.
Maybe this can be a good reading [1], I think it is more a kernel rule?

[1] https://www.kernel.org/doc/html/latest/process/coding-style.html

Cheers

Vincent.

> _______________________________________________
> Linux-kernel-mentees mailing list
> Linux-kernel-mentees@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees