From: "Shirish Pargaonkar" <shirishpargaonkar@gmail.com>
To: "Steve French" <smfrench@gmail.com>
Cc: "Harvey Harrison" <harvey.harrison@gmail.com>,
"Jeff Layton" <jlayton@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: cifs: suggestions for a few more sparse warnings
Date: Thu, 24 Jul 2008 08:43:11 -0500 [thread overview]
Message-ID: <4a4634330807240643j6eb3314am343efe6c37992b50@mail.gmail.com> (raw)
In-Reply-To: <524f69650807231839g399f57a8ied548d81eefdbebd@mail.gmail.com>
Steve,
On Wed, Jul 23, 2008 at 8:39 PM, Steve French <smfrench@gmail.com> wrote:
> On Wed, Jul 23, 2008 at 7:55 PM, Harvey Harrison
> <harvey.harrison@gmail.com> wrote:
>> Here's a patch for some of the other warnings, but the cifsacl.c bit
>> needs a comment I think.
>>
>> Harvey
>>
>> diff --git a/fs/cifs/cifsacl.c b/fs/cifs/cifsacl.c
>> index 34902cf..70f0ef5 100644
>> --- a/fs/cifs/cifsacl.c
>> +++ b/fs/cifs/cifsacl.c
>> @@ -169,8 +169,7 @@ static void copy_sec_desc(const struct cifs_ntsd *pntsd,
>> for (i = 0; i < 6; i++)
>> ngroup_sid_ptr->authority[i] = group_sid_ptr->authority[i];
>> for (i = 0; i < 5; i++)
>> - ngroup_sid_ptr->sub_auth[i] =
>> - cpu_to_le32(group_sid_ptr->sub_auth[i]);
>> + cpu_to_le32s(&group_sid_ptr->sub_auth[i]);
>>
>> return;
>> }
>
> No - the cifsacl one looks like just a bug - there should not be an
> endian conversion here.
>
I think you are right, there should not be any conversion since the
sub authorities would be in little endin format when we did get_cifs_acl
prior to this copy.
> Shirish,
> Would you verify?
>
> --
> Thanks,
>
> Steve
>
prev parent reply other threads:[~2008-07-24 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1216860920.30386.55.camel@brick>
2008-07-24 1:39 ` Steve French
2008-07-24 13:43 ` Shirish Pargaonkar [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=4a4634330807240643j6eb3314am343efe6c37992b50@mail.gmail.com \
--to=shirishpargaonkar@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.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
all inboxes | Powered by JetHome®