From: Ming Lei <ming.lei@canonical.com>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>
Subject: Re: linux-next: manual merge of the driver-core tree with the driver-core.current tree
Date: Wed, 19 Jun 2013 23:04:04 +0800 [thread overview]
Message-ID: <CACVXFVObBDwaounzZ7RyF=+QrQCBoEd0s-uLYFokksOzKgZSjA@mail.gmail.com> (raw)
In-Reply-To: <20130619143918.GC8413@kroah.com>
On Wed, Jun 19, 2013 at 10:39 PM, Greg KH <greg@kroah.com> wrote:
> On Wed, Jun 19, 2013 at 02:58:39PM +0800, Ming Lei wrote:
>> On Wed, Jun 19, 2013 at 1:32 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> > Hi Greg,
>> >
>> > Today's linux-next merge of the driver-core tree got a conflict in
>> > drivers/base/firmware_class.c between commit 875979368eb4 ("firmware
>> > loader: fix use-after-free by double abort") from the driver-core.current
>> > tree and commit fe304143b0c3 ("firmware: Avoid deadlock of usermodehelper
>> > lock at shutdown") from the driver-core tree.
>> >
>> > I fixed it up (more may be required - see below) and can carry the fix as
>> > necessary (no action is required).
>> >
>> > --
>> > Cheers,
>> > Stephen Rothwell sfr@canb.auug.org.au
>> >
>> > diff --cc drivers/base/firmware_class.c
>> > index 01e2103,6ede229..0000000
>> > --- a/drivers/base/firmware_class.c
>> > +++ b/drivers/base/firmware_class.c
>> > @@@ -446,22 -452,11 +452,18 @@@ static struct firmware_priv *to_firmwar
>> > return container_of(dev, struct firmware_priv, dev);
>> > }
>> >
>> > - static void fw_load_abort(struct firmware_priv *fw_priv)
>> > + static void fw_load_abort(struct firmware_buf *buf)
>> > {
>> > - struct firmware_buf *buf = fw_priv->buf;
>> > -
>> > + /*
>> > + * There is a small window in which user can write to 'loading'
>> > + * between loading done and disappearance of 'loading'
>> > + */
>> > + if (test_bit(FW_STATUS_DONE, &buf->status))
>> > + return;
>> > +
>> > + list_del_init(&buf->pending_list);
>> > set_bit(FW_STATUS_ABORT, &buf->status);
>> > complete_all(&buf->completion);
>> > -
>> > - /* avoid user action after loading abort */
>> > - fw_priv->buf = NULL;
>>
>> Hmm, maybe the most important part in the commit 875979368eb4
>> ("firmware loader: fix use-after-free by double abort") has been removed, :-)
>>
>> In fact, the commit 87597936 is for linus tree only because it is a fix,
>> so the conflict is caused by merging it with other firmware loader patches
>> in -next tree.
>>
>> Greg, I can figure out one patch for -next easily, but it depends you
>> push it on 3.10-rc or 3.11-rc.
>
> I'll be pushing your patch for 3.10-final to Linus as it fixes a bug,
> but I will need something to resolve the merge issue properly. Can you
> provide me that patch/merge?
OK, I can send you one patch, but I am wondering the patch is against
today's next tree or your driver-core/driver-core-next?
If it is against your driver-core/driver-core-next, would you mind letting
me know how to generate the patch for the conflict? Sorry for the stupid
question, because I seldom meet such problem, :-(
Thanks,
--
Ming Lei
next prev parent reply other threads:[~2013-06-19 15:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 5:32 linux-next: manual merge of the driver-core tree with the driver-core.current tree Stephen Rothwell
2013-06-19 5:55 ` Greg KH
2013-06-19 6:58 ` Ming Lei
2013-06-19 14:39 ` Greg KH
2013-06-19 15:04 ` Ming Lei [this message]
2013-06-19 16:36 ` Greg KH
2013-06-20 0:23 ` Ming Lei
2013-06-20 1:06 ` Stephen Rothwell
2013-06-20 1:22 ` Ming Lei
2013-06-20 3:28 ` Greg KH
2013-06-20 3:46 ` Ming Lei
2013-06-20 3:49 ` Stephen Rothwell
2013-06-19 7:12 ` Stephen Rothwell
2013-06-19 7:21 ` Ming Lei
-- strict thread matches above, loose matches on Subject: below --
2020-04-30 4:25 Stephen Rothwell
2020-04-30 8:15 ` Greg KH
2013-12-09 3:47 Stephen Rothwell
2013-12-09 8:21 ` Greg KH
2012-02-03 3:51 Stephen Rothwell
2012-02-03 15:07 ` Greg KH
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='CACVXFVObBDwaounzZ7RyF=+QrQCBoEd0s-uLYFokksOzKgZSjA@mail.gmail.com' \
--to=ming.lei@canonical.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).