From: Pavel Skripkin <paskripkin@gmail.com>
To: dhowells@redhat.com, viro@zeniv.linux.org.uk, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH] sysv: use BUILD_BUG_ON instead of runtime check
Date: Mon, 27 Sep 2021 15:12:42 +0300 [thread overview]
Message-ID: <787abb01-f8c0-6ddf-baee-90b8e558914a@gmail.com> (raw)
In-Reply-To: <dc7771f0-e4db-ee5c-a66d-b5db5f26a59d@gmail.com>
On 9/1/21 13:15, Pavel Skripkin wrote:
> On 8/13/21 15:30, Pavel Skripkin wrote:
>> There was runtime checks about sizes of struct v7_super_block
>> and struct sysv_inode. If one of these checks fail kernel will panic.
>> Since these values are known on complite time let's use BUILD_BUG_ON(),
>> because it's standard mechanism for validation checking at build time
>>
>> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>> Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
>> ---
>> fs/sysv/super.c | 6 ++----
>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/fs/sysv/super.c b/fs/sysv/super.c
>> index cc8e2ed155c8..d1def0771a40 100644
>> --- a/fs/sysv/super.c
>> +++ b/fs/sysv/super.c
>> @@ -474,10 +474,8 @@ static int v7_fill_super(struct super_block *sb, void *data, int silent)
>> struct sysv_sb_info *sbi;
>> struct buffer_head *bh;
>>
>> - if (440 != sizeof (struct v7_super_block))
>> - panic("V7 FS: bad super-block size");
>> - if (64 != sizeof (struct sysv_inode))
>> - panic("sysv fs: bad i-node size");
>> + BUILD_BUG_ON(sizeof(struct v7_super_block) != 440);
>> + BUILD_BUG_ON(sizeof(struct sysv_inode) != 64);
>>
>> sbi = kzalloc(sizeof(struct sysv_sb_info), GFP_KERNEL);
>> if (!sbi)
>>
>
> Hi, David and Alexander!
>
>
> Maybe, this one can go through one of your trees? I didn't find any sysv
> related trees, so..
>
> Lore link to the patch:
> https://lore.kernel.org/lkml/20210813123020.22971-1-paskripkin@gmail.com/
>
>
>
> Thank you!
Hi, Andrew,
Maybe this one can go through your tree?
With regards,
Pavel Skripkin
prev parent reply other threads:[~2021-09-27 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 12:30 Pavel Skripkin
2021-09-01 10:15 ` Pavel Skripkin
2021-09-27 12:12 ` Pavel Skripkin [this message]
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=787abb01-f8c0-6ddf-baee-90b8e558914a@gmail.com \
--to=paskripkin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®